BlueScreen OS Version: 6.1.7601.2.1.0 LocalID: 1033. Latest BCCode: a

[ghettotron]

Hi, I had this computer for a year now and been getting the random BSOD ever since then.
I replaced the RAM which had errors on MemTest, etc. and I thought that was causing it but still had issues.
I've reinstalled Windows 7 pro 64-bit like 5 times and still get BSOD. I don't recall the previous problem details but this is the latest one that popped up when I rebooted Windows. I've read forums on here but most of them don't seem to be the same issue and I'm afraid to install a hotfix if it is not the same issue.
Sometimes it will happen in "sleep mode" and sometimes it will happen while it's idle doing nothing but screen is on. Any help would be appreciated. Thanks in advance. Attached zip file.


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

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF800032E493C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030815-14398-01.dmp
C:\Users\Bobby\AppData\Local\Temp\WER-22120-0.sysdata.xml

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800032e493c}

*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : [COLOR="Red"][B]scmndisp.sys[/B][/COLOR] ( scmndisp+16d1 )

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

0: kd> lmvm scmndisp
start             end                 module name
fffff880`01df5000 fffff880`01dff000   scmndisp T (no symbols)           
    Loaded symbol image file: scmndisp.sys
    Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
    Image name: scmndisp.sys
    Timestamp:        Wed [B][COLOR="red"]Jan 17[/COLOR][/B] 18:18:03 [B][COLOR="red"]2007[/COLOR][/B] (45ADD4B3)
    CheckSum:         00008B81
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Netgear wireless driver is 8 years old. See if an update exists here:
NETGEAR Support | Welcome

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88011961269, fffff8800eb87fa0, 0}

Probably caused by : [B][COLOR="red"]danew.sys[/COLOR][/B] ( danew+1269 )

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

0: kd> lmvm danew
start             end                 module name
fffff880`11960000 fffff880`11962f00   danew    T (no symbols)           
    Loaded symbol image file: danew.sys
    Image path: \SystemRoot\system32\drivers\danew.sys
    Image name: danew.sys
    Timestamp:        Tue [B][COLOR="red"]Mar 23[/COLOR][/B] 19:07:33 [B][COLOR="red"]2010[/COLOR][/B] (4BA87DCD)
    CheckSum:         0000D71C
    ImageSize:        00002F00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the DeathAdder mouse driver:
Razer Support

You seem to have a lot of outdated drivers - good through ALL your devices systematically and update all the drivers.

 

[ghettotron]

Thanks for the throrough reply. This site is awesome! First time using.

Interesting though. I installed latest drivers for everything when I built computer last year and just updated the Netgear drivers in November last year. Just verified again my drivers for NETGEAR (Software release version: 2.2.0.3 in XP/Vista/Win7/ Win8). I looked online and that "scmndisp.sys" is a common thing with some of the recent Netgear drivers. :O Ugh. I'll research into that a bit more. I'll also go through again and make sure all drivers are accurate and up-to-date too. And if you happen find anything about this scmndisp.sys, please let me know. Thanks again.

 

[Golden]

Keep us updated on the situation

 

[ghettotron]

Okay, got another random BSOD code BCCode: fe
Haven't got this code before in my history so wonder what this is.
Thanks.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa801c932000}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************

Ensure USB device drivers are updated.