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

[open]

0x01E was the last BSOD code, but they vary.

I've had this secondary computer for 2 and a half years now but it was very rarely used. Partly because of things getting in the way but also because it just bluescreens constantly. It is mainly used for playing games, so most of the BSOD occur during that, but it can randomly occur elsewhere.

It is factory-built and has had issues since I first got it. One of the first things I tried, since it was already new, was to completely reinstall windows and reformat the disk while doing it. The problem persisted. At this point I was thinking it may be a hardware issue. Today I ran memcheck86 and it got through two passes with no errors (I will try letting it run overnight for more passes to be sure). I also tried physically removing the RAM to test each one, but the problem is I can never just make it BSOD, it is seemingly random and often won't do it when I want it to do it.

Perhaps it is a driver (though there is very little installed on the PC at all, because it is so rarely used, and even less when it first started doing this), but I'm not entirely sure how to go about narrowing it down.

Some of the most recent "cause addresses" for the BSODs:

ntoskrnl.exe+75c00
ntoskrnl.exe+b6ab3
ntoskrnl.exe+705c0
ntoskrnl.exe+705c0
ntoskrnl.exe+705c0
Npfs.SYS+6e9f
rdyboost.sys+91b0
rdyboost.sys+91b0
nvlddmkm.sys+c38040
win32k.sys+928f2
rdyboost.sys+91b0
ntoskrnl.exe+705c0
ntoskrnl.exe+70700
win32k.sys+ce301

If you need different/more information, let me know, and thanks

 

[YoYo155]

Hello and welcome to SF .

The majority of the bugchecks appear to be caused by AVG and COMODO.
Please uninstall both and install MSSE as an alternative.

• AVG Removal Tool
• COMODO IS Removal Tool
• Microsoft Security Essentials

Please scan for possible infection and file corruption.

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)


Please follow this detailed quote and update the driver.

Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Keep us posted .

 

[open]

AVG/Comodo removed and Nvidia drivers removed and then installed clean.

TDSS-Killer found no problems.
Kaspersky Rescue CD found no problems.
SFC/ SCANNOW corrected problems. I looked at the (gigantic) log file, but can't make heads or tales of it.

P.S. Your Drivers - Clean Left over Files after Uninstalling is unavailable to me. Either it has been removed or I don't have permission to view it.

Now I guess I play the waiting game and see if any more BSOD show up. I don't know how to read driver errors, but if you are fairly certain it is a software and not a hardware issue, I am willing to just reformat again if the problem persists and this time not install AVG/Comodo. I'm curious as to why they cause such problems on some systems and not others (they are installed on all my machines).

 

[YoYo155]

Hi thanks for the update .
Yep you're right sorry about the broken tutorial link it has been withdrawn at the moment.
As you said now it's a waiting game , it's been 14 hours since (at the time of writing this post)
and it will probably be more when you read it, how are things going so far?

 

[open]

Well I left it on overnight and it is still running fine, but I can't remember if it ever crashed while sitting idle before. I still have to try testing it with gameplay.

 

[YoYo155]

Thanks for the update .
You can check the minidump folder for new bugchecks that might have been.

C:\Windows\minidump

Keep updating.

 

[open]

Well, no new files in that folder for today, but I tried leaving Minecraft running and came back to a crash report. Though that may just be because I haven't updated JAVA. Then I tried playing Left 4 Dead 2. Every time I launch it, it will hang at a black screen until I hit Ctrl+Alt+Delete or tab out and it will show this error message:

"Left 4 Dead 2 - left4dead2.exe - Entry Point Not Found

The procedure entry point RIB_unregister_interface could not be located in the dynamic link library mss32.dll"

After I exit that message, L4D2 is in the destkop toolbar and can then be played as normal. Though it did lock up once and the process needed to be ended once during about 30 minutes of play.

I'm considering simply reinstalling the OS again and reformatting the hard drive and just not install Comodo and AVG this time.

 

[YoYo155]

Well, no new files in that folder for today, but I tried leaving Minecraft running and came back to a crash report. Though that may just be because I haven't updated JAVA. Then I tried playing Left 4 Dead 2. Every time I launch it, it will hang at a black screen until I hit Ctrl+Alt+Delete or tab out and it will show this error message:

"Left 4 Dead 2 - left4dead2.exe - Entry Point Not Found

The procedure entry point RIB_unregister_interface could not be located in the dynamic link library mss32.dll"

After I exit that message, L4D2 is in the destkop toolbar and can then be played as normal. Though it did lock up once and the process needed to be ended once during about 30 minutes of play.

I'm considering simply reinstalling the OS again and reformatting the hard drive and just not install Comodo and AVG this time.

What kind of crash?
A user mode crash meaning a program stopped responding and crashed to the desktop
or a blue screen WERFault window the one letting you know that Windows has recovered from an unexpected shutdown (the kind after the automated restart)?

From what you're describing I lean towards the user-mode crash.
A clean install, if you don't mind going through it, is a good starting point to eliminate any software issues.

You can follow the steps in the linked tutorial to achieve a perfect install.

• http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Is any component in your system overclocked?
Have you had any kind of malware /virus infection?
Are the errors specific to L4D2 and Minecraft?

 

[open]

The "crash" was the game completely froze. Like the gameplay just stopped and everything was at a standstill with no sound and it remained unresponsive until Ctrl+Alt+Del to end the process.

I am very doubtful there is any malware or virus infection because the computer is very very rarely used and when it is used, it is for playing games on two computers at once, so it is basically never used for browsing the internet. Plus I would occasionally scan it with AVG.

As for being specific to those two games, they are the only ones I have tried. There aren't too many installed (four total, I believe), I will try again tonight. Perhaps with a different game as well.

Though that startup error message about the mss32.dll happens 100% of the time L4D2 is launched, so if I can't figure out what that dll is, I will end up doing the clean install anyway.

 

[YoYo155]

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?

 

[open]

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.

 

[open]

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.

 

[YoYo155]

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:

• Power Supply Calculator

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

   Warning

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.

• *Popular BIOS access keys.

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: 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:

• CLR CMOS

   Note

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.

   Note

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

   Information

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.

   Warning

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.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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.
   

 

[open]

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.

 

[YoYo155]

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
[COLOR=Red][B]Probably caused by : dtsoftbus01.sys[/B][/COLOR] ( 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

• Driver Reference Table - dtsoftbus01.sys

Start Menu\Programs\DAEMON Tools Lite

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.

 

[open]

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.

 

[YoYo155]

Thanks for the added info .
Did the machine crash with Driver Verifier?