Bluescreen: new driver or something sinister?

By luketigers ·
Hi, just wondering whether it is not uncommon to get a blue screen following installing new drivers. I had just downloaded and installed the new drivers for my Razer Naga from their website. Upon being asked to restart the computer and selecting OK I got an instant Bluescreen.

Below is the report

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.
Locale I 3081

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: 0000000000000000
BCP3: FFFFF8800764D000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:

Is it most likely from the driver or could it be from something else on my computer (virus, hacker etc.). I'd rather reformat than assume it's ok. I have been having moderate issues with Firefox loading slowly and any games I run seem to push the RAM to near limit and hence run slowly. This has been for about 4 weeks.

I'm running Windows 7 64bt. It's frustrating seeing my RAM at near capacity for just a game and firefox (plugins use a bit).

Cheers for any insights.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by santeewelding In reply to Bluescreen: new driver or ...

That you are out on the cusp of things (up to a thousand selectable choices?).

Collapse -

How can I narrow it down more for you

by luketigers In reply to Appears

I'm after what's likely - if you need more info let me know please.

Collapse -

not 100% where to find it

by luketigers In reply to Yep.

these are from my action centre

Kernel - Power (Critical)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0x0000000000000000, 0xfffff8800764d000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 122**0-54319-01.

Activation context generation failed for "C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\ Component 2: C:\Windows\WinSxS\manifests\

Bonjour service
360: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Is Bonjour necessary?

Hope this is what helps

Collapse -

Where to find it:

by seanferd In reply to not 100% where to find it

When the system BSODs, read the screen, and write it down. (STOP 0x00000000 some human readable text - no need to write down all the registers after that.)

If the system reboots before you can read it, stop that behavior: System Properties → Advanced → Startup and recovery settings → un-tick Automatically restart.

Custom dynamic link libraries are being loaded for every application.</code>

Could be normal, could be bad. Get this: and run Autoruns.exe.

Look at the AppInit tab. Anything in there? Anything look wrong?

You can have a poke through the other tabs as well, Logon is fairly informative.

There is also a conflict in Windows SxS -your Adobe app can't use the correct Common controls. Was it properly installed as a 32-bit app in this 64-bit system?

"Is Bonjour necessary?"

It is for some Apple stuff.

But I don't think most of these are related to your crash.

Collapse -

TY for being helpful

by luketigers In reply to Where to find it:

"Look at the AppInit tab. Anything in there? Anything look wrong?"

Only had an AVG startup in there, so that looks fine thanks.

logon looks ok, only thing im not sure of there is
HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms

rdpclip file not found

followed your other tips

this is prolly my STOP code

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0x0
BugcheckParameter3 0xfffff8800764d000
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

I got this recently too from event viewer..
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

1 user registry handles leaked from \Registry\User\S-1-5-21-3973223190-2993365107-28**21576-1001:
Process 5748 (\Device\HarddiskVolume2\Windows\System32\msiexec.exe) has opened key \REGISTRY\USER\S-1-5-21-3973223190-2993365107-28**21576-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts

Collapse -

Wininit/AppInit is probably fine, then.

by seanferd In reply to TY for being helpful

<code>HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms</code>

Remote Desktop. Rdpclip is for server-side clipboard/filecopy. That may be left from a time when you had this system set up for you or someone else (even MS Support) to remote into. Not sure why the file is missing, but unless you remote into this system, you don't really need it. You can certainly un-check this as a startup item, but you don't have to.

Run sfc /scannow from the Run box or command prompt to see if any other files are missing.

"this is prolly my STOP code"

Nope. That is debug data I can't even begin to understand, especially without the machine in front of me. You have to get it from the BSOD itself. Just note the initial code and error text next time it bluescreens.

<code>Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.</code>

If this happens at every logoff or shutdown, you can install the UPHClean service from MS, although it will not necessarily cause problems, especially where domain policy isn't being updated all the time.

This looks like it would be an isolated instance where the Windows/Microsoft Installer failed to close a key it had modified. As long as whatever the application was installed OK, nothing to worry about.

P.S., if you hunt through Event Viewer looking for errors and warnings, you'll find them. Best to just look for errors occurring just prior to the time of your system or application crash. In fact, it may make it easier if you clear the event logs (back them up when prompted, if you like), so you aren't hunting through unrelated errors.

Have you found any of the links on the Razer relevant to your situation, or no? The drivers do apparently have issues that cause system crashes.

Collapse -

You already did

by santeewelding In reply to How can I narrow it down ...

Narrow it down, that is, in your original reloading the OS at the drop of a hat. I was struck by that.

This would seem to me that your W7 64-bit exists solely to accommodate gaming (mine is not). Yours does not appear to be overloaded with other stuff for workaday things. You know -- like monitoring, security, performance, and the like. It is, but a platform for gaming.

You also mentioned other worrisome (to me) anomalies, like slowing and cpu overuse in the immediate past.

Long story short: I am the wrong one to ask. I only react and remark about your "cuspiness".

Collapse -

Possible temp workaround and new way forward

by TobiF In reply to Bluescreen: new driver or ...

I'd guess that the problem is with what you just installed. Further investigations down the lines given in the other subthreads will help you with that. (exploring the minidump etc.)

I suggest you roll back to your latest system restore point, to get the system operational.

Then, rather than just running that installation package again, try checking it out with the compatibility checker. Don't have my win7 around right now, but I'd try right clicking on the installation exe and look for compatibility settings. There is a longer way around, as well (where you'd first go into the compatibility things, and then point to your installation file from there.)

Good luck!

Related Discussions

Related Forums