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

BSOD/ Memory dump translation


  • Please log in to reply
4 replies to this topic

#1 104percent

104percent

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:04 PM

Posted 09 June 2009 - 08:20 PM

I have a HP dv6171cl with a brand new hard drive and operating system. (xp home) I installed the new HD & OS less than a week ago and have been getting the BSOD occasionally ever since. The blue screen is blurry so I cannot read the error message when it comes up.

I did a little research and after I found that my event viewer was not logging any information about the crashes I found that the .dmp file may be helpful. Unfortunately my computer is not creating a .dmp file when it crashes so I had to force one by modifying the registry. I am very new to this but from what I have read this requires a "complete dump" so I have posted below the results of a user initiated BSOD "complete dump" file. Any help in translating this into something actionable would be greatly appreciated.

I suspect is has something to do with the drivers so, I have tried updating and them rolling back one at a time to find the culprit. I have not had any success. I would not rule this possibility out but I have not been able to fix it by this method.

Any help you can provide is greatly appreciated. If I can provide any further information please let me know.



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


Loading Dump File [C:\WINDOWS\Minidump\Mini060909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jun 9 20:33:45.687 2009 (GMT-3)
System Uptime: 0 days 0:02:01.251
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E2, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\AmdPPM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AmdPPM.sys
*** ERROR: Module load completed but symbols could not be loaded for AmdPPM.sys
Probably caused by : i8042prt.sys ( i8042prt!I8xProcessCrashDump+237 )

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

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

MANUALLY_INITIATED_CRASH (e2)
The user manually initiated this crash dump.
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: MANUALLY_INITIATED_CRASH

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from b9c187fb to 804f9f43

STACK_TEXT:
bacdfc38 b9c187fb 000000e2 00000000 00000000 nt!KeBugCheckEx+0x1b
bacdfc54 b9c18033 00ae60d8 01fcacc6 00000000 i8042prt!I8xProcessCrashDump+0x237
bacdfc9c 805456a5 898799c0 89ae6020 01010009 i8042prt!I8042KeyboardInterruptService+0x21c
bacdfc9c baada832 898799c0 89ae6020 01010009 nt!KiInterruptDispatch+0x45
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdfd30 bab38c70 80528799 bab38000 8055c0c0 AmdPPM+0x2832
bacdfd50 80545d4c 00000000 0000000e a756a665 0xbab38c70
bacdfd54 00000000 0000000e a756a665 7487a687 nt!KiIdleLoop+0x10


STACK_COMMAND: kb

FOLLOWUP_IP:
i8042prt!I8xProcessCrashDump+237
b9c187fb 5d pop ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: i8042prt!I8xProcessCrashDump+237

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: i8042prt

IMAGE_NAME: i8042prt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c67

FAILURE_BUCKET_ID: MANUALLY_INITIATED_CRASH_i8042prt!I8xProcessCrashDump+237

BUCKET_ID: MANUALLY_INITIATED_CRASH_i8042prt!I8xProcessCrashDump+237

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,385 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:04 PM

Posted 09 June 2009 - 08:51 PM

<<IMAGE_NAME: i8042prt.sys>>

Info on http://www.file.net/process/i8042prt.sys.html

On my system...that file is the keyboard driver. I would just uninstall it (using Device Manager), reboot and let a new one install.

I have 4 copies of that driver, all legit (not malware), so don't be surprised if you do a search of your system and find that you have four copies.

Louis

#3 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:10:04 PM

Posted 09 June 2009 - 09:02 PM

From what I can see looking at your dump file it looks like it's pointing to the AMD CPU driver ( normally amdk8.sys ) for your laptop. It also looks like you're running a laptop with an X2 or dual core AMD processor of some kind. I would try this http://h10025.www1.hp.com/ewfrf/wc/softwar...product=3253924 first then I would go to www.amd.com and get the most up to date processor driver for your version chip for Windows XP and get it installed.

I poked around on the net a little bit and found some "shaking of the trees" about SP3 and AMD cpu's. I myself have not experienced any problems with SP3 and AMD processors yet ( knock on wood ). I run Turion's, Opterons, and Athlon64 X2's all with SP3.

Hope this helps.

Techextreme
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#4 104percent

104percent
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:04 PM

Posted 11 June 2009 - 07:52 AM

Thanks for your help guys. I uninstalled the keyboard and the processor drivers and have not had a BSOD event since. I will post again if the problem happens again.

PS I think it was the processor drivers that did it. I should have mentioned it but the registry modification was to the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameter

so I think the i8042 portion of the log is related to the way in which I caused the crash. But this is all very new to me so I am not sure.


Thanks again guys. :thumbsup:

#5 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:10:04 PM

Posted 11 June 2009 - 08:24 AM

Glad to hear you got it working.

Happy computing!!

Techextreme
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users