3 bluescreens today


  1. Posts : 45
    Windows 7 X64
       #1

    3 bluescreens today


    Hello.

    I was posting here a couple of weeks ago about my bluscreens and
    was told to uninstall slysoft's Virtual Clonedrive
    and remove Acronis True Image.

    Today I got 3 new bluescreens in a row.

    Can someone give me a clue about what the problem could be?=
    The RAM should bee ok due to memtest86
      My Computer


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

    3 different BSOD's and they blame 2 different Windows components.
    Most likely this is a hardware issue, but it can also be a problem with Windows.

    To rule out 3rd party stuff, let's start with running Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    Once we analyze the dump files from that, then we'll start with these free hardware diagnostics:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 04:06:17.396 2010 (UTC - 4:00)
    System Uptime: 0 days 0:07:14.222
    BugCheck 3B, {c0000005, fffff80002cae1e6, fffff880095adf30, 0}
    Probably caused by : ntkrnlmp.exe ( nt!ExfReleasePushLock+4bb )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  WmiPrvSE.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 03:58:05.660 2010 (UTC - 4:00)
    System Uptime: 0 days 0:04:17.486
    BugCheck 50, {fffff88005d85224, 0, fffff96000671686, 0}
    *** ERROR: Module load completed but symbols could not be loaded for cdd.dll
    Probably caused by : cdd.dll ( cdd+11686 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  explorer.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 03:42:04.021 2010 (UTC - 4:00)
    System Uptime: 0 days 3:44:22.474
    BugCheck 1E, {ffffffffc0000005, 1, 8, 1}
    Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  SkypeNames2.ex
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
     
     
      My Computer


 

  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 01:08.
Find Us