|
Problem description: I recently built a new PC, and it runs great -- the only issue is, if I've left it in sleep mode for more than a few minutes (think 5-10ish), when I take it out of sleep mode it's as if it rebooted. Now, Windows 10 loads off my SSD in about 8 seconds so this isn't the HUGEST deal, but I'm afraid of losing data due to a badly timed restart event. Heck, the only reason I can tell that my computer crashed rather than hibernated is that after this happens, no browser windows or programs that I'd previously had active are open. Note that I can still "wake" the computer with my mouse/keyboard, and my tower acts as though it is in sleep mode (flashing power light) before I do anything. The entry in the event log shows the crash as early into the sleep cycle, rather than when I wake it up. Attempted fixes: Went into the event viewer; the coinciding error is as follows: code:Recent changes: None. This has been going on since I first got my build up and running last month. -- Operating system: 64-bit Windows 10, all latest updates installed. System specs: Mobo: ASRock Fatal1ty H97 Performance RAM: Crucial Ballistix Sport 16GB Kit (8GBx2) DDR3 1600 MT/s Video Card: MSI GTX 970, no overclock CPU: Intel Core i7-4790 SSD: Samsung EVO 850 500GB PSU: EVGA 750W 120-G1-0750-XR RT Location: USA! USA! I have Googled and read the FAQ: Yes Not a Children fucked around with this message at 21:58 on Sep 22, 2015 |
#
?
Sep 22, 2015 21:50
|
|
|
|
| # ? May 3, 2024 12:50 |
|
|
I had a similar problem to this and it turned out to be a bad ethernet driver for Windows 10. After disabling the adapter I haven't had any issues since.
|
|
#
?
Sep 22, 2015 22:33
|
|
|
0x0000000a is a memory allocation error but it can be caused by bad hardware or a bad driver. Some devices don't like coming out of sleep (I can relate). It could very well be a network driver as Angelwolf said. Download WhoCrashed? from here: http://www.resplendence.com/downloads install it and hit the "Analyze" button. WhoCrashed generally gives more specific information on the crash.
|
|
#
?
Sep 22, 2015 22:41
|
|
|
Thanks for the advice! WhoCrashed? identified a controller driver that my brother installed as the culprit. I'll uninstall it and report back tomorrow as to whether the crashing keeps up.
|
|
#
?
Sep 22, 2015 23:03
|
|
|
The problem persists! The new Bugcheck code: 0x3B. Seems like it's more memory-related stuff. I've tried disabling the ethernet port (I use a PCI-e wireless card) just now as Angelwolf suggested, but past that I'm sort of at a loss. WhoCrashed suggests that FltMgr.sys is causing the issue, but as far as I can tell that's an integral Windows process?
|
|
#
?
Sep 24, 2015 02:07
|
|
|
Not a Children posted:The problem persists! The new Bugcheck code: 0x3B. Seems like it's more memory-related stuff. I've tried disabling the ethernet port (I use a PCI-e wireless card) just now as Angelwolf suggested, but past that I'm sort of at a loss. WhoCrashed suggests that FltMgr.sys is causing the issue, but as far as I can tell that's an integral Windows process? Can you uninstall your USB3.0 drivers and report back? Also, is your computer set for hybrid sleep?
|
|
#
?
Sep 24, 2015 17:22
|
|
|
I suppose I could get rid of my USB 3.0 drivers, but I use them all the time... I'll give it a shot, in any case. Not sure about the hybrid sleep. I'll check when I get home from work. Didn't even know it was a thing, but it makes total sense that it might be causing the issue.
|
|
#
?
Sep 24, 2015 18:42
|
|
|
Update! Uninstalling the USB Drivers did not do anything. I disabled hybrid sleep and hibernate modes, and now I have a neat new problem. Now, when the computer comes out of sleep mode, it powers up for about 2 seconds, doesn't output any display, dies (seems to just shut off on its own), then starts back up (also on its own)! So, the problem persists. Everything I google for seems to get intermingled with other unrelated resets-during-sleep errors. The latest error in the event viewer was Bugcheck 7e, which apparently corresponds to video drivers. It looks like there's an update for my 970, so I'll install that and hope for the best.
|
|
#
?
Sep 30, 2015 03:13
|
|
|
It's got to be one of the devices. The reason I said USB was because I've had that exact problem when coming out of sleep, and it was the USB3.0 drivers. Was this a clean install of Windows 10? There could also be a hardware issue, possibly PSU. How long did you run Memtest?
|
|
#
?
Sep 30, 2015 16:02
|
|
|
Gotcha. It was a clean install of Windows 10, so there wouldn't be any bloatware causing issues. I'm going to play round robin with disabling my drivers to see if any particular combination works. When you disabled your USB drivers, were you able to use a different set of drivers (old or otherwise) to get them up and working again? It'd be a shame to lose use of those 3.0 ports... I ran memtest over the course of about 2 hours. I'll run it again before I go to sleep tonight.
|
|
#
?
Sep 30, 2015 20:18
|
|
|
Not a Children posted:Gotcha. It was a clean install of Windows 10, so there wouldn't be any bloatware causing issues. I'm going to play round robin with disabling my drivers to see if any particular combination works. When you disabled your USB drivers, were you able to use a different set of drivers (old or otherwise) to get them up and working again? It'd be a shame to lose use of those 3.0 ports... I had swapped out my motherboard/CPU (P67 to Z97) but was using the previous Windows 7 install. Everything else worked fine but the USB3.0 drivers would cause a blue screen coming out of sleep. I've also had issues with Intel's 3.0 drivers on other machines so it was worth a shot. The fact that you are getting so many different types of blue screens is odd, which is why I think maybe PSU/memory.
|
|
#
?
Sep 30, 2015 22:41
|
|
|
Ran Memtest overnight, for a total of 18 hours; 0 errors, so my memory is solid, looks like. I'm at the end of my rope here. I'm pretty close to just disabling sleep mode altogether. I'll mess with the BIOS settings a bit later on today. If nothing pans out, I'll wipe and install a fresh copy of windows 10 as a last ditch. If that doesn't work, well... I'll play musical chairs with all my hardware to isolate the source. Thanks for all the suggestions along the way, Gorson.
|
|
#
?
Oct 6, 2015 19:14
|
|
|
Not a Children posted:I'm pretty close to just disabling sleep mode altogether. With a system like that, and an SSD, you can easily afford to disable sleep.
|
|
#
?
Oct 7, 2015 12:59
|
|
|
|
| # ? May 3, 2024 12:50 |
|
|
I fixed my problem by disabling sleep and putting hibernate on a short timer. Hibernate doesn't appear to trigger the same issues for whatever voodoo hardware/driver reason. Now I get the best of both worlds, crash-free! Plus, I don't have to cover up the LEDs on my case at night anymore.
|
|
#
?
Oct 14, 2015 19:01
|
|