Company about
Home > 64 Bit > 64 Bit Pro + Sleep = BSOD

64 Bit Pro + Sleep = BSOD

RAM is already tested with three different tools (memtest including), not a glitch. Copyright © 2006-2017 How-To Geek, LLC All Rights Reserved

About Screenshots Downloads Documentation     End-user docs     Technical docs Contribute Community Search: LoginPreferences Browse Source Context Navigation ← Previous TicketNext Ticket → This is killing me. Monitor(s) Displays HP 24z IPS Keyboard IBM Model M Keyboard Mouse Generic Microsoft Mouse PSU Corsair 750W Case CM Storm Scout Cooling Thermaltake Fans Hard Drives 120GB Intel 320 SSD with

If you wake it up right away it doesn't seem to happen, but after around 3 minutes it bluescreens. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. It too is no longer available for reproducing the problem (the OS was reinstalled to Win7, and till now the reported BSOD did not occur), but luckily I have the files I know the those controllers had some BSOD issues not to long ago.

Your cache administrator is webmaster. Related Resources HELP! - BSOD after Sleep Mode? ( Windows 7 ) solved BSOD Windows 7 64bit dxgmms1.sys help please Windows 7 Sleep Mode problem? Possibly this problem is caused by another driver which cannot be identified at this time. it just happened again too.

Hard reboot required. The issue as appearing is with the Linksys AE1200. (c:\windows\system32\drivers\ae1200w764.sys). i then re-inserted both sticks of RAM and again it blue screen.Iam currently running memtest86+ but it has not currently found any error but will post back later to let you It will resist the wake up/sleep time power transition, so there will be a less chance for a driver power state failure.

I also tried moving around to different USB ports. The event log under system shows this: The computer has rebooted from a bugcheck. In some threads, the driver with the blocked IRP, kept changing after each driver update/disabled device driver. see this here This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Based on past experience, I haven't always had the best of luck with USB network adapters. Or do you have a wireless connection to your AP? skazDec 9, 2011, 6:26 AM Go into power options, change plan settings, advance settings, hard disk, and select "turn hard disk off after" to "never". If I deinstall VirtualBox and try the same scenario, I never get BSOD, even if I don't wait at all and send the computer into hibernation immediately after exiting qBittorrent.

comment:4 follow-up: ↓ 5 Changed 4 years ago by mhanor Have you tried updating your ethernet nic drivers by going to www.realtek.com ? http://superuser.com/questions/642048/windows-7-64-bit-machine-blue-screen-every-time-it-wakes-up-from-sleep solved windows 7 hibernation and sleep mode shuts PC down and drains power solved i7 4790 cpu temps very high right after getting off sleep mode HELP Sleep mode windows 7 At first I didn't bother doing a fresh install; I just uninstalled the old... Possibly this problem is caused by another driver which cannot be identified at this time.

Windows 7: Windows 7 x64 Pro bluescreen after waking from sleep 07 Dec 2013 #1 Diogones Windows 7 Professional x64 73 posts Windows 7 x64 Pro bluescreen after That's plain facts. It appears to be a physical memory dump error. Worse comes to worst, I can always replace it easily enough.

B85M-D3H Memory Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz) Graphics Card 2047MB GeForce GTS 450 (ZOTAC International) Sound Card Onboard (Realtek High Definition Audio) Monitor(s) Displays LG Flatron E2040T there are no programs open when i put the computer to sleep manually but the error still occurs. okay i saw the link but i dont know what to download if those are service pack 1 for windows 7 i think my computer already installed those updates... May be around 8 GgB if its there u can resoter ur Pc to ur factory settings which brand ur using ?

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. On Thu 06/10/2011 1:02:54 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\100611-26442-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8003057A10, 0xFFFFF80000BA2748, 0xFFFFFA8004C4B740) Error: Memory came back ok.

NTOSKRNL.EXE is a operating system file.

And I am having 2 seperate issues(one is a minor issue) and I am completely stumped. Possibly this problem is caused by another driver which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 10 crash dumps have been found and analyzed. On Fri 07/10/2011 5:29:03 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x9F (0x3, 0xFFFFFA8003087A10, 0xFFFFF8000519D748, 0xFFFFFA800543A270) Error: I didn't see an actual BlueScreen, everything just froze.

Possibly this problem is caused by another driver which cannot be identified at this time. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. The kernel pools are fare away from the limit. Also, although this BSOD (blue screen of death) problem is new, I've had a problem for years where the computer will suddenly freeze solid, requiring hard reboot.

The next morning or sometime after the computer is put to sleep the blue light is on (not blinking) at this point there is not disk activity(red... It happened about 5-10 minutes after starting up the computer from the off position (not sleep/hibernation). BSOD Help and Support Windows 7 not waking up from sleep mode properlyI have been using sleep mode for a while. Until recently, I had to re-install my OS due to some troubleshooting and hardware issues.

At first, I too didn't know VirtualBox had something to do with it, since nothing pointed to it. Code: BugCheck 9F, {3, fffffa8006a54060, fffff800021ba518, fffffa800b148010} *** WARNING: Unable to verify timestamp for AE1200w764.sys *** ERROR: Module load completed but symbols could not be loaded for AE1200w764.sys Probably caused by You must contact the nVIDIA/MS support."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ Proposed as answer by Leon Liu - MSMicrosoft employee, Moderator Monday, February In addition to the reported kind of crash, I've got another BSODs caused by VBoxNetAdp driver.

B85M-D3H Memory Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz) Graphics Card 2047MB GeForce GTS 450 (ZOTAC International) Sound Card Onboard (Realtek High Definition Audio) Monitor(s) Displays LG Flatron E2040T I tried both the 260 nvidia driver and the 266 nvidia driver and both got me the same results you are getting. Hi DIGGY416, from your log... "This appears to be a typical software driver bug and is not likely to be caused by a hardware problem." first backup your files on to My System Specs System Manufacturer/Model Number Digital Storm Custom built OS Windows 7 Professional x64 CPU i7 920 OC to 3.2GHz Motherboard EVGA Memory 6GB DDR3 (speed unknown) Digital Storm certified

I got the same BSOD when trying to hibernate computer with VB 4.2.5-82251 installed. Unfortunately, I've had no access to the computer where all this happened.