BSOD when I shut down my computer

[Rokchant]

I get this problem everytime I shutdown my computer and I'm not sure why.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 76
BCP1: 0000000000000000
BCP2: FFFFFA800B5F5B30
BCP3: 0000000000000034
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\042910-24913-01.dmp
C:\Users\Rokchant\AppData\Local\Temp\WER-35895-0.sysdata.xml

 

[JamesR404]

Forum lurkers to the rescue?

1) Does it also happen when you simply log off from Windows? Or only at shutdown?

2) Does it also happen when you start up windows in safe mode, and then try to shutdown?

3) Can you provide the BSOD code you see, you should have a code on the screen like: 0x00000000 and then again 0x00000000 0x00000000 0x00000000 0x00000000

The 0 can be any number. The first 0x00000000 helps most (as far as I know) to troubleshoot this. Here are some links to BSOD analysis tools I'd try to use: JamesR404's bsod Bookmarks on Delicious

But provide us forum lurkers with the error, and others can perhaps have greater insights =]

 

[Tews]

We will need the actual .dmp file for analysis.... [1 - Novice] How to ask for help with a BSOD problem

 

[usasma]

3) Can you provide the BSOD code you see, you should have a code on the screen like: 0x00000000 and then again 0x00000000 0x00000000 0x00000000 0x00000000

That info is in Rokchant's original post:
BCCode: 76
BCP1: 0000000000000000
BCP2: FFFFFA800B5F5B30
BCP3: 0000000000000034
BCP4: 0000000000000000

This translates to the info that you've requested like this:
STOP 0x00000076 (0, FFFFFA800B5F5B30, 34, 0)
or
STOP 0x00000076 (0000000000000000, FFFFFA800B5F5B30, 0000000000000034, 0000000000000000)

Still need the memory dump files (as Tews has requested) in order to try and isolate the offending driver

 

[y0himba]

Can this is directly related to a Windows update for greater than 32gb SD cards? I was getting the same thing whenever I tried to install that update....

 

[Rokchant]

Only when I shutdown do I get the blue screen.

 

[y0himba]

I was also, each time I tried to install the update below. I hid the update, and no more BSOD on shutdown.

The capacity of a Secure Digital (SD) card that is larger than 32 GB is reported incorrectly in Windows 7 and in Windows Server 2008 R2

 

[usasma]

It blames your Razer Lachesis.sys driver file.
In this post it implies that the driver isn't 64 bit compatible - BSOD - Vista - Razer Lachesis? - TechSpot OpenBoards

Temporarily uninstall the Razer software and see if that helps - if so, get the latest 64 bit drivers for the Razer and use that.

Also, update the JMicron RAID drivers on your motherboard - they're older and may not be working correctly with Win7.

Summary of the BSODs:

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 05:45:46.597 2010 (GMT-4)
System Uptime: 0 days 2:56:31.658
BugCheck 76, {0, fffffa8007070b30, 6, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18116 )
PROCESS_NAME:  conviction_gam
BUGCHECK_STR:  0x76
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 02:48:37.399 2010 (GMT-4)
System Uptime: 0 days 4:35:06.835
BugCheck 76, {0, fffffa800b5f5b30, 34, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18116 )
PROCESS_NAME:  conviction_gam
BUGCHECK_STR:  0x76
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 22:12:53.730 2010 (GMT-4)
System Uptime: 0 days 4:44:03.792
BugCheck 76, {0, fffffa8009f4cb30, 4, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18116 )
PROCESS_NAME:  conviction_gam
BUGCHECK_STR:  0x76
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 05:24:24.410 2010 (GMT-4)
System Uptime: 0 days 2:01:32.846
BugCheck 76, {0, fffffa800c3bab30, 3e, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18116 )
PROCESS_NAME:  conviction_gam
BUGCHECK_STR:  0x76
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 24 17:43:17.651 2010 (GMT-4)
System Uptime: 0 days 1:30:05.087
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lachesis.sys
*** ERROR: Module load completed but symbols could not be loaded for Lachesis.sys
Probably caused by : Lachesis.sys ( Lachesis+f44 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
[/FONT]

 

[Rokchant]

Hm, well I actually installed and old driver awhile ago which wasn't working right so I uninstalled it and installed the latest 64-bit Windows 7 compatible driver.

But, since it is still messing up, I guess I'll re-install it again and see if it fixes it.

 

[usasma]

I would suggest uninstalling it and seeing if that stops the problem.
If so, then reinstall the latest version to see if that brings the problem back.

 

[Rokchant]

Well, I re-installed the windows 7 driver and the problem still persists. So, I uninstalled it temporarily and shut down the computer a few times and it seemed to not have the BSOD.

I'm wondering what I can do. I need the new driver for my mouse but it crashes my computer.

Here's what the recent minidumps say.

 

[usasma]

Have you verified if the mouse driver is 64 bit compatible?
If it's not, then it just won't work for you.
If you're unsure, please provide us with a link where you downloaded it from.
The fix for an incompatible driver is to get another (compatible) mouse.

In this case the memory dump is a STOP 0x76 error that blames the OS kernel. Most often this is because a driver accesses the OS kernel improperly and causes the crash.

We can run Driver Verifier to identify the driver - but, IMO, that'd be unnecessary because we already know that your mouse driver is an issue.

 

[Rokchant]

Yeah it definitely is compatible with windows 7 -64bit

Razer Lachesis Windows 7 Driver v1.10 (English)

I downloaded the 1.10 driver.

 

[usasma]

Well, if the driver is OK - then that only leaves the mouse (or it's connection) as the issue.

 

[Rokchant]

I just got another BSOD AFTER I completely uninstalled all drivers for my Razer Lachesis mouse.

What's going on here? Are there files still needing deletion?

By the way, I wasn't getting these errors before I installed the windows 7 drivers.

 

[Rokchant]

bump

 

[usasma]

There are many different causes for BSOD's.

For example, a driver from Program A can write to an address space reserved for a driver from Program B. As long as the driver from Program B doesn't need to access that address space - there won't be a problem.

Then, if the driver from Program A exits - there won't be any evidence of the presence of the driver from Program A. But, then the driver from Program B will eventually access the address space that was improperly written to previously - and it'll crash (with no evidence of why it crashed).

In this case, the dump file shows that the Lachesis.sys driver is still being loaded.
Please go to C:\Windows\System32\drivers and rename Lachesis.sys to Lachesis.BAK
Then reboot the system.

The dump is still a STOP 0x76 error so you must update your JMicron drivers (JGOGO.sys Tue Feb 07 06:53:22 2006 and jraid.sys Fri Mar 23 23:20:18 2007)
Once that's done - if you're still having BSOD's there is a registry edit that should help force the bad driver to the forefront. But there is no point in doing that registry edit until the Razer driver is renamed (and stops loading) and the JMicron drivers are updated.

Summary of the BSOD:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May  3 04:23:14.481 2010 (GMT-4)
System Uptime: 0 days 12:12:59.542
BugCheck 76, {0, fffffa80071ff060, 23, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18116 )
PROCESS_NAME:  conviction_gam
BUGCHECK_STR:  0x76

 

[Rokchant]

I updated my Jmicron driver and renamed the file. Still getting the BSOD so I guess I should delete those lachesis system files and reinstall the driver or something.

 

[Rokchant]

theres 4 lachesis system files I want deleted. How do I do that registry edit that you were telling me about?

 

[usasma]

Post the memory dump files for us to have a look at.