BSOD after about 10 minutes of playing high demanding games

Code:

BugCheck 1A, {41793, fffffe010f4bcbf8, 180, 17f}

Probably caused by : memory_corruption

Code:

BugCheck 1A, {41792, ffff8180f6f84110, 100000, 0}

Probably caused by : memory_corruption ( ONE_BIT )

Code:

BugCheck 1A, {41793, ffffc100a603aff8, 200, 1ff}

Probably caused by : memory_corruption

Code:

BugCheck A, {ffffea8000000000, 2, 0, fffff802de69dd1e}

Probably caused by : memory_corruption

Code:

BugCheck 1A, {41792, ffff9d8000009388, 4000000000, 0}

Probably caused by : memory_corruption ( ONE_BIT )

Code:

BugCheck 1A, {41793, ffffe980000b3098, 14, 13}

Probably caused by : memory_corruption

Code:

BugCheck 1A, {41792, ffff85001f24d388, 10000, 0}

Probably caused by : memory_corruption

There are 7/7 minidump debugged indicating memory.
Sometimes the results are indeterminate.
Having 8 or more runs per the above link is the minimum used to rule out memory problems. It sometimes takes runs in the teens to find memory problems.

Memory problems. - Microsoft Community

MemTest86+ - Test RAM Windows 10 BSOD Tutorials

How to Upload and Post Screenshots and Files at Ten Forums Windows 10 Tutorials

Let us know about clean boot and performance. Also bsod frequency not in and it clean boot.
After reviewing the up coming posts we may advance to stress testing:


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials


SpeedFan - Access temperature sensor in your computer
GIMPS - Free Prime95 software downloads - PrimeNet
http://www.ozone3d.net/benchmarks/fur/

Hi,

I'm currently not at home, but I started a memtest this morning with 8 runs so hopefully I will have the results later.

As for the stress test I used IntelBurnTest and got those result when testing with the high settings :

Time (s)	Speed (GFlops)	Result
145.483	52.9803	3.152469e-002
145.178	53.0915	3.152469e-002
145.748	52.8837	3.152469e-002
145.771	52.8757	3.152469e-002
145.786	52.8702	3.152469e-002
145.689	52.9054	3.152469e-002
145.673	52.9111	3.152469e-002
145.727	52.8914	3.152469e-002

When I tried the "max" settings, I had a BSOD with the memory management error code.

I will try the programs you advise as soon as I can.

When the memtest86+ completes 8 or more runs please post an image into the thread.

Alright, Im home and my memtest86 did actually 14 passes

Attachment 140282

for the gpu benchmark i did for 1h but I didnt know that if I closed it it wouldnt give me the log. I did once again for 10 min and it gave me this (No bsod for all this time).

Attachment 140288

Attachment 140288

I will try running the CPU stress test

For the clean boot performance, it runs fine but I dont see any difference when Im in clean boot or not when I play a game. Right now everything works perfectly (not in safe mode).

Ive been running Prime95 for almost 4 hours now, it isnt done yet but no errors to report.

Which method did you choose to monitor temperatures?
Please confirm:
1) CPU stress test with prime95 continued to run without problems
2) GPU stress test with Furmark ran without problems....What was the high temperature?
3) The stress testing was done using clean boot and there were no bsod during any of the stress testing.
4) Memtest86+ ran for 13 passes and found no memory problems.

If all of the above is correct the next step is stimulating the drivers using windows driver verifier to find the misbehaving drivers.
Before using windows driver verifier backup your files and create a restore point.
You must be comfortable navigating the Windows recovery or advanced troubleshooting menu.
Windows driver verifier is designed to repetitively produce bsod until it is turned off or until all misbehaving drivers have been fixed.
In order to turn windows driver verifier off you will need to get to the windows advanced troubleshooting menu. Then within the menu you must navigate to startup options (not startup repair). When in startup options it will restart and you will select #6 safe mode with command prompt and type or copy and paste this command: verifier /reset
Then you will reboot to the desktop.
When on the desktop you will run 2 software programs to identify the bsod: Bluescreenview and Whocrashed
Each software program may produce different information.
You will then uninstall the driver or the application.
Then you have a choice. You can restart driver verifier and look for the next misbehaving driver. Or you can install a replacement driver and restart driver verifier. The process will continue until there are no longer any bsod. Then you will run windows driver verifier for an additional 36 hours under typical use. If there are no longer any bsod you then have fixed the misbehaving driver(s)/application(s) and you have performed preventative maintenance.

Before using windows driver verifier you will want to change settings in the startup and recovery settings. You will want time to view the bsod. When using windows driver verifier there will be a stop code. The typical stop code is driver verifier detected violation. Sometimes it will display the misbehaving driver in this form: *.sys. If you see the driver identified please record it.
This is information on how to set the windows startup and recovery settings:
BSOD Finding and fixing them - Microsoft Community

To setup and start using Windows driver verifier use the settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Practice navigating through the Windows advanced troubleshooting menu by typing or copy and pasting this command into administrative command prompt: shutdown /r /o /f /t 00

When you have time to troubleshoot the bsod you will turn on Windows driver verifier by typing verifier in the left lower corner search.



Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed

I totally forgot to mesure the temperature with a program you suggest for the CPU benchmark.

1) No problems with the run, no BSOD.
2) Temperature was normal (from the program I saw) and in no case it went more than 55-60.
3) Clean boot was used yes and no problem at all.
4) Memtest ran 13 times without any problems.

Ill come back for the rest later and will update you.

thanks for the help by the way, its really appreciated.

On your drives run one of these SMART tests and post images into the thread:

http://crystalmark.info/software/Cry...o/index-e.html
http://www.hdtune.com/
https://www.hdsentinel.com/

SDD test

Attachment 140381

HD test
Attachment 140382

Smart test
Attachment 140383

Im doing the instructions of post #16 right after this post.

I ran the verifier and got a BSOD right on the reboot. Here's the report by whocrashed

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 2017-06-20 6:00:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\062017-5531-01.dmp
This was probably caused by the following module: rzpmgrk.sys (rzpmgrk+0x208)
Bugcheck code: 0xC4 (0x2004, 0xFFFFA88B15B3DEE8, 0xFFFFF80C68AD0208, 0xFFFFE181207CE6E8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\rzpmgrk.sys
product: RZPMGRK
company: Razer, Inc.
description: Razer Overlay Support
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rzpmgrk.sys (Razer Overlay Support, Razer, Inc.).
Google query: Razer, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 2017-06-20 6:00:37 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rzpmgrk.sys (0xFFFFF80C68AD0208)
Bugcheck code: 0xC4 (0x2004, 0xFFFFA88B15B3DEE8, 0xFFFFF80C68AD0208, 0xFFFFE181207CE6E8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\rzpmgrk.sys
product: RZPMGRK
company: Razer, Inc.
description: Razer Overlay Support
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rzpmgrk.sys (Razer Overlay Support, Razer, Inc.).
Google query: Razer, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION

Im trying to find a way to delete rzpmgrk.sys but the programs is still running somewhere. I deleted all the files or programs that were related to Razer (I changed my mouse too) but I still cant delete it.