Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Debug Files Please

06 Jun 2010   #41
thomamon

Windows 7 Professional 64 Bit
 
 

Quote   Quote: Originally Posted by richc46 View Post
Evidentally, the tests that are used to determine the fact that a driver is current or not isn't completly accurate. The only cure is to download from the website, which is the suggested procedure, anyway. Once you have updated all the potentially problemsome drivers from the website, you are done. Even if some test says its not up to date, not much you can do.
Wow, this is so frustrating because I am back to where I was before. I am thinking my wife is right about just replacing the entire computer, at this point I just want to throw it against the wall and her telling me she needs it working surely does not help.

I have been to the website for all the hardware and updated all the drivers by hand when the kernel 41 power reboot started. So unless the manufacturer of one of the websites has a bad driver up there, what else can it be?


My System SpecsSystem Spec
.
06 Jun 2010   #42
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

I have never told anyone to buy a new computer, since I cannot even see it. That being said it does appear that you are having quite a bit of problems. Member Jon_King even gave his opinion and indicated that it may be memory and also potentialyl the hard drive. If the computer is old, you may want to consider getting new. The time we have spent together has just resulted in trading an automatic reboot for a BSOD. The potential help that I can give is limited by the information supplied by the mini dump, no more I can do. I will be glad to answer questions, but I can not suggest buying a new computer.

Sound like the computer is important to your wife, it may be a good investment.
My System SpecsSystem Spec
06 Jun 2010   #43
thomamon

Windows 7 Professional 64 Bit
 
 

Quote   Quote: Originally Posted by richc46 View Post
I have never told anyone to buy a new computer, since I cannot even see it. That being said it does appear that you are having quite a bit of problems. Member Jon_King even gave his opinion and indicated that it may be memory and also potentialyl the hard drive. If the computer is old, you may want to consider getting new. The time we have spent together has just resulted in trading an automatic reboot for a BSOD. The potential help that I can give is limited by the information supplied by the mini dump, no more I can do. I will be glad to answer questions, but I can not suggest buying a new computer.

Sound like the computer is important to your wife, it may be a good investment.
Its barely a year old, so replacing it would be a waste of money, IMO. But if it can not be fixed, I don't know what else to do.

I just got a BSOD with a pxhlpa64.sys error after turning no driver verifier. Once it boots up, it goes to that screen and I can't even get into it anymore.

Again, I can not thank you enough for you continuously trying to help me with it. You have been a great during all of this.
My System SpecsSystem Spec
.

06 Jun 2010   #44
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

That is a DVD drive issue.

Do one last thing. Shut off the computer. Boot, tell me the exact beeps are they long, short, one, two etc. one long, two short.
My System SpecsSystem Spec
06 Jun 2010   #45
thomamon

Windows 7 Professional 64 Bit
 
 

Quote   Quote: Originally Posted by richc46 View Post
That is a DVD drive issue.

Do one last thing. Shut off the computer. Boot, tell me the exact beeps are they long, short, one, two etc. one long, two short.
Just one quick beep.
My System SpecsSystem Spec
06 Jun 2010   #46
thomamon

Windows 7 Professional 64 Bit
 
 

Here is the latest dump with an XML file it told me it had. Maybe this will help more?
My System SpecsSystem Spec
06 Jun 2010   #47
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

Actually that is a good sign. Most compputer mfgs. have a beep code. No beeps or one beep means the computer hardware is ok.

Your call, trust the beeps or the dmp file. Go with the beeps, worse case scenario, you have to reinstall, saving hundreds of dollars.
My System SpecsSystem Spec
06 Jun 2010   #48
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

Driver
You can read it yourself, this one is fairly clear. I marked it in bold.


Code:
   Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WER-81588-0.sysdata[1].zip\060610-32089-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
Debug session time: Sun Jun  6 20:16:54.120 2010 (GMT-4)
System Uptime: 0 days 0:01:24.774
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {224, fffff880011692d8, fffff98017234d30, 3}
Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+82d8 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
 IRP's IoStatus.Status field.
Arg2: fffff880011692d8, The address in the driver's code where the error was detected.
Arg3: fffff98017234d30, IRP address.
Arg4: 0000000000000003, Expected status code.
Debugging Details:
------------------
 
BUGCHECK_STR:  0xc9_224
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224
FAULTING_IP: 
PxHlpa64+82d8
fffff880`011692d8 53              push    rbx
FOLLOWUP_IP: 
PxHlpa64+82d8
fffff880`011692d8 53              push    rbx
IRP_ADDRESS:  fffff98017234d30
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800031093dc to fffff80002c7f600
STACK_TEXT:  
fffff880`02fe8378 fffff800`031093dc : 00000000`000000c9 00000000`00000224 fffff880`011692d8 fffff980`17234d30 : nt!KeBugCheckEx
fffff880`02fe8380 fffff800`0311347a : fffff800`031079f0 fffff880`011692d8 fffff980`17234d30 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02fe83c0 fffff800`031143f3 : fffff880`011692d8 fffffa80`07b5bca8 00000000`00000003 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02fe8410 fffff800`0311f759 : fffffa80`07b5bbf0 fffffa80`07b5bbf0 fffffa80`07b5bca8 fffff880`0116b0b0 : nt!VfErrorReport4+0x83
fffff880`02fe8500 fffff800`0311fb63 : fffffa80`07b5bbf0 00000000`00000002 fffffa80`05b36030 fffff8a0`042389b0 : nt!IovpCallDriver2+0x179
fffff880`02fe8560 fffff800`03125c2e : fffff980`17234d30 fffff980`17234d30 00000000`00000002 fffffa80`05b36030 : nt!VfAfterCallDriver+0x353
fffff880`02fe85b0 fffff800`031284da : fffff980`17234f20 fffffa80`05b36030 fffffa80`05b35620 fffffa80`07b5bbf0 : nt!IovCallDriver+0x57e
fffff880`02fe8610 fffff800`03125c16 : fffff980`17234d30 00000000`00000002 fffffa80`05b35620 fffffa80`07920d60 : nt!ViFilterDispatchPnp+0xea
fffff880`02fe8640 fffff880`00efc93c : fffff980`17234f68 00000000`00000000 fffffa80`05b3eb60 fffffa80`07920d60 : nt!IovCallDriver+0x566
fffff880`02fe86a0 fffff880`00ef52ce : 00000000`00000001 fffff880`02fe87b0 fffff880`02fe8700 fffffa80`05b3eb00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`02fe86d0 fffff880`00ef3dd6 : fffffa80`0590ec02 00000000`00000002 00000000`00000000 fffffa80`05b3eb60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`02fe8740 fffff880`00ec3245 : fffff980`17234d30 fffff980`17234d30 fffffa80`05b3e5a0 fffffa80`05b3e5a0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`02fe87b0 fffff880`00ec314b : fffff880`02fe8898 fffff980`17234d30 00000000`00000002 fffffa80`05b3e5a0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02fe87e0 fffff800`03125c16 : fffff980`17234d30 00000000`00000002 fffffa80`05b3e5a0 fffff880`02fe8938 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`02fe8820 fffff800`02eec3a5 : fffffa80`05b3e5a0 00000000`c00000bb fffff880`02fe8938 fffffa80`07646200 : nt!IovCallDriver+0x566
fffff880`02fe8880 fffff800`03069ec1 : fffffa80`04f89060 00000000`00000000 fffffa80`04f6f5c0 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`02fe88f0 fffff800`02d80b43 : fffff8a0`023ef1b0 fffff8a0`023ef1b0 00000000`00000015 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`02fe89b0 fffff800`03069a14 : fffffa80`04f6f5c0 00000000`00000000 00000000`00000002 fffffa80`04f89060 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`02fe8a00 fffff800`03069b20 : 00000000`00000000 fffff8a0`0408e001 fffff8a0`0388d840 ffffe69c`a74d3ae5 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`02fe8a30 fffff800`030fa044 : 00000000`00000002 00000000`00000000 fffffa80`04f6f5c0 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`02fe8aa0 fffff800`030fa69c : fffff880`00000000 00000000`00010200 fffff880`02fe8c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`02fe8be0 fffff800`02fe573c : 00000000`00000000 fffffa80`05dfc2a0 fffff8a0`0408e010 fffff800`02e24500 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`02fe8c10 fffff800`02c8c861 : fffff800`02eebe80 fffff8a0`0408e010 fffff800`02e245f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x592eb
fffff880`02fe8c70 fffff800`02f24a86 : 00000000`00000000 fffffa80`0371a040 00000000`00000080 fffffa80`036fd040 : nt!ExpWorkerThread+0x111
fffff880`02fe8d00 fffff800`02c5db06 : fffff880`009e8180 fffffa80`0371a040 fffff880`009f2f40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`02fe8d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  PxHlpa64+82d8
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: PxHlpa64
IMAGE_NAME:  PxHlpa64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  45c3ac06
FAILURE_BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+82d8
BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+82d8
Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Jun 2010   #49
thomamon

Windows 7 Professional 64 Bit
 
 

OK, so we know it is a driver right now. How do we know which one it is? LOL

Quote   Quote: Originally Posted by richc46 View Post
Driver
You can read it yourself, this one is fairly clear. I marked it in bold.


Code:
   Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WER-81588-0.sysdata[1].zip\060610-32089-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
Debug session time: Sun Jun  6 20:16:54.120 2010 (GMT-4)
System Uptime: 0 days 0:01:24.774
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {224, fffff880011692d8, fffff98017234d30, 3}
Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+82d8 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
 IRP's IoStatus.Status field.
Arg2: fffff880011692d8, The address in the driver's code where the error was detected.
Arg3: fffff98017234d30, IRP address.
Arg4: 0000000000000003, Expected status code.
Debugging Details:
------------------
 
BUGCHECK_STR:  0xc9_224
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224
FAULTING_IP: 
PxHlpa64+82d8
fffff880`011692d8 53              push    rbx
FOLLOWUP_IP: 
PxHlpa64+82d8
fffff880`011692d8 53              push    rbx
IRP_ADDRESS:  fffff98017234d30
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800031093dc to fffff80002c7f600
STACK_TEXT:  
fffff880`02fe8378 fffff800`031093dc : 00000000`000000c9 00000000`00000224 fffff880`011692d8 fffff980`17234d30 : nt!KeBugCheckEx
fffff880`02fe8380 fffff800`0311347a : fffff800`031079f0 fffff880`011692d8 fffff980`17234d30 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02fe83c0 fffff800`031143f3 : fffff880`011692d8 fffffa80`07b5bca8 00000000`00000003 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02fe8410 fffff800`0311f759 : fffffa80`07b5bbf0 fffffa80`07b5bbf0 fffffa80`07b5bca8 fffff880`0116b0b0 : nt!VfErrorReport4+0x83
fffff880`02fe8500 fffff800`0311fb63 : fffffa80`07b5bbf0 00000000`00000002 fffffa80`05b36030 fffff8a0`042389b0 : nt!IovpCallDriver2+0x179
fffff880`02fe8560 fffff800`03125c2e : fffff980`17234d30 fffff980`17234d30 00000000`00000002 fffffa80`05b36030 : nt!VfAfterCallDriver+0x353
fffff880`02fe85b0 fffff800`031284da : fffff980`17234f20 fffffa80`05b36030 fffffa80`05b35620 fffffa80`07b5bbf0 : nt!IovCallDriver+0x57e
fffff880`02fe8610 fffff800`03125c16 : fffff980`17234d30 00000000`00000002 fffffa80`05b35620 fffffa80`07920d60 : nt!ViFilterDispatchPnp+0xea
fffff880`02fe8640 fffff880`00efc93c : fffff980`17234f68 00000000`00000000 fffffa80`05b3eb60 fffffa80`07920d60 : nt!IovCallDriver+0x566
fffff880`02fe86a0 fffff880`00ef52ce : 00000000`00000001 fffff880`02fe87b0 fffff880`02fe8700 fffffa80`05b3eb00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`02fe86d0 fffff880`00ef3dd6 : fffffa80`0590ec02 00000000`00000002 00000000`00000000 fffffa80`05b3eb60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`02fe8740 fffff880`00ec3245 : fffff980`17234d30 fffff980`17234d30 fffffa80`05b3e5a0 fffffa80`05b3e5a0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`02fe87b0 fffff880`00ec314b : fffff880`02fe8898 fffff980`17234d30 00000000`00000002 fffffa80`05b3e5a0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02fe87e0 fffff800`03125c16 : fffff980`17234d30 00000000`00000002 fffffa80`05b3e5a0 fffff880`02fe8938 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`02fe8820 fffff800`02eec3a5 : fffffa80`05b3e5a0 00000000`c00000bb fffff880`02fe8938 fffffa80`07646200 : nt!IovCallDriver+0x566
fffff880`02fe8880 fffff800`03069ec1 : fffffa80`04f89060 00000000`00000000 fffffa80`04f6f5c0 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`02fe88f0 fffff800`02d80b43 : fffff8a0`023ef1b0 fffff8a0`023ef1b0 00000000`00000015 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`02fe89b0 fffff800`03069a14 : fffffa80`04f6f5c0 00000000`00000000 00000000`00000002 fffffa80`04f89060 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`02fe8a00 fffff800`03069b20 : 00000000`00000000 fffff8a0`0408e001 fffff8a0`0388d840 ffffe69c`a74d3ae5 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`02fe8a30 fffff800`030fa044 : 00000000`00000002 00000000`00000000 fffffa80`04f6f5c0 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`02fe8aa0 fffff800`030fa69c : fffff880`00000000 00000000`00010200 fffff880`02fe8c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`02fe8be0 fffff800`02fe573c : 00000000`00000000 fffffa80`05dfc2a0 fffff8a0`0408e010 fffff800`02e24500 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`02fe8c10 fffff800`02c8c861 : fffff800`02eebe80 fffff8a0`0408e010 fffff800`02e245f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x592eb
fffff880`02fe8c70 fffff800`02f24a86 : 00000000`00000000 fffffa80`0371a040 00000000`00000080 fffffa80`036fd040 : nt!ExpWorkerThread+0x111
fffff880`02fe8d00 fffff800`02c5db06 : fffff880`009e8180 fffffa80`0371a040 fffff880`009f2f40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`02fe8d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  PxHlpa64+82d8
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: PxHlpa64
IMAGE_NAME:  PxHlpa64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  45c3ac06
FAILURE_BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+82d8
BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+82d8
Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Jun 2010   #50
Jonathan_King

Windows 7 Professional x64
 
 

I haven't run the dmps myself, but I will assume it is indeed a driver issue.

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers
My System SpecsSystem Spec
Reply

 Debug Files Please




Thread Tools




Similar help and support threads
Thread Forum
can someone please help me debug
So I built this computer several months ago. And this is the first bsod ive gotten, so its very strange, and its really bothering me. It happened while I was playing a game (one that i play all the time). Im going to upload the dmp file, so you guys can help me figure this out. My system specs...
BSOD Help and Support
Debug Errors
Hi, would someone please have a look at the attached log file and see if they can suggest ways to resolves the errors I keep getting. Windows 7 64 bit Professional Service Pack 1 Processor: Intel Core i5 2500K Motherboard: Foxconn H67M-S/H67M-V/H67 Memory: 8192MB (2 x 4096 DDR3-SDRAM ) ...
BSOD Help and Support
Debug
Hi Can anyone tell me what I need to do to read the .DMP files in the minidump directory. Windows 7 32 bit. Thanxhttp://cdn.sevenforums.com/images/smilies/biggrin.gif
BSOD Help and Support
taskhost - Debug (I think)
Hi everyone, First of all, I'd like to thank you all who are interested in helping me. I have turned off my computer last night and everything was working fine except when I turned it on about an hour ago, it started to give debug messages on the screen. On the window that pops up, states the...
BSOD Help and Support
Debug please!
thanks guys
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:28.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App