Member Avatar for MH_Wadester

hey so heres whats happening recently i have been receiving the windows message "windows has Recovered from an Unexpected Shutdown" randomly... i dont know what triggered this because it happens occasionally on shutdown and i get the blue screen but a lot of the time i dont see the bluescreen.... doesnt happen on startup.I get this message a lot when my computer wakes from as sleep.
More detailed info on the message is :
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.
Locale ID: 3081

Additional information about the problem:
BCCode: 9f
BCP1: 00000003
BCP2: 870B6030
BCP3: 82D78AE0
BCP4: 86F7C8C8
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\060310-21855-01.dmp
C:\Users\Wade\AppData\Local\Temp\WER-54257-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Please can you help me fix or find a solution for this... thanks in advance
PS: I am running windows 7 on a new hdd that is currently up to date along with all my drivers supposedly..

  • 2 Contributors
  • 3 Replies
  • 294 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by davidmorgen19

Dani AI

Generated

Quick expert summary: the symptoms described match a DRIVER_POWER_STATE_FAILURE (stop code 0x9F) — a driver failed during a sleep/resume power transition. That is consistent with the crashes happening on wake and with attached minidumps; the minidump is the right place to look for the exact faulty module. [Microsoft — Bug Check 0x9F].(https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x9f--driver-power-state-failure)

How to get the most useful diagnostic quickly: open the supplied minidump(s) with the Windows Debugging Tools (WinDbg), point WinDbg at the Microsoft symbol server, and run a verbose analysis to show the suspected driver and stack. Example workflow:

windbg -y SRV*c:\symbols*https://msdl.microsoft.com/download/symbols -z path\to\minidump.dmp
!analyze -v
dx KiBugCheckDriver

The "!analyze -v" output and the MODULE_NAME / stack frames are the key indicators. [WinDbg !analyze docs].(https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/-analyze)

Practical, low-risk remediation steps to try first: update or roll back device drivers (start with network/wireless, display, and chipset drivers), disable adapter power-saving options and USB selective suspend, and check for BIOS/ACPI firmware updates. Reseating RAM as suggested is a quick sanity check, but 0x9F more commonly implicates drivers; if memory is still suspected, run a full MemTest86 pass. When changing the registry or firmware, back up important data first. [Network adapter power settings].(https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/power-management-on-network-adapter) [MemTest86].(https://www.memtest86.com/)

If the dump points to a specific driver but updating does not help, use Driver Verifier to force and identify driver failures — with the caveat that it intentionally stresses drivers and can cause additional crashes; "verifier /reset" from Safe Mode clears it. The combination of the WinDbg "!analyze -v" summary and the MODULE_NAME/stack frame is what determines whether to update, roll back, or remove the offending driver. [Driver Verifier].(https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier)

Member Avatar for MH_Wadester

heres a zip file of all my minidumps if that helps with your solution.

060410-21512-01.zip (69.64 KB)
Member Avatar for MH_Wadester

sorry i found there was some hidden minidump files that i didnt include here is the zip file of all the minidump files

060310-20217-01.zip (403.37 KB)
Member Avatar for davidmorgen19

I think this problem is because of RAM.
Open your cabinet Unplug RAM clean it and plug in and check this problem will be solved. and if it is occurs again then plug in another RAM and check it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.