Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD generally at startup, errors: 0x0000000a and 0x0000003b.


16 Mar 2012   #1

Windows 7 Home Premium x64
 
 
BSOD generally at startup, errors: 0x0000000a and 0x0000003b.

Hi guys, I have been experiencing BSOD crashes for a few months now. I wasn't really sure what to do but now that they have become more frequent (normally 1-3 a day) I have come to you guys for help. I'm not completely computer illiterate and I've followed the appropriate error posting instructions. Any help is hugely appreciated, thank you.

Windows 7 Home Premium
- x64
- Windows 7 Home premium first and only OS on PC.
- OEM
- Have owned the computer for about a year and a half.
- I haven't re-installed the OS at any point.

Thanks again, Nambarc.

My System SpecsSystem Spec
.

16 Mar 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

> Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe


Microsoft Security Essentials - Free Antivirus for Windows





> These crashes were caused by memory corruption/exception (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.




Memtest.
Quote:
*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 or 6 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.

RAM - Test with Memtest86+



Driver verifier

Quote:
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 SpecsSystem Spec
16 Mar 2012   #3

Win 8 Release candidate 8400
 
 

In addition to JMH'S suggestions plea remove dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd as it is often a problem.
My System SpecsSystem Spec
.


18 Mar 2012   #4

Windows 7 Home Premium x64
 
 
Memtest

Quote   Quote: Originally Posted by JMH View Post
> Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe


Microsoft Security Essentials - Free Antivirus for Windows





> These crashes were caused by memory corruption/exception (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.




Memtest.
Quote:
*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 or 6 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.

RAM - Test with Memtest86+



Driver verifier

Quote:
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.
I contacted the people I purchased my PC from about 2 weeks ago and they also suggested running Memtest86. However when I used it before I booted from a USB. It reported 0 errors but is it the same booting from USB as using a Disk ISO? I have un-installed Avast and installed MSE. Haven't actually had a BSOD yet, will report if I do.
My System SpecsSystem Spec
18 Mar 2012   #5

Win 8 Release candidate 8400
 
 

Did you run memtest for the 6-8 passes it requires?
My System SpecsSystem Spec
19 Mar 2012   #6

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Did you run memtest for the 6-8 passes it requires?
Ran Memtest86+ for 8 passes last night and it didn't report any errors so I will try this driver identifier next.
My System SpecsSystem Spec
19 Mar 2012   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Nambarc View Post
Quote   Quote: Originally Posted by zigzag3143 View Post
Did you run memtest for the 6-8 passes it requires?
Ran Memtest86+ for 8 passes last night and it didn't report any errors so I will try this driver identifier next.
Good job and good news. Verifier should make your system crash. Upload the dmp file when it does.
My System SpecsSystem Spec
Reply

 BSOD generally at startup, errors: 0x0000000a and 0x0000003b.




Thread Tools



Similar help and support threads for2: BSOD generally at startup, errors: 0x0000000a and 0x0000003b.
Thread Forum
Solved Random BSOD, 3 crashes, error 0x000000d1, 0x0000000a, and 0x0000003b BSOD Help and Support
Solved BSOD, multiple errors 0x0000003b, 0x0000007e, 0x0000007f BSOD Help and Support
BSOD random 0x0000000a, 0x0000003b BSOD Help and Support
BSOD Playing BF3 error 0x0000003B, 0x0000000D1, 0x0000000A & 0x0000007 BSOD Help and Support
BSOD Frequent Errors 0x0000000a and 0x0000000e BSOD Help and Support
BSOD during general use, errors 0x0000003B and 0x000000BE BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 06:06 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33