Problems with Windows 8.1 kernel

[the_red_spirit]

So I recently reinstalled Windows 8.1 on my PC and I have a problem. My PC crashes and reboots. Mostly when PC just started or when waking up from sleep. I have some crash dumps and downloaded program called "whocrashed" to open those. I opened those files and program shows me this information:
On Sat 2018-02-10 19:47:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021018-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE0000A76D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 2018-02-07 01:54:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020718-17234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE001403028F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 2018-01-31 06:56:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013118-15906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE000735761C8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Seems like persisting error and after it says that drivers are alright I don't know what to do. I ran OS disk check and it didn't found anything. I'm not completely sure if it's software problem either, but it would be nice to hear what parts I should suspect then.

 

[USAFRet]

MERGED QUESTION
Question from the_red_spirit : "Problems with Windows 8.1 kernel"

So I recently reinstalled Windows 8.1 on my PC and I have a problem. My PC crashes and reboots. Mostly when PC just started or when waking up from sleep. I have some crash dumps and downloaded program called "whocrashed" to open those. I opened those files and program shows me this information:
On Sat 2018-02-10 19:47:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021018-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE0000A76D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 2018-02-07 01:54:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020718-17234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE001403028F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 2018-01-31 06:56:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013118-15906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x59CEA5)
Bugcheck code: 0x124 (0x0, 0xFFFFE000735761C8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Seems like persisting error and after it says that drivers are alright I don't know what to do. I ran OS disk check and it didn't found anything. I'm not completely sure if it's software problem either, but it would be nice to hear what parts I should suspect then.

 

[the_red_spirit]

Crashed again while waking up from sleep. Screen was blank, but it kept working until I I heard BIOS beep (indication of it starting). When it started it says that computer encountered problem.

 

[the_red_spirit]

I guess I will look into my BIOS configuration. The power state section.

My PSU is this:
https://bulk.fsp-europe.com/fsp700-50arn-88

Even if ErP is enabled it should work fine.

 

[the_red_spirit]

So I disabled S3 power state and PC works fine, just that now in sleep state fans spin and LED blinks. I would still wish to fix this issue

 

[the_red_spirit]

I reflashed my mobo's BIOS from version F4b (beta version) to F3 (latest non-beta version). I will see how everything works now.

 

[Paul NZ]

Upload the small dmp files somewhere then post the link. Yup not a good idea to use beta bioses

These can be buggy

 

[the_red_spirit]

Upload the small dmp files somewhere then post the link. Yup not a good idea to use beta bioses

These can be buggy

I hope these will work:
http://www83.zippyshare.com/v/WRT975wH/file.html
http://www83.zippyshare.com/v/7TQO9JeJ/file.html
http://www83.zippyshare.com/v/9e0V5Wpt/file.html
http://www83.zippyshare.com/v/mDn8W0Dx/file.html

 

[Paul NZ]

I would run tdsskiller. See if you've got rootkits. Since ntfs.sys is crashing with 0x124 stop errors

https://usa.kaspersky.com/downloads/tdsskiller

I would check your cpu as well. It may not be installed properly, it maybe overheating, it maybe faulty

 

[the_red_spirit]

I would run tdsskiller. See if you've got rootkits. Since ntfs.sys is crashing with 0x124 stop errors

https://usa.kaspersky.com/downloads/tdsskiller

I would check your cpu as well. It may not be installed properly, it maybe overheating, it maybe faulty

I downloaded tdsskiller and it found nothing.

As for CPU it's really unlikely that it's not installed properly. First of all PC was assembled in 2014 and worked fine. I also have very heavy cooler, Scythe Mugen 4 PCGH. So the only thing I could imagine here is that somehow that cooler put huge pressure and pulled out part of CPU, but it's very unlikely. Overheating is also very questionable as I have really beefy CPU cooler and I could probably perfectly working system even without thermal paste. Too bad there's one thing I never said. My specs are:
Gigabyte 78lmt-s2p rev. 5
AMD FX 6300
2x4gb DDR3 RAM

In past I tried overclocking CPU and I sorta didn't knew much about OCing. I thought it was a good idea to OC 95W CPU on 95W mobo with only 3+1 phase design. That mobo is really bad for OCing and I needed huge voltages to achieve my highest OC of 4.375 GHz. Then I run out of voltage adjustment and if I recall correctly that was around 1.7 volts. CPU itself didn't get hot (only around 50s), but my problem was VRMs. They were hot, extremely hot. I recorded max temperature on the back of my mobo and it was 147 degrees of Celsius. I burned my finger a bit. Then I understood that I had to stop OCing with that board. And only after lots of time I saw that my mobo is a bit brown near CPU. Not sure if it will have long term effects, but it may have those. Everything worked well since then, so I think there are no problems on the side of hardware. PC was upgraded several times too. Latest upgrade was GTX 650 Ti to AMD RX 560. After my upgrade I reinstalled Windows or rather downgraded from 10 after lots of issues with PC stability. Mostly because I downloaded Office 95 from shitty source and it wrecked my Windows files. For one month I have been trying to revive Windows with no luck. Due to personal reasons I reinstalled 8.1, but not 10 or maybe more for hardware support (No drivers for Windows 10 for some motherboard components). The only bad thing I saw with 8.1 is that AMD doesn't support RX 560 on 8.1. So I installed Windows 7 driver. Not sure if it's drivers problem, but in UT 2004 my gameplay has some stutter-alike problem. It gets good FPS, but PC sort of lock up for small fractions of time. It's not FPS drop, but something weirder. Call of Duty 2 doesn't seem to have this problem. So I don't have a clue why is that. Juiced that I have tried also suffers from that momentary locking up problem, but Juiced overall is buggy POS and in my experience doesn't work well on many other normal functioning computers. As for safety I cheap out, but I don't ignore it either. I have three programs:
Avast free antivirus (best free antivirus security)
ZoneAlarm free firewall (one of the best free firewalls)
Spybot Search and Destroy 2.6 (best free active anti-malware software)
Since they are all different purpose software, they shouldn't conflict with each other or at least I think so. And for the end of this story, yesterday I ran latency monitoring software DPC latency checker to see if there are problems while playing UT 2004. Too bad I found nothing and maximum latency recorded was 1951µs. Normally it stays at around 1000. I tried to turn off HPET as I read it may reduce latency and increase FPS, but it had another effect on this system. It actually increased latency, so I turned it on in BIOS. So besides sleeping issue PC doesn't have any other issues and after BIOS downgrade to F3 I haven't seen problems, but that needs more longer term checking and due to you noticing problems in minidump files I would want to fix issues I may not see.

Glorious picture of overclocking fail:

 

[the_red_spirit]

After BIOS update sleep function seems to be working fine.

 

[the_red_spirit]

I went back to Windows 10 and sleep crashing issue is back there too.

 

[the_red_spirit]

PC crashed when I was browsing net and I got crash minidump file. Surprisingly all information is exactly the same as it was in Windows 8.1. Same thing crashed. So maybe it's a hardware thing, if it is then at what I should look at? Yet I'm starting to be suspicious about my security software.

 

[the_red_spirit]

I would run tdsskiller. See if you've got rootkits. Since ntfs.sys is crashing with 0x124 stop errors

https://usa.kaspersky.com/downloads/tdsskiller

I would check your cpu as well. It may not be installed properly, it maybe overheating, it maybe faulty

Can you help me further?

 

[the_red_spirit]

I think I found problem. It's my WiFi adapter called TP-Link TL-WN721N. It always had dodgy drivers and stability issues, just that previously I could see BSODs, but for some reason I don't now, so it added some mysterious hardware failure effect. Not sure how this system will fare in long term, but currently it seems promising. Even latency is much lower with much less spikes.