BSOD regularly but randomly, even when computer was idle.

Page 1 of 3 123 LastLast

  1. Posts : 13
    Windows 7 Enterprise 64 bit
       #1

    BSOD regularly but randomly, even when computer was idle.


    Purchased the computer late Oct 2011, only 2 month old when system would randomly blue screen and restart at regular interval (about couple times within few hours of each other every 9-10 days). Current OS came OEM with the system, I have not re-installed OS but is considering it.

    More on the Window 7 installed here:
    64 bit
    Windows 7 Enterprise, SP1, came pre-installed with the computer.

    I have followed the steps to zip Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file. Please let me know if any additional information is needed.

    Thanks in advance!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    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.

    I'd suggest that you first backup your data 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).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    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"
    - 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).

    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.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  3. Posts : 13
    Windows 7 Enterprise 64 bit
    Thread Starter
       #3

    Thank you for the response. I'll look into implementing the first test (Memtest). Regarding the second test, when my computer blue screened in the past, I tried to use system restore (since the problem did not start until about 1.5 months after I have the computer, I thought maybe something I installed was causing this problem). But I have never been successful in system-restore -- I would get an error that says the system was not restored. I don't have the exact error messages now but if I cannot system restore, should I still try test 2?
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    charlestonc said:
    Thank you for the response. I'll look into implementing the first test (Memtest). Regarding the second test, when my computer blue screened in the past, I tried to use system restore (since the problem did not start until about 1.5 months after I have the computer, I thought maybe something I installed was causing this problem). But I have never been successful in system-restore -- I would get an error that says the system was not restored. I don't have the exact error messages now but if I cannot system restore, should I still try test 2?

    You can do them in any order but IF it is something you installed (which it usually is) verifier is the test to run

    Be sure to back up as the instructions say, just in case.

    BTW, BSOD's are always a combination of things, so it could be directx and anything else you have installed. Thats why Clean installs are so effective.
      My Computer


  5. Posts : 13
    Windows 7 Enterprise 64 bit
    Thread Starter
       #5

    driver verifier led to BSOD


    Hi,
    I followed step 2 and had the driver verifier running in the background. The computer crashed after about an hour (during which I was watching a DVD). One difference of the BSOD this time is that the computer did not automatically restart. I have attached the crash report here, but am not sure what other information I should give you to help determine the faulty driver. I also followed instruction for reporting BSOD and attached the Windows_NT6_BSOD_jcgriff2 folder again (but did not run perfmon).

    Cheers!

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

    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF8000318DB2C
    BCP3: FFFFF8800C90CE60
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\011512-40809-01.dmp
    C:\Users\Charleston\AppData\Local\Temp\WER-64085-0.sysdata.xml

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    charlestonc said:
    Hi,
    I followed step 2 and had the driver verifier running in the background. The computer crashed after about an hour (during which I was watching a DVD). One difference of the BSOD this time is that the computer did not automatically restart. I have attached the crash report here, but am not sure what other information I should give you to help determine the faulty driver. I also followed instruction for reporting BSOD and attached the Windows_NT6_BSOD_jcgriff2 folder again (but did not run perfmon).

    Cheers!

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

    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF8000318DB2C
    BCP3: FFFFF8800C90CE60
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\011512-40809-01.dmp
    C:\Users\Charleston\AppData\Local\Temp\WER-64085-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    Still memory corruption (driver verified) and this was running at the time mpc-hc.exe
      My Computer


  7. Posts : 13
    Windows 7 Enterprise 64 bit
    Thread Starter
       #7

    Hi,
    So... was that informative about what driver I should remove/reinstall to help make the system stable?

    And yes, I was using media player classic to watch DVD at the time. Though in past, I don't think I need to be using MPC for the computer to blue-screen.

    Since the last post, it had blue-screened one more time, also while watching DVD.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    charlestonc said:
    Hi,
    So... was that informative about what driver I should remove/reinstall to help make the system stable?

    And yes, I was using media player classic to watch DVD at the time. Though in past, I don't think I need to be using MPC for the computer to blue-screen.

    Since the last post, it had blue-screened one more time, also while watching DVD.
    verifier just catches things when they mis behave. In this case it didnt. If you have more DMP files always upload them
      My Computer


  9. Posts : 13
    Windows 7 Enterprise 64 bit
    Thread Starter
       #9

    OK! I will keep running verifier in the background and wait for more BSOD.
    Cheers.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    charlestonc said:
    OK! I will keep running verifier in the background and wait for more BSOD.
    Cheers.
    Good luck and let us know if you need help


    Ken
      My Computer


 
Page 1 of 3 123 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 19:12.
Find Us