Constant BSOD over the past two week, varying error codes

Page 2 of 2 FirstFirst 12

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

    devalonski said:
    Ok, it's attached.
    No dump files.
    Anyway,

    Lets enable driver verifier to rule out buggy drivers.

    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/Windows 7 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 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


    Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

    Information
    Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

    Capt.Jack Sparrow said:
    Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #12

    The Event reports show major problems with the filesystem



    Please run a full CHKDSK and (another) SFC scan....
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

    At the Command prompt, type
    CHKDSK C: /R
    and hit the Enter key.

    You will be told that the drive is locked,
    and the CHKDSK will run at he next boot - hit the Y key, and then reboot.
    The CHKDSK will take a few hours depending on the size of the drive, so be patient!
    After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

    then run the SFC.

    SFC -System File Checker - Instructions
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
    At the Command prompt, type
    SFC /SCANNOW
    and hit the Enter key

    Wait for the scan to finish - make a note of any error messages - and then reboot.
    Copy the full CBS.log file created to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your SkyDrive (http://skydrive.live.com ) and post a link to it so that I can take a look.

      My Computer


  3. Posts : 15
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #13

    KoolKat,

    I followed your directions and now when I try and boot, I get the following BSOD: USBfilter.sys 0x00000D5

    School week started for me, so I'll try your route also Noel next time I get a break.

    Many Thanks
      My Computer


  4. Posts : 15
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #14

    I disabled driver verifier in Safe Mode, uninstalled AVG and MSE, reinstalled Kaspersky, and updated a few drivers using Driver Reviver. Problem seems to be gone for the meantime, computer now runs normal. I'll be back should the problem arise again.

    Thanks for the support,
    Devalonski
      My Computer


  5. Posts : 15
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #15

    New BSOD message


    Hello again,

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    0x1000007e
    Last edited by devalonski; 23 Oct 2012 at 18:29.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 20:35.
Find Us