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: BSOD while resuming from sleep, or not resuming from sleep at all

01 Oct 2012   #1

W7 Ultimate 64 bits
 
 
BSOD while resuming from sleep, or not resuming from sleep at all

My system was never able to resume from sleep. Tried several things, BIOS settings, settings for power management etc.
Thought it could be related to recovery software or other installed drivers etc.

But now: I replaced my harddisk with a SSD, did a fresh install of Windows 7 Ultimate 64. Removed all possible hardware (tv card, usb devices except keyboard / mouse). Tried fail save options in BIOS and optimized settings as well but no luck.
Got most windows updates in place, installed all the latest drivers from the motherboard and graphics card, latest bios drivers and still getting BSOD.

Who can help me solving this so I can save lots of energy.
Followed the manual to attach zip file with minidumps etc. Please let me know when additional info is required.

Details about what happens:
When I put my system into sleep it goes well. When I try to wake my system:
often nothing happens and I have to shut it down holding start button
or I get back my desktop but within a few seconds I get a BSOD.

If I have seen it well I posted several minidumps, so I hope it is not too difficult to find the ones related to the resume from sleep.


Kind regards,

Michel

My System SpecsSystem Spec
.

01 Oct 2012   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Welcome aboard

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
15 Oct 2012   #3

W7 Ultimate 64 bits
 
 

Thanks Arc,

Done as suggested, added new crashdump file, hope that provides the required info.

regards, Michel
My System SpecsSystem Spec
.


15 Oct 2012   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Michel, are you sure that the driver verifier was running there when it crashed?
It does not indicate so.

Anyway, based on that dump, I can suggest you two things.

You perform a disc check.
Code:
fffff880`0a1e1d38  fffff880`0146b7a3 Ntfs!NtfsLookupAllocation+0x4c3
fffff880`0a1e1d40  00000000`00000010
fffff880`0a1e1d48  00000000`00010282
fffff880`0a1e1d50  fffff880`0a1e1d60
fffff880`0a1e1d58  00000000`00000018
fffff880`0a1e1d60  fffff8a0`04022270
fffff880`0a1e1d68  fffff880`0a1e23b0
fffff880`0a1e1d70  fffff980`19feec60
fffff880`0a1e1d78  fffff880`01288701 fltmgr!FltpQueryInformationFileFromInstance+0x71
As ntfs and fltmgr errors are there, it is better to check for possible ntfs corruptions.
  1. Reseat the sata and power.
  2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  3. Seatool for dos: SeaTools | Seagate download
    Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
  4. If you are using a SSD, update its firmware.
You need to check your RAM Modules.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffda8032969519, 1, fffff8800146b7a3, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
Do it: RAM - Test with Memtest86+
Run memtest for at least 8 passes, for each module in each slot. That means, if you have two modules and two slots, you are to run total 32 passes.

Free up the startup.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept the restart.
Uninstall the following programs:
  • Start Menu\Programs\ASUS
  • Start Menu\Programs\Catalyst Control Center
  • Start Menu\Programs\MSI\Live Update 5
Let us know the results.
My System SpecsSystem Spec
Reply

 BSOD while resuming from sleep, or not resuming from sleep at all





Thread Tools



Similar help and support threads for2: BSOD while resuming from sleep, or not resuming from sleep at all
Thread Forum
BSOD after resuming from Sleep BSOD Help and Support
Solved BSOD after resuming from Sleep BSOD Help and Support
Solved BSOD when resuming from sleep BSOD Help and Support
BSOD after resuming from sleep BSOD Help and Support
Solved BSOD When resuming From Sleep BSOD Help and Support
bsod after resuming sleep BSOD Help and Support
BSOD's after resuming from sleep 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 09:37 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33