Windows 7 random BSOD's while not in use

Page 1 of 2 12 LastLast

  1. Posts : 89
    Windows 7 Home Premium 64bit
       #1

    Windows 7 random BSOD's while not in use


    I've started a thread in the general discussion about whether or not to reinstall windows or try and correct issues on my machine and I was directed here. My computer will be sitting and then all of a sudden shut down and come back up with a "system has recovered from an unexpected shut down" window and say it was from a blue screen. I've been having issues with my Radeon card getting correct drivers installed and I feel like it may be caused by that. I had to uninstall and run driver sweeper a couple of times and it finally installed the latest 13.1 up from 11.2. I've been getting artifacts on the screen a few times that resulted in a crash but It's been working so far. I've posted a minidump file that's been created in hopes that we can get this sorted without me having to just wipe the system.


    Any help is much appreciated!
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    It appears that a very old driver from Netgear Neutral Wireless Solution is the cause of your BSOD.

    Please update it to the latest version available: Driver Reference Table - scmndisp.sys
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 1, fffff8000309ba3c}
    
    *** WARNING: Unable to verify timestamp for scmndisp.sys
    *** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
    Probably caused by : scmndisp.sys ( scmndisp+16d1 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000309ba3c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cd100
    GetUlongFromAddress: unable to read from fffff800032cd1c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeWaitForSingleObject+13c
    fffff800`0309ba3c f00fba2e07      lock bts dword ptr [rsi],7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800726aeb0 -- (.trap 0xfffff8800726aeb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000014e5d5 rbx=0000000000000000 rcx=0000000000000002
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000309ba3c rsp=fffff8800726b040 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff80003210e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeWaitForSingleObject+0x13c:
    fffff800`0309ba3c f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030941e9 to fffff80003094c40
    
    STACK_TEXT:  
    fffff880`0726ad68 fffff800`030941e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0726ad70 fffff800`03092e60 : 00000000`00000000 00000000`00000002 fffffa80`05b085d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0726aeb0 fffff800`0309ba3c : fffffa80`048ff830 fffff880`03a1f19a 00000000`00000001 00000000`abababab : nt!KiPageFault+0x260
    fffff880`0726b040 fffff880`014b45b2 : 00000000`00000000 fffffa80`00000000 fffffa80`048ff800 fffff880`00df5100 : nt!KeWaitForSingleObject+0x13c
    fffff880`0726b0e0 fffff880`018876d1 : 00000000`00000000 00000000`00000088 00000000`00000001 00000000`00000000 : ndis!NdisWaitEvent+0x32
    fffff880`0726b120 00000000`00000000 : 00000000`00000088 00000000`00000001 00000000`00000000 fffff880`00df73e0 : scmndisp+0x16d1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    scmndisp+16d1
    fffff880`018876d1 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  scmndisp+16d1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: scmndisp
    
    IMAGE_NAME:  scmndisp.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45add4b3
    
    FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1
    
    BUCKET_ID:  X64_0xA_scmndisp+16d1
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm scmndisp
    start             end                 module name
    fffff880`01886000 fffff880`01890000   scmndisp T (no symbols)           
        Loaded symbol image file: scmndisp.sys
        Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
        Image name: scmndisp.sys
        Timestamp:        Wed Jan 17 13:48:03 2007 (45ADD4B3)
        CheckSum:         00008B81
        ImageSize:        0000A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

       Note
    Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:
      My Computer


  3. Posts : 89
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    I haven't gotten a chance to handle the Netgear issue but the only Netgear device I have on is a Wireless usb stick that does look like it has extremely old drivers which I will take care of shortly. I did get another "windows has recovered..." message and this is the minidump file associated. My apologies if it is the same netgear issue, but I really appreciate all the help!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    It is exactly the same as the earlier one .... the historic Netgear driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 1, fffff800030d9a3c}
    
    *** WARNING: Unable to verify timestamp for scmndisp.sys
    *** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
    Probably caused by : scmndisp.sys ( scmndisp+16d1 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800030d9a3c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330b100
    GetUlongFromAddress: unable to read from fffff8000330b1c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeWaitForSingleObject+13c
    fffff800`030d9a3c f00fba2e07      lock bts dword ptr [rsi],7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88004655eb0 -- (.trap 0xfffff88004655eb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000025b7a rbx=0000000000000000 rcx=0000000000000002
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030d9a3c rsp=fffff88004656040 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff8000324ee80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeWaitForSingleObject+0x13c:
    fffff800`030d9a3c f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030d21e9 to fffff800030d2c40
    
    STACK_TEXT:  
    fffff880`04655d68 fffff800`030d21e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`04655d70 fffff800`030d0e60 : 00000000`00000000 00000000`00000002 fffffa80`06296030 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`04655eb0 fffff800`030d9a3c : 00000000`00000000 fffff880`03a1f19a 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`04656040 fffff880`014e05b2 : 00000000`00000000 fffffa80`00000000 fffffa80`07628800 fffff800`030c8e00 : nt!KeWaitForSingleObject+0x13c
    fffff880`046560e0 fffff880`0191f6d1 : 00000000`00000000 fffffa80`06d06210 00000000`00000000 00000000`00000000 : ndis!NdisWaitEvent+0x32
    fffff880`04656120 00000000`00000000 : fffffa80`06d06210 00000000`00000000 00000000`00000000 fffff880`03a873e0 : scmndisp+0x16d1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    scmndisp+16d1
    fffff880`0191f6d1 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  scmndisp+16d1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: scmndisp
    
    IMAGE_NAME:  scmndisp.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45add4b3
    
    FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1
    
    BUCKET_ID:  X64_0xA_scmndisp+16d1
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm scmndisp
    start             end                 module name
    fffff880`0191e000 fffff880`01928000   scmndisp T (no symbols)           
        Loaded symbol image file: scmndisp.sys
        Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
        Image name: scmndisp.sys
        Timestamp:        Wed Jan 17 13:18:03 2007 (45ADD4B3)
        CheckSum:         00008B81
        ImageSize:        0000A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    After taking care of the driver (if that is possible to get a driver supporting windows 7 for your device) let us know the situation.
      My Computer


  5. Posts : 89
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    I ran the updated software before and after it finsihed the program opened fine but it wouldnt actually connect to the network even though it was visible.. so I used a restore point and now I can't even uninstall the stupid program through control panel due to some error

    Edit: I upgraded it again then I was succesfully able to unistall it completely from control panel and then reinstall it new but I'm still having issues connecting to the actual nework. It shows up but doesnt establish a connection
    Last edited by Zach1928; 12 Mar 2013 at 12:07.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Dont mind, I would suggest you to either use a new dongle, or to install (the best option) a network card.

    Those old devices and their drivers are always problematic for windows 7 .... as those are not designed for this OS.
      My Computer


  7. Posts : 89
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    It actually works now, speak of the devil. And I only got the device last summer just because my box isnt very big and I've got a 4850 in one spot and an antec cyclone in the other so there isn't access to the pci slot :/ But I guess now I'll report back if the machine crashes again (hopefully not) and run the memtests tonight to see what those produce. Thanks everyone
    Last edited by Zach1928; 12 Mar 2013 at 19:57.
      My Computer


  8. Posts : 89
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Just had another BSOD which I think may be related to the ATI drivers. I was trying to run a Windows Experience Index which hasn't been actually able to complete for quite some time and during the DX9 and DX10 assessments, there were artifacts coming on the screen and then it would flash and say "amd drivers have crashed and successfully recovered." I then went into Catalsyt Control center and adjusted the clock speeds and ran the gpu test to check the stability and that caused the blue screen.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8006a404e0, fffff88003ac7efc, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+8efc )
    
    Followup: MachineOwner
    ---------
    See it: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    Is it the first time you are seeing the "amd drivers have crashed and successfully recovered."? How old the GPU is?
      My Computer


  10. Posts : 89
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    It's the first time actually, I've had problems in the past with this card getting the proper drivers installed but I only got it over the summer. It was stuck on 11.2 and then the other day I uninstalled them, ran driver sweeper in safe mode and then miraculously version 13.1 installed no problem so the drivers are current
    Last edited by Zach1928; 13 Mar 2013 at 10:49.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:31.
Find Us