BSOD's not saving minidumps, multiple 0x9F crashes

[piehole1983]

Crap, sorry. Let me try to sort it out now.

 

[piehole1983]

I have downloaded the very same zip file and the DMP file IS there! It's 2/3's the way down the list of files and its named 022112-19999-01.dmp

Here it is anyway:

 

[piehole1983]

Have you had a chance to look through the dump?

 

[piehole1983]

Anyone?

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\piehole1983\022112-19999-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03049e90
Debug session time: Mon Feb 20 19:14:48.912 2012 (UTC - 6:00)
System Uptime: 0 days 0:24:54.005
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, fffffa8003c40040, fffff80000b9c510}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8003c40040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8003c40040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f0cea6 to fffff80002e84640

STACK_TEXT:  
fffff800`00b9c4d8 fffff800`02f0cea6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`03c40040 : nt!KeBugCheckEx
fffff800`00b9c4e0 fffff800`030bf3cc : fffff800`00000000 fffffa80`00000000 fffff800`03004c00 fffff800`00b9cc58 : nt!PnpBugcheckPowerTimeout+0x76
fffff800`00b9c540 fffff800`02e90062 : 00000000`0000000a fffff800`00000000 00000000`00000000 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`00b9c570 fffff800`02e8ff06 : fffff880`03e26ad0 fffff880`03e26ad0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02e8fdee : 00000003`7a7f22e8 fffff800`00b9cc58 00000000`00017618 fffff800`02ff9588 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e8fbd7 : 00000000`c4adf1ce 00000000`00017618 00000000`c4adf10d 00000000`00000018 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e7c36a : fffff800`02ff6e80 fffff800`03004cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .thread 0xfffffa8003c40040 ; kb

FOLLOWUP_IP: 
nt!PnpBugcheckPowerTimeout+76
fffff800`02f0cea6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

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

Does not identify what driver is causing the problem. Are you getting crashes still? Any new .dmp files?

 

[piehole1983]

Yes, every single time I shut down. Really frustrating! It still will not save any new dumps either! I think I'm looking at some kind of hardware issue but which part?

 

[writhziden]

Use the following to check hardware:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

 

[piehole1983]

Thank you for the information! I started with realtemp and prime95 running together and almost instantly got CPU temps of 88 degrees and seems to be very slowly climbing!

I'll let it run on for a while and see what happens.

 

[piehole1983]

Check it out after 3 minutes!

 

[writhziden]

Could you fill out your system specs? It is a bit annoying to have to search through both of your threads to find information about your system. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html can be used as a guide to filling out the specs.

Regardless, those temperatures seem very high. Have you blown the dust out of the system in the past six months?

To remove dust, follow the subsequent general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
8. Start the computer and see if performance is better.

 

[piehole1983]

Sorry, I'll fill in the system spec. Basically it's a HP DV7 3111ea with an intel core i5 430M 2.26GHz processor. 4GB RAM and 500GB Toshiba HDD.

I have carried out numerous tests on the RAM and HDD using memtest and seatools with no faults arising.

Interestingly, when I ran the hardware test you mentioned before (hwinfo) the program froze at "detecting smart batteries". Is this perhaps my cause as the BSOD points to a power state failure? Is it ACPI based?

As for system cleanliness, it is like a new machine inside. Heat sink has been removed and cleaned, CPU cleaned, fresh thermal compound added.

 

[writhziden]

Odd that your temperatures would be getting so high with everything clean...

Power state failure means one of your drivers is not turning off the hardware or turning on the hardware when the system sends a signal for it to do so. The usually happens during sleep cycles, hibernation cycles, or shutdown/startup of the system. I do not know what "smart batteries" are other than batteries that can be charged? I did a Google search and found no information regarding them. Can you post the screenshot of the message: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[piehole1983]

Yes, I'll try it again once I'm at home. I can only assume its a term they have used for batteries in general. Would the operating system call for any of the battery circuitry to shut down?

 

[piehole1983]

And the problem I have only ever happens on startup/shutdown/sleep etc. any power state change!

 

[writhziden]

Driver power state failures are typically due to four things:

1. chipset drivers being outdated or corrupted
2. network adapter drivers being outdated or corrupted
3. sound drivers being outdated or corrupted
4. graphics card drivers being outdated or corrupted.

I would suggest uninstalling all of the above and re-installing them; start with the chipset drivers.



To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

 

[piehole1983]

I really appreciate your time and effort on this, it's helping me understand how these things work! I'll give your steps a go in the morning. My wife is getting fed up with me!

It's using the intel 5 series/3400 chipset and it's using the intel drivers for a lot of the on board hardware. Should I uninstall each part in the device manager individually that uses the intel drivers?

 

[writhziden]

It appears you have an Intel wireless adapter, integrated Ethernet adapter (not sure what brand, but may be Intel), and nVidia card. Audio is usually Realtek, but not sure with your computer as the specs for the general DV7 did not specify. Is this correct for your model? I am unable to find the exact model since you did not provide adequate information to do so, so I am working with some guesswork here.

If you have the intel wireless, I would uninstall it. Also uninstall any intel chipset drivers. Re-install the latest for all through the Intel® Driver Update Utility

 

[piehole1983]

Now you mention it, the HP driver site actually has two different drivers for the wireless card. The one I have appears to be Broadcom, at least that's what it physically says on the silicone chip on the card. I'll try removing the card from the machine and deleting all traces of it from the OS.

I'll google the specs of the machine and post them up.

 

[piehole1983]

The wireless adapter is Realtek but Intel's driver detection software picks it up and they have their own driver for it. Is it possible I would need to install the intel version of the driver instead of the Realtek version?

 

[writhziden]

Can you post the hardware ID? In device manager, if you right click on the driver, click properties, and go to the details tab, you can find the hardware ID for the wireless device. It is the second Property in the list within the Property section of the details tab.