|13 Apr 2012||#1|
| || |
BSOD randomly, error 0x0000003B
I seem to be getting somewhat random BSOD errors. As far as I have noticed they are all 0x0000003B.
It generally happens after playing a game for a while but the game doesn't seem to make a difference and sometimes it doesn't happen for days.
I have not installed any new hardware for over 6 months and also generally keep my drivers as up-to-date as I can.
I have also noticed that for some reason after a computer restart (or crash), sometimes after the Windows 7 logo appears and before the login screen sometimes my monitors stop receiving signal and it can take sometimes up to 7 minutes before they regain it and I am presented with the login screen.
Any help much appreciated.
|My System Specs|
|13 Apr 2012||#2|
| || |
These crashes were caused by memory corruption/exception (Cx05) 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!!!
* If you have Raid update its Driver.
*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-7 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.
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.
So, 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/Windows 7 Startup Repair feature).
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 "Special Pool", "Force Pending I/O Requests" and "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.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
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 System Specs|
|13 Apr 2012||#3|
| || |
Besides the memory exception there are two items that need to be addressed.
Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. A known problem needs to be removed and replasced with something like magicISO.
Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST
Microsoft Security Essentials - Free Antivirus for Windows
|My System Specs|
|Similar help and support threads for2: BSOD randomly, error 0x0000003B|
|PC locks up randomly so far when idle, error 0x0000003b||BSOD Help and Support|
|Randomly occurring BSOD (STOP: 0x0000003B)||BSOD Help and Support|
|BSOD happens randomly mostly getting 0x0000003b||BSOD Help and Support|
|BSOD randomly, error 0x0000003b, BAD_POOL_HEADER. PLEASE HELP!||BSOD Help and Support|
|BSOD It Occurred Randomly, error 0x0000003b||BSOD Help and Support|
|BSOD Randomly during idle time. Error 0x0000001a, 0x0000003b||BSOD Help and Support|
|Help ks.sys BSOD error 0x0000003B||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 02:46 AM.