The Windows Subsystem system process terminated unexpectedly

Ithilion

Distinguished
Sep 18, 2011
12
0
18,510
I'm reposting this in the Windows 7 section because it's no longer Overclocking related, as I've reverted to stock settings and this keeps happening.

I'm experiencing the weirdest BSOD in my entire time with Windows.

I don't have a screenshot of my error but this looks pretty much the same:
4Kmp2.png


The strange thing is that this BSOD seems to be happening after the system has been idle for some time (20 minutes to a couple of hour), but it doesn't happen all the times; in fact, it happens very rarely (maybe one or two times a month on normal use). I'm able to reproduce it only by repeatedly letting my system go idle but i could not find any additional triggering information.

Event Viewer is also not helping me at all, all i ever found there about this is the exact time the BSOD kicked in. Additionally, no mini-dumps are collected for this BSOD even though they're working (forced another BSOD to test).

Here some system info

- OS: Windows 7 Ultimate x64 SP1 (all Windows updates installed)
- MOBO: ASUS z87 Deluxe
- CPU: Intel 4770k (stock settings, all C states activated, EIST activated)
- RAM: 16 GB g.skill TridentX
- VGA: Nvidia GTS 250 (with latest drivers)
- Main drive: Samsung 830 256GB

The CPU is watercooled and idle core temperatures (which is when this BSOD happens) are around 25-28 °C.

I'm tempted to do a format and OS reinstall, but before going this drastic i would try to understand what is causing this.
 
Solution
G
Sorry I didn't fully read your description the first time. The only thing that it really could be is that your computers power supply is incompatible with haswell.f Just try overclocking your processor to 4.4 and then the vcore to 1.22. Also set your voltage to override, and not adaptive. I'm pretty damn sure that is your issue. You probably got mislead by whoever told you the overclock was the issue.
G

Guest

Guest
The last time that I had that happen to me it was a ram issue. Just run memtest86 off a usb for about 20mins and see
 
G

Guest

Guest
Sorry I didn't fully read your description the first time. The only thing that it really could be is that your computers power supply is incompatible with haswell.f Just try overclocking your processor to 4.4 and then the vcore to 1.22. Also set your voltage to override, and not adaptive. I'm pretty damn sure that is your issue. You probably got mislead by whoever told you the overclock was the issue.
 
Solution