Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen diagnosis needed!


  • Please log in to reply
5 replies to this topic

#1 tombstone37

tombstone37

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:30 PM

Posted 18 March 2010 - 01:27 PM

This is my memory dump, please help me decipher this dump, i need to understand the cause of my dump.

________________________________________________________________________



Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\la06278a\Desktop\Minidump\Mini030910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Mar 9 16:51:37.599 2010 (GMT-7)
System Uptime: 0 days 8:45:37.264
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 116e001, 4185f, c0883000}

Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 0116e001
Arg3: 0004185f
Arg4: c0883000

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: HPBPRO.EXE

LAST_CONTROL_TRANSFER: from 00650076 to 804f9f43

STACK_TEXT:
9017bfd8 00650076 00330072 00000032 0043005f nt!_woutput+0x414
WARNING: Frame IP not in any known module. Following frames may be wrong.
9017bfe8 0041004c 00000000 00000000 00000000 0x650076
9017bfec 00000000 00000000 00000000 00000000 0x41004c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+414

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e9e60

FAILURE_BUCKET_ID: 0x1a_41284_nt!_woutput+414

BUCKET_ID: 0x1a_41284_nt!_woutput+414

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,753 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:30 AM

Posted 18 March 2010 - 01:43 PM

Try uninstalling all HP printer software and deleting the printer...then reinstalling.

Louis

#3 tombstone37

tombstone37
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:30 PM

Posted 18 March 2010 - 02:12 PM

Louis,

Can you point out the specifics and how you came to this conclusion by reading my mem dump file?

I would like to understand how to read this alittle for future reference.

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,753 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:30 AM

Posted 18 March 2010 - 03:34 PM

Look at the Process Name line in the data you displayed...then Google to see what the referenced file might be.

Net result: http://www.file.net/process/hpbpro.exe.html.

IMO, most BSODs are caused by a damaged file, many of those are drivers for some program or function.

The only way to repair damaged files...is to uninstall the file/program...and then replace/reinstall.

Louis

#5 tombstone37

tombstone37
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:30 PM

Posted 18 March 2010 - 04:01 PM

Louis, thank you very much.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,753 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:30 AM

Posted 18 March 2010 - 05:34 PM

Easily done, let us know if that solves it (or fails to solve it).

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users