Constant BSODs, Including on Driver Verify Boot - Windows 7 x64

E

eluros

New member
Joined
Apr 4, 2015
Posts
4
Hey, all,

Thank you in advance SO MUCH for your help!

I built this PC ~7 years ago, but it's lasted me great until 2 or three years ago when it started getting BSODs. It's now BSOD'ing constantly, multiple times ago.

About a month ago, I did a fresh install of Windows; that did not resolve the issue.

I tried running Driver Verifier, and get a BSOD immediately on boot.


I get a variety of BSODs constantly, ranging from IRQL_LESS_THAN_OR_EQUAL to USB_BUGCODE bsods.

I've tried running Memtest86 on each stick of RAM individually for hours. No BSODs, although there's always the chance that it needs to run longer.

I've tried running the Windows Memory Diagnostic, although not on each individual stick of RAM.

View attachment SysnativeFileCollectionApp.zip

I would be tremendously appreciative of any assistance you all can provide. Thank you so much! Let me know what else you need from me.




EDIT:
· OS - Windows 8.1, 8, 7, Vista ? Windows 7
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 7

· Age of system (hardware) ~7 Years
· Age of OS installation - have you re-installed the OS? Reinstalled in May, so 1 month

· CPU: i7 920
· Video Card GTX 460 SLI
· MotherBoard - (if NOT a laptop) x58 EVGA
· Power Supply - brand & wattage (if laptop, skip this one) Unsure; let me know if you need this.

· System Manufacturer Custom built
· Exact model number (if laptop, check label on bottom) Custom built

· Laptop or Desktop? Desktop
 
Re: Constant BSODs, Including on Driver Verify Boot

Let me know what else you need from me.
Click to expand...

You have a stack of 50 dollar bills laying around?

Code: 
3: kd> .bugcheck
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`00000058 fffffa80`07ecdb10 fffff880`0aa73430

A driver referenced a user handle as kernel-mode, which is a no-no.

Code: 
3: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`0ddbe318 fffff800`037604ec nt!KeBugCheckEx
01 fffff880`0ddbe320 fffff800`03775aa4 nt!VerifierBugCheckIfAppropriate+0x3c
02 fffff880`0ddbe360 fffff800`03608fa0 nt!VfCheckUserHandle+0x1b4
03 fffff880`0ddbe440 fffff800`035b365d nt! ?? ::NNGAKEGL::`string'+0x19cae
04 fffff880`0ddbe510 fffff800`032cab53 nt!NtSetEvent+0x75
05 fffff880`0ddbe570 fffff800`032c7110 nt!KiSystemServiceCopyEnd+0x13
06 fffff880`0ddbe708 fffff880`0aa73430 nt!KiServiceLinkage
07 fffff880`0ddbe710 fffff980`1e21a001 rzpmgrk+0x1430
08 fffff880`0ddbe718 fffff980`1e21a000 0xfffff980`1e21a001
09 fffff880`0ddbe720 00000000`00000c00 0xfffff980`1e21a000
0a fffff880`0ddbe728 fffffa80`082ac660 0xc00
0b fffff880`0ddbe730 00000000`00000000 0xfffffa80`082ac660

Razer Synapse driver, no surprise. Razer is known for their sub par driver development.

Update it, and if that fails, get rid of Synapse. Will your mouse you paid $$$ for lose some functionality? Yes. Will you crash frequently anymore? No.

Pros & cons.
 
Last edited:
Thanks for your help, Patrick. Synapse was fully up to date, so I've uninstalled it. I'm a big fan of macros and whatnot, so that's a shame, but certainly worth it if it'll solve this problem.

I've submitted a support ticket with Razer with some of the info from the bugcheck. I'll be curious to see if they say anything useful. I'll certainly be glad to post back here if they do, in case it helps others.

I'll leave my PC on and have it run an application or two while I'm at work today to see if uninstalling Synapse solves the problem. Fingers are crossed.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top