Windows 10: Random Restarts when playing games. Kernel errors (41) but no dump.

Upgraded from Windows 8.1 Pro to 10 Pro.
I think I took care of the update bug so I don't believe it is the issue.

Updated GForce Drivers after using DisplayDriverUninstaller.
SSD C: Drive firmware updated.
Ran Memtest86+ on each stick for 8 passes with no errors.
Updated audio drivers.
Updated network drivers.
Updated SATA drivers.
Ran Windows Defender Full Scan with no findings.
Ran Malwarebytes Full Scan with no findings.

It happens when I play games. I ran one 3DMark test with no issues. Ran it again and it reset as it normally does. I ran Furmark for 5 mins with no issue.

:)

 

EVENT 1001 - BugCheck - The computer has rebooted from a bugcheck.

Lately my computer has been restarting out of nowhere at random times, doesn't show a BSOD it just black screens and restarts.

This is the error that shows on eventviewer:

Event 1001, BugCheck

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffab0182114038, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\010618-40156-01.dmp. Report Id: 3e609480-61a7-4589-a40c-3f315d745e16.

and the critical error is:

Event 41, Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The two instances I remember it crashing was when playing a game and when downloading a file.

Haven't made any changes into hardware/software lately.

Shared items 1-6-2018

 

Kernel Power 41 (63) error after updating to win10 from win7

Bump for solution

 

Just ran FurMark for a while with no issues. Seems I can run FurMark with no issue but my games prompt a reset within a couple minutes of starting.

 

Hi mizzer,

The suddenly restart problem is not a BSOD.
The BSOD section is for those who are experiencing BSOD's.
The problem is more a performance problem, please create a new thread at the Performance and Maintenance section

 

Hi axe0,

Perhaps you're right. However I did run Driver Verifier on my own and received two blue screens. One was a violation detected at rzpngrk.sys, I uninstalled the Razer driver and software.

The second one was UNEXPECTED_KERNEL_MODE_TRAP. I had to restore in order to boot.

So, I'm wondering: is the other section where my issue belongs or does it fit here?

Thanks!

 

The thread fits here, because of the BSOD's.

Are the dump files in the attached zip file?
If not, please use the tool again and upload the zip file.

 

They should be. I ran the tool after the BSOD's.

thanks

 

Only from the razer software is a dump, the other is likely removed with restoring.

 

Should I run Driver Verifier again and send a new dump?
Could you post the directions for Driver Verifier, please? Last time I got caught in a loop and could only get back through Restore.
Thanks.

Also, would there be any benefit to performing a fresh install of Windows 10 pro? I'm almost at that point where the headache of re-installing outweighs the headache of troubleshooting. *Sad

 

The best benefit of a clean install is you don't have the bugs that come with an upgrade.
A lot of people are doing a clean install, right after the upgrade to avoid bug problems.

There are a few common causes with the crash "UNEXPECTED_KERNEL_MODE_TRAP".

• hardware failure
• software problem

There is another one, but I don't fully understand it yet.
The hardware failure is the most common cause, but yet they can be fixable with updates from Microsoft.

This might seem logic as a lot of BSOD's are being caused by either hardware or software, but there are also BSOD's where a setting is causing it.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Thanks axe0, I appreciate the help. I will tinker a bit and report back.

 

Alright, just nuked, paved, and replanted: a fresh install of Windows 10 pro.

And I'm still getting the shut down and restart.

I included the pre-Driver Verifier dump here. I'm going to run DV and then download that dump soon.

 

Latest dump file. Driver Verifier is running.

I couldn't get it to blue screen but it did restart. In this instance, it occurred after launching 3DMark.

 

Please check the 3.3V, 5V and 12V values in the BIOS.
Please include your PSU and cooling system in your specs.
Please go to this site and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs: