BSOD when I shut down my computer

Page 1 of 2 12 LastLast

  1. Posts : 27
    Windows 7
       #1

    BSOD when I shut down my computer


    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
      My Computer


  2. Posts : 43
    Windows 7
       #2

    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 =]
      My Computer


  3. Posts : 11,840
    64-bit Windows 8.1 Pro
       #3

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


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    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
      My Computer


  5. Posts : 120
    Windows 7 Professional x64
       #5

    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....
      My Computer


  6. Posts : 27
    Windows 7
    Thread Starter
       #6

    Only when I shutdown do I get the blue screen.
      My Computer


  7. Posts : 120
    Windows 7 Professional x64
       #7

    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
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    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:
    Code:
    
    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
    
      My Computer


  9. Posts : 27
    Windows 7
    Thread Starter
       #9

    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.
      My Computer


  10. Posts : 5,705
    Win7 x64 + x86
       #10

    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.
      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 13:48.
Find Us