0x01E BSOD with factory-built PC, both before and after reformatting

Page 2 of 2 FirstFirst 12

  1. Posts : 9
    Windows 7 x64
    Thread Starter

    YoYo155 said:
    Thanks for the feedback :) .

    So it was a user mode form of "CTD".
    Maybe you're pushing the GPU beyond its limits?
    Do you monitor the temperatures in some manner?
    Did you have a look inside the case recently looking for dust accumulation?
    The GT430 is supposed to be able to get around 50FPS at max quality with 4xAA at much higher resolutions than this computer is set to. I've also stress tested the GPU before and left it running for hours without a problem. Temp after playing or leaving games running were still low. As for dust, when I manually checked the RAM a couple days ago, I had to open the case and I was actually surprised how beautifully clean it is in there (because it is so rarely used).

    I actually just fixed the dll problem for L4D2 by deleting the bin folder and then re-validating through steam (which re-downloads the files). Now it will launch without an error message. I also updated Java and Minecraft seems to be running smoothly now. I'm going to leave it on for a while and see how it goes. Later tonight and tomorrow I will try more L4D2 and another game and see how that goes, but it is looking like I may not have to reinstall the OS after all.

    Thanks for all the help, by the way.
      My Computer

  2. Posts : 9
    Windows 7 x64
    Thread Starter

    Apparently I spoke too soon. It was working great with no crashes and my wife has been playing L4D2 fairly frequently on it without problems until today. It crashed to desktop and the mouse became unresponsive. Upon restart, it took a couple tries to get it to actually boot (one time it stopped at a "searching for OS" screen). When it did boot back up, she tried L4D2 again and it crashed again. Both times it said L4D2 caused the crash. This is the dmp report (which I don't know how to determine anything from). I'd appreciate knowing what is causing this problem.
      My Computer

  3. Posts : 3,056
    Windows 10

    The bug check doesn't contain any clues, but what you're describing sounds like a hardware issue,
    be it thermals or plain faulty.

    What is the make an model of you PSU?
    Fill out this form and post back the result:

    I would like to run some tests.
    Please perform them in the order they appear.

    The Following Method Should NOT Be Performed On An SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fx key.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.

    Testing the RAM:

    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:


    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    When done with the testing procedure take a picture and upload it here.

    Test for thermals and stability:

    • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
      • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

    Reset the BIOS back to default in case you're unaware that your CPU is overclocked:

    Write down the current value of the SATA Mode!
    Its either AHCI or IDE.
    After resetting the CMOS go back and verify the value for SATA Mode is what it was
    when the OS was installed.

    If any component is overclocked reset it back to stock speeds!

    Arc said:
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.


    Please enable driver verifier following this TUTORIAL | But using the settings below:

    1. Go to Start and type in "verifier" (without the quotes) and press Enter
    2. Select "Create custom settings (for code developers)" and click "Next"
    3. Select "Select individual settings from a full list" and click "Next"
    4. Select everything, EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
    5. Select "Select driver names from a list" and click "Next"
    6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
    7. Select "Finish" on the next page.
    8. Restart the PC to take affect.
      My Computer

  4. Posts : 9
    Windows 7 x64
    Thread Starter

    The jpg is a picture of the memtest. At pass 14, the computer was needed so that is as far as it got.

    I did the driver verifier thing, but it would BSOD upon start up every time until I turned it off (in safe mode). The dmp file attached is the report for those crashes.

    I tried doing both methods of the disk check. Both times, upon restart, it didn't seem like it did anything.

    Still working on the rest.

    Edit: Oh, and one other thing. On your description of how to do the driver verifier, the word "driver" becomes a link to a paid program for drivers (an ad). It doesn't do this on my other computer. I ran a full scan with the Windows Security Essentials and downloaded Malware Anti-Adware and neither found any problems.
      My Computer

  5. Posts : 3,056
    Windows 10

    Thanks for the update :) .
    The crash was due to a well known BSOD cause in Windows 7.

    BugCheck C9, {23e, fffff88003b45308, fffff980065a4ee0, 0}
    Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
    lmvm dtsoftbus01
    start             end                 module name
    fffff880`03b44000 fffff880`03b87000   dtsoftbus01 T (no symbols)           
        Loaded symbol image file: dtsoftbus01.sys
        Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
        Image name: dtsoftbus01.sys
        Timestamp:        Thu Jan 13 10:27:08 2011

    Start Menu\Programs\DAEMON Tools Lite
    Arc said:
    Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
    I would like you to re-enable Driver Verifier just because this driver
    will always bug check the machine while DV is running, and does not mean that
    is the only problematic driver.
      My Computer

  6. Posts : 9
    Windows 7 x64
    Thread Starter

    I downloaded the SPTD standalone installer, but the Uninstall option was already greyed out. So I just went ahead and uninstalled Daemon Tools. I re-initiated the verifier and it ran fine all day, even with running L4D2.

    Forgot to mention it, but I did the PSU calculator and the PSU has more than twice the wattage needed to run the machine.
      My Computer

  7. Posts : 3,056
    Windows 10

    Thanks for the added info :) .
    Did the machine crash with Driver Verifier?
      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 00:30.
Find Us