Strange BSOD after 6 straight hours of stability.


  1. Posts : 89
    W7 ULTIMATE 64b
       #1

    Strange BSOD after 6 straight hours of stability.


    Well, holy cow, it seemed that BSODS were gone in this computer. Somehow, strangely, after 3 or 4 weeks of BSOD absence they've come back.
    Oddly, before THIS BSOD appeared, the computer, instead of giving BSOD after a cold boot, it just froze and in order to restart the PC, I had to press the power on button for like 6 seconds.

    Well, I was just going to the kitchen to get something to eat and as I turn my back on the computer I can hear it going off and restarting, I was like "WTF?".
    Then, log in screen......"Windows bla bla problem= BSOD" "Not again...."
    I have ran PRIME95,OCCT,Windows Memory diagnose and MEMTEST in this computer, none of them have found errors, even using them after a cold boot.

    Here's the file, I would be very happy if you could lend me a hand !
      My Computer


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

    ArgentineBoy said:
    Well, holy cow, it seemed that BSODS were gone in this computer. Somehow, strangely, after 3 or 4 weeks of BSOD absence they've come back.
    Oddly, before THIS BSOD appeared, the computer, instead of giving BSOD after a cold boot, it just froze and in order to restart the PC, I had to press the power on button for like 6 seconds.

    Well, I was just going to the kitchen to get something to eat and as I turn my back on the computer I can hear it going off and restarting, I was like "WTF?".
    Then, log in screen......"Windows bla bla problem= BSOD" "Not again...."
    I have ran PRIME95,OCCT,Windows Memory diagnose and MEMTEST in this computer, none of them have found errors, even using them after a cold boot.

    Here's the file, I would be very happy if you could lend me a hand !
    This one related to memory management. Usually a driver. To find out which please run driver verifier.

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

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


  3. Posts : 89
    W7 ULTIMATE 64b
    Thread Starter
       #3

    ok,thanks for fast reply, will do it tomorrow at morning and see how things turn out.
      My Computer


  4. Posts : 89
    W7 ULTIMATE 64b
    Thread Starter
       #4

    Fast crash mate


    Ok, I followed the steps then restarted the machine, as soon as Windows loaded itself (the part where WIndows 7 logo forms) it crashed with something like a "softbus1.sys" BSOD.
    here's the minidump I just found inside Windows folder.
      My Computer


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

    ArgentineBoy said:
    Ok, I followed the steps then restarted the machine, as soon as Windows loaded itself (the part where WIndows 7 logo forms) it crashed with something like a "softbus1.sys" BSOD.
    here's the minidump I just found inside Windows folder.

    Driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. I would remove it at least to test.
      My Computer


  6. Posts : 89
    W7 ULTIMATE 64b
    Thread Starter
       #6

    NOOOOOOOOOOOOO, the computer is starting to go FUBAR!!!!!!
    Programs are starting to crash randomly and Icons and files are dissapearing without warning! Now the Start icon is not the rounded W7 icon, but a white Start square icon, why is this happening? I MEAN THE PC HAS PASSED ALL KINDS OF STRESS TESTS!
      My Computer


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

    Most recent still refers to memory management. I would run driver verifier again.
      My Computer


  8. Posts : 89
    W7 ULTIMATE 64b
    Thread Starter
       #8

    zigzag3143 said:
    Most recent still refers to memory management. I would run driver verifier again.
    Wilco.
    But now Zigzag, this is insulting my logical thinking, I mean, how come the BSOD ALWAYS happens at Cold Boot? Shouldnt the error repeat itself no matter what? Why restarting the PC several times fixes the problems?
      My Computer


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

    ArgentineBoy said:
    zigzag3143 said:
    Most recent still refers to memory management. I would run driver verifier again.
    Wilco.
    But now Zigzag, this is insulting my logical thinking, I mean, how come the BSOD ALWAYS happens at Cold Boot? Shouldnt the error repeat itself no matter what? Why restarting the PC several times fixes the problems?
    AB

    It may be the memory only has a problem when cold? I might try running memtest from a completely cold machine.

    If the results werent so consistent I would be looking elsewhere and if you have a hunch I am willing to follow it even without any evidence.

    One thing you can do is to run your powercfg and tell us what sleep states are supported. (powercfg -a)

    Can we assume you arent overclocking, running a raid, and that you have a page file on the same HD as the OS?
      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 10:16.
Find Us