BSOD while gaming / booting games

Hello ! Welcome to SF !

Yes i think it has to do something with Razor Mouse because the Driver it's using is from 2005. Uninstall the mouse drivers completely and download a fresh copy if it's available. Then update it. If not delete the mouse drivers and see if you can get a mouse from you friend or so and see if that works fine.

Code:

 Razerlow.sys Mon Nov 07 12:03:11 2005

Good Luck,
Captain

joost said:

Thank you for your reply.

I downloaded this driver: Razer Diamondback Windows 7 Driver v6.02

I have already reinstalled it like 3 times today and yesterday. Do you have any idea why it says 2005?

Cheers

Since that release date or the Driver wasn't updated after 2005. Try to go to C:\Windows\System32\Drivers and rename the Razerlow.sys to Razerlow.old then reboot then try to install the Driver. Remember the Mouse won't function until you reinstall the Driver.

- Captain

joost said:

I have removed the driver and renamed the file as you said, rebooted and reinstalled the newest version of the driver. I tried to play some COD2 and it seemed to work, but after about 20 minutes I still got a BSOD... :/

I attached the dmp file. Any help would be appreciated :)

Thanks

Hello,

Seems like the IRQL has been raised while i-Tunes was running. That's quiet weird try this follow this thread Using Driver Verifier to identify issues with Drivers and enable Driver Verifier.

- Captain

Hello,

Seems like the Driver Verifier has caught Razor Mouse again seems like a bad driver or Bad mouse itself it best to replace the mouse.

Code:

nable to load image \SystemRoot\system32\drivers\Razerlow.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Razerlow.sys
*** ERROR: Module load completed but symbols could not be loaded for Razerlow.sys
Probably caused by : Razerlow.sys ( Razerlow+20f3 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: d7d7d7d70000012c, Handle value being referenced.
Arg3: fffffa80066bcb30, Address of the current process.
Arg4: fffff88003dfc0f3, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f5c3dc to fffff80002ad2600

STACK_TEXT:  
fffff880`09554728 fffff800`02f5c3dc : 00000000`000000c4 00000000`000000f6 d7d7d7d7`0000012c fffffa80`066bcb30 : nt!KeBugCheckEx
fffff880`09554730 fffff800`02f71ae4 : fffffa80`066bcb30 d7d7d7d7`c0000022 fffffa80`00000000 fffff980`149ecee0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09554770 fffff800`02d2e580 : 0012019f`08999600 fffff880`095549a0 00000000`00000000 fffffa80`060e3200 : nt!VfCheckUserHandle+0x1b4
fffff880`09554850 fffff800`02daa425 : fffffa80`00000000 fffffa80`00100000 00000000`00000000 fffff800`02dee600 : nt! ?? ::NNGAKEGL::`string'+0x20e1e
fffff880`09554920 fffff800`02f71878 : fffffa80`05a115f0 fffff980`13e86ee0 fffffa80`067ec0d8 fffff800`02dee6b7 : nt!ObReferenceObjectByHandle+0x25
fffff880`09554970 fffff880`03dfc0f3 : fffff980`13e86ee0 00000000`00000002 fffffa80`060e3270 00000000`00000001 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`095549c0 fffff980`13e86ee0 : 00000000`00000002 fffffa80`060e3270 00000000`00000001 fffff880`03dfcfa8 : Razerlow+0x20f3
fffff880`095549c8 00000000`00000002 : fffffa80`060e3270 00000000`00000001 fffff880`03dfcfa8 00000000`00000000 : 0xfffff980`13e86ee0
fffff880`095549d0 fffffa80`060e3270 : 00000000`00000001 fffff880`03dfcfa8 00000000`00000000 fffffa80`060e3270 : 0x2
fffff880`095549d8 00000000`00000001 : fffff880`03dfcfa8 00000000`00000000 fffffa80`060e3270 00000000`00000002 : 0xfffffa80`060e3270
fffff880`095549e0 fffff880`03dfcfa8 : 00000000`00000000 fffffa80`060e3270 00000000`00000002 00000000`06a4cc00 : 0x1
fffff880`095549e8 00000000`00000000 : fffffa80`060e3270 00000000`00000002 00000000`06a4cc00 fffff800`02f74d86 : Razerlow+0x2fa8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Razerlow+20f3
fffff880`03dfc0f3 89842480000000  mov     dword ptr [rsp+80h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Razerlow+20f3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Razerlow

IMAGE_NAME:  Razerlow.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  436ef527

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_Razerlow+20f3

BUCKET_ID:  X64_0xc4_f6_VRF_Razerlow+20f3

Good Luck,
Captain

joost said:

After removing the drivers and trying Driver Verifier with another mouse, I didn't get any BSODs.

I have already ordered a new mouse.

Thank you for all your help!

Your welcome ! Glad I could help !

- Captain