Windows 10: BSOD after about 10 minutes of playing high demanding games

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.
Resplendence Software - WhoCrashed, automatic crash dump analyzer

 

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
HD Tune website
Hard Disk Sentinel - HDD health and temperature monitoring

 

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

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.

 

Please post an updated zip or a new zip file.

 

Attachment 140392

I tried playing the witcher 3 while being in "verifier" mode and, apart from the fact that the game is kinda sluggish (which its probably due to the verifier) but there was no BSOD.

In my last run of "verifier" I didnt include rzpmgrk.sys and there was no BSOD on boot. I still didnt find a way to delete the driver.

 

Sometimes you can be mislead by the minidump debugging.
Did you also use Bluescreen view?
Please report the findings with it.
If you had not used it you can download and install it now and look back at the prior events.

One of the dumps, the last one, was only 1 KB so it did not create a proper zip file.

Of the 4 remaining on 4/20/2017 using Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64 it produced this debugging:

Code: BugCheck C4, {2000, fffff8096b2226e5, 0, 6e657a72} *** WARNING: Unable to verify timestamp for rzendpt.sys *** ERROR: Module load completed but symbols could not be loaded for rzendpt.sys Probably caused by : memory_corruption[/quote] Code: BugCheck C4, {2000, fffff80a828226e5, 0, 6e657a72} *** WARNING: Unable to verify timestamp for rzendpt.sys *** ERROR: Module load completed but symbols could not be loaded for rzendpt.sys Probably caused by : memory_corruption[/quote] Code: BugCheck C4, {2004, ffffa88b15b3dee8, fffff80c68ad0208, ffffe181207ce6e8} Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+6b )[/quote] Code: BugCheck C4, {2000, fffff808973626e5, 0, 6e657a72} *** WARNING: Unable to verify timestamp for rzendpt.sys *** ERROR: Module load completed but symbols could not be loaded for rzendpt.sys *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote]
You had submitted the whocrashed results. What was seen using bluescreenview?


Code: Event[3622]: Log Name: System Source: Service Control Manager Date: 2017-06-20T19:10:44.450 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-DNTIQO6 Description: The Razer Game Scanner Service service failed to start due to the following error: The system cannot find the file specified.[/quote]

Code: Event[3449]: Log Name: System Source: Service Control Manager Date: 2017-06-20T18:02:32.141 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-DNTIQO6 Description: The following boot-start or system-start driver(s) did not load: AFD AsrAppCharger cdrom dam Dfsc FileCrypt GpuEnergyDrv NetBIOS NetBT npsvctrig nsiproxy Psched rdbss tdx vwififlt WdFilter[/quote]

If there are more bsod please post an updated zip.

 

Which mouse manufacturer are you using?

 

Are you using any of these products: Official Razer Support

 

Last BSOD with Bluescreenviewer

Attachment 140393

Previous one

Attachment 140394

Here is the zip once again. Im not sure if it worked.

Attachment 140395

Should I keep running verifier for the time being (36 hours like you recommended it?). I can use my computer, but it seems really sluggish, even when im not playing any games.

Also, should I start looking for a new mouse? Or try to reinstall the Razer drivers and see if the BSOD are still happening?

 

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time 062017-5531-01.dmp 2017-06-20 6:00:37 PM DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002004 ffffa88b`15b3dee8 fffff80c`68ad0208 ffffe181`207ce6e8 rzpmgrk.sys rzpmgrk.sys+208 x64 ntoskrnl.exe+16c3f0 C:\Windows\Minidump\062017-5531-01.dmp 12 15 15063 787,100 2017-06-20 6:02:32 PM 062017-5562-02.dmp 2017-06-20 5:26:37 PM DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002000 fffff809`6b2226e5 00000000`00000000 00000000`6e657a72 rzendpt.sys rzendpt.sys+26e5 x64 ntoskrnl.exe+16c3f0 C:\Windows\Minidump\062017-5562-02.dmp 12 15 15063 720,140 2017-06-20 5:28:29 PM 062017-5500-01.dmp 2017-06-20 5:05:36 PM DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002000 fffff808`973626e5 00000000`00000000 00000000`6e657a72 rzendpt.sys rzendpt.sys+26e5 x64 ntoskrnl.exe+16c3f0 C:\Windows\Minidump\062017-5500-01.dmp 12 15 15063 753,884 2017-06-20 5:07:55 PM 062017-5546-01.dmp 2017-06-20 4:41:16 PM DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002000 fffff80a`828226e5 00000000`00000000 00000000`6e657a72 rzendpt.sys rzendpt.sys+26e5 x64 ntoskrnl.exe+16c3f0 C:\Windows\Minidump\062017-5546-01.dmp 12 15 15063 817,076 2017-06-20 4:44:06 PM
html version


As for my mouse, Im using the Deathadder chroma normally, but I switched to a logitech for time I would be verifying the drivers. I tried to delete all Razer files but two drivers doesnt seem to be erasable (rzpmgrk.sys and rzpnk.sys).

 

Viewing bluescreenview it displays:
rzpmgrk.sys and that is missing from the drivers log
rzendpt.sys is on the drivers list: rzendpt rzendpt rzendpt Kernel Manual Stopped OK FALSE FALSE 0 24,576 0 2016-06-15 8:43:23 PM C:\Windows\system32\drivers\rzendpt.sys



rzpmgrk.sys Razer Overlay Support Driver Official Razer Support
rzendpt.sys Razer RzEndPt driver Official Razer Support
Open file explorer and use the hide/unhide feature. Search again for any files. Do not delete, just search.
Also download and install everything (everything search or search everything). It will index everything on your internal and external drives. The as you type characters you will see instantaneous results. The more characters you type the narrower the results. You can have it start on boot or have it off and use it when you need it. I suggest the latter to have fastest boot times and best numbers on task manager.


Turn off Windows driver verifier and see if you have spontaneous bsod.
It may need to be run again to find the misbehaving driver(s).




Please update on what you find with the various search methods.

 

Were you previously using Razer products?
If so which ones?


When you searched where you able to find them but not delete them or were you not able to find them?
If you found them and were not able to delete them was there an error message?