[SOLVED] Random BSODs - Windows 7 x86

T

ThuG PoeT

Member
Joined
Feb 28, 2015
Posts
16
Hi,

I'm getting random BSODs and I have no clue why!!
Attached is the needed zip files.

Thanks.

· OS - Windows 7 Ultimate SP1
· x86 (32-bit)
· What was original installed OS on system? Windows XP
· Retail version
· Age of system (hardware) around 4-5 years old
· Age of OS installation - have you re-installed the OS? 2 years - No

· CPU: Intel Core 2 Duo
· Video Card: Nvidia GeForce 8500GT
· MotherBoard - Intel (not sure which model)
· Power Supply - S-TEK 400W

· System Manufacturer: Acer
· Exact model number: Veriton M460

· Desktop
 

Attachments

re: Random BSODs - Windows 7 x64

Code: 
0: kd> .bugcheck
Bugcheck code 000000C4
Arguments 000000f6 0000012c a86b3558 93dfc849

Code: 
0: kd> k
ChildEBP RetAddr  
a989366c 83148f03 nt!KeBugCheckEx+0x1e
a989368c 8314d766 nt!VerifierBugCheckIfAppropriate+0x30
a9893720 8303426b nt!VfCheckUserHandle+0x14f
a9893750 83034125 nt!ObReferenceObjectByHandleWithTag+0x13b
a9893774 83156836 nt!ObReferenceObjectByHandle+0x21
a989379c 93dfc849 nt!VerifierObReferenceObjectByHandle+0x21
a9893bdc 831436c3 Lachesis+0x849
a9893c00 82e47bc5 nt!IovCallDriver+0x258
a9893c14 8303cca5 nt!IofCallDriver+0x1b
a9893c34 8303fe8e nt!IopSynchronousServiceTail+0x1f8
a9893cd0 830868cb nt!IopXxxControlFile+0x6aa
a9893d04 82e4e896 nt!NtDeviceIoControlFile+0x2a
a9893d04 770670f4 nt!KiSystemServicePostCall
0012ebcc 00000000 0x770670f4

Your Razer Lachesis drivers are incorrectly referencing a handle that is user-mode as kernel-mode, therefore verifier threw the bug check.

Code: 
0: kd> lmvm Lachesis
start    end        module name
93dfc000 93dfef00   Lachesis   (no symbols)           
    Loaded symbol image file: Lachesis.sys
    Image path: \SystemRoot\system32\drivers\Lachesis.sys
    Image name: Lachesis.sys
    Timestamp:        Mon Sep 28 06:20:38 2009

Razer has never been one to be known for their outstanding drivers, but for once this is just a matter of you needing to update the driver in general. 2009? That's pre-Synapse as far as I know, which is what you want nowadays with Razer devices for their drivers. Synapse is garbage, but you at least won't blue screen : )
 
re: Random BSODs - Windows 7 x64

Oh ok. Didn't know Razer suck that much lol.
I'll update the driver and try again.
 
re: Random BSODs - Windows 7 x64

Oh ok. Didn't know Razer suck that much lol.
Click to expand...

Razer makes decent hardware, but their drivers on the other hand..

Also I am fairly elitist when it comes to software development regarding hardware. I've seen a lot of "interesting" stuff from Razer's drivers.

According to this list my Razer Lachesis isn't supported by Razer Synapse 2
Click to expand...

: (

Is there any way to update the driver standalone?
 
re: Random BSODs - Windows 7 x64

Looks like it was modified in 2011. Does now = updated the 2009 one, or now = the one I saw in the dump?
 
re: Random BSODs - Windows 7 x64

Well, if there's no update the only thing you can do to stop the crashes is:

1. Don't use the mouse, use something else.

2. If you like the mouse, remove the Razer drivers + unplug it and shut down. On startup, plug it back in and Windows will install the generic mouse drivers. The mouse will work fine but you won't have any Razer control panel features, etc. AFAIK as I had a Lachesis years ago, you could change the DPI on it right from the buttons at the top so it's fine without the Razer drivers.
 
Re: Random BSODs - Windows 7 x64

So I did option 2, and Windows installed a Lachesis mouse driver dated 2007. I tried the Driver Verifier and this time no BSOD :)
But i have a question, how do i know Driver Verifier is running?

PS: i think you need to change the thread title cuz i'm using Win 7 32bit not 64.
 
Re: Random BSODs - Windows 7 x64

But i have a question, how do i know Driver Verifier is running?
Click to expand...

Elevated CMD (admin) and type verifier /query

If a bunch of stuff flashes and then CMD closes, it's enabled.

PS: i think you need to change the thread title cuz i'm using Win 7 32bit not 64.
Click to expand...

Changed.
 
Oh no i got a fresh BSOD :(
I left Driver Verifier running through the night and when i woke up the BSOD was there.
Attached is the mini dump.

I wonder if it's still the mouse??
 

Attachments

I know what it is, but I can't explain/show it with a minidump. Can you get me the kernel-dump for that crash, please? C:\Windows and it's called MEMORY.DMP. Upload it anywhere like Onedrive, and then paste the link here.
 
Your system is likely currently only set to generate small memory dumps.

Oh well, I can still analyze it, just not explain it as much as I'd like to.

Code: 
1: kd> .bugcheck
Bugcheck code 000000C4
Arguments 00000062 878f6244 87897150 00000006 // 6 allocations

Code: 
1: kd> knL
 # ChildEBP RetAddr  
00 ab8e88c0 8314ef03 nt!KeBugCheckEx+0x1e
01 ab8e88e0 831535eb nt!VerifierBugCheckIfAppropriate+0x30
02 ab8e88f0 82e264ca nt!VfPoolCheckForLeaks+0x33
03 ab8e892c 82fb6f5a nt!VfTargetDriversRemove+0x66
04 ab8e8940 82fc49d4 nt!VfDriverUnloadImage+0x5e
05 ab8e8978 82fc475b nt!MiUnloadSystemImage+0x231
06 ab8e899c 830d2a1d nt!MmUnloadSystemImage+0x36
07 ab8e89b4 8303a881 nt!IopDeleteDriver+0x38
08 ab8e89cc 82e8f320 nt!ObpRemoveObjectRoutine+0x59
09 ab8e89e0 82e8f290 nt!ObfDereferenceObjectWithTag+0x88
0a ab8e89e8 830d30e9 nt!ObfDereferenceObject+0xd
0b ab8e8b3c 830d2d3a nt!IopUnloadDriver+0x3a0
0c ab8e8b48 82e54896 nt!NtUnloadDriver+0xf
0d ab8e8b48 82e53ba1 nt!KiSystemServicePostCall
0e ab8e8bc4 830d2e39 nt!ZwUnloadDriver+0x11
0f ab8e8d1c 830d2d3a nt!IopUnloadDriver+0xf0
10 ab8e8d28 82e54896 nt!NtUnloadDriver+0xf
11 ab8e8d28 77c370f4 nt!KiSystemServicePostCall
12 003cf1b4 00000000 0x77c370f4

Code: 
0xc4_62_VRF_LEAKED_POOL_IMAGE_MBAMSwissArmy.sys

Malwarebytes' anti-malware driver didn't free six pool allocations before unloading itself, causing a leak and therefore verifier threw the bug check.

Uninstall Malwarebytes.
 

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

Back
Top