Diagnosing my BSOD

Beautiful People

Honorable
Jan 1, 2014
10
0
10,510
Build: Custom
OS: Windows 10 (64)
Mother board: Asus A88X-Pro
RAM: 18GB
Processor: AMD A10-6700 APU 3.70 GHz
Graphics Card: GeForce GTX 660

Put your thinking caps on for this one!

Problem Description: My computer (seemingly) randomly BSOD

Attempted resolutions: Destructive restore; Completely wiped the drive and reinstalled the OS.

Current Status: There are very few programs install that are very unlikely to be the cause. I suspect it is a driver, but, everything can be working fine for hours before the BSOD.

Did I capture the most recent crash information, No. I have been researching how to find, read and understand event viewer and the C:\WINDOWS\MEMORY.DMP file. Unfortunately I am have trouble going forward. Can anyone assist me in identifying my BSOD and implementing a resolution.

 
Solution
I'm interested to see if you can come up with a solution. I also have a GTX 660 and after upgrading to Windows 10, have had random blue screens. The Nvidia driver seems to be the cause for me. I pulled out the card and am currently running a GT 610 on the same drivers without issue.


Thats a great question. There are many BSOD utilities "Blue Screen view", what is it and how can I navigate to it. Assuming is not called Blue screen view in start up
 
For future readers, these next few steps have helped me identify whether or not the problem was hardware or software. Before proceeding please not this may not work for you but hopefully it helps and PLEASE CREATE A RESTORE POINT.

The following utilizes DRIVER VERIFIER rule out drivers.

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 10 & 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Swipe mouse top-right of screen to bring up Charms |click on "Search" | type create | select "Create a Restore Point"

2. Run Driver Verifier -
- Windows 10, 7 & Vista - START | type verifier
- Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier

Make these selections -
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -
Special Pool
Force IRQL checking
Pool Tracking
Deadlock Detection
Security Checks (new as of Windows 7)
Miscellaneous Checks
Power framework delay fuzzing (new as of Windows 8)
DDI compliance checking (new as of Windows 8)
4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot

(After doing this my computer crashed upon the next two reboots. I was very happy to have an idea of the likely cause. I will post more progress as I go along)
 
I'm interested to see if you can come up with a solution. I also have a GTX 660 and after upgrading to Windows 10, have had random blue screens. The Nvidia driver seems to be the cause for me. I pulled out the card and am currently running a GT 610 on the same drivers without issue.
 
Solution



Thank you for the feed back. I think my problem is leaning toward my Razer gaming mouse. During the induced BSOD rzpmgrk.sys was flagged. And it makes since as I have always had and used it. Regardless to whether or not it turns out to be the mouse I will be sure to let you know. If its not I will investigate my NVidia drivers as they also were apart of the diag tho not flagged. (BTW this may run into tomorrow about 8 p.m. est I have to get some rest soon so stay posted)

Update - I just ran the diagnostic tool again (DRIVER VERIFIER) this time I "DID NOT" select my mouse to be verified. As a result the system rebooted perfectly fine with no errors validating the mouse as the problem. I could run it one more time and only select the mouse but at this point it probably redundant.
 
Thank you for following this post, and to all that may come by this, I hope this is some what useful. I have updated my drivers for this device. I will run another test shortly, in the event it fails I will remove the drivers completely. In addition, even though I have this pretty much wrapped up, there is still a chance that there is faulty hardware causing the problem. I would advise to others to run diags on the ram. Reason being is if there's a page fault when performing operations, it can cause similar issues.
Well, thats all ladies and gents. Please message me with any questions, I will be happy to provide any help I can.

Update - I ran the test (driver verifier) after updating the software and it worked, no BSOD!