BSOD on start up error 0x0000003b

What hardware did you get from newegg?


Have you tried to format and install Windows since you did the disk checks? Any results?

Also, what RAM modules do you have installed? Were they bought as one kit, or did you buy separate kits?

Alright just got windows installed and is running. I am going to install the drivers tomorrow with a USB stick. I'll let you know how that goes. Hope for no BSOD *knock on wood*. Thanks got any ideas and why this might have worked this time after windows used dskchk and found nothing?

Disk check may have found something the first time it was run. Or was this the first time it was run? I had thought you ran it before?

We'll see what happens. For the driver installation and program installation, you should follow Clean Reinstall - Factory OEM Windows 7 starting with step 9.

gregrocker said:

9. The installer is mostly driver-complete, with newer arriving quickly via optional Windows Updates. Just in case, have your Wireless or Ethernet LAN driver on flash stick or CD so you can install it to get online quickly - these can be found on the Support Downloads webpage for your model computer . Then enable hardware driver auto-updating and check for optional Updates.

10. Any drivers still missing in Device Manager after several rounds of Updates can be found on the Support Downloads webpage for your model computer or device, along with possibly needed hotfixes which you can also wait to see if you need. Driver Install - Device Manager

I would not replace any drivers given by the installer or optional Updates unless performance problems point to that specfic driver. This is not XP - Windows 7 is the authority on it's own drivers.

• Unknown Devices are often SID card readers, can be traced using Hardware Identification.
• Co-processor, USB and Storage controllers are elements of the chipset.

11. Install updates and then programs slowly over time to gauge performance changes after each. You can roll back most any Program installs or Update using System Restore.

12. Don't let any programs write themselves into msconfig>Startup as they slow startup, become freeloaders on your RAM/CPU and can spy on you.

As illustrated in Startup Programs - Change uncheck everything except AV and gadgets (aka "sidebar") in msconfig>Startup.

Then after reboots do the same in msconfig>Services after checking "Hide All MS Services."

Check back with both lists periodically to see if anything writes itself back in and turn it off in its Program Preferences or Uninstall it.

● If you have any questions about a listing, Google it to learn what it does.

13. Use a lightweight free AV like Microsoft Security Essentials which works perfectly with the Windows 7 Firewall. If you're prone to infection add the paid real-time protection for Malwarebytes otherwise run its excellent free scanner monthly.

14. Activation at Control Panel>System may require a robocall to MS the first time to record your hardware signature in their servers. It will always work as long as you installed the correct version and input the key accurately.

15. When finished, clean and order the HD perfectly using state-of-the-art free CCleaner "Run Cleaner" button and Registry tab. I recommend Puran free boot-time defragger + Full Disk Check after checking Intelligent Optimizer on Additional Operations tab for state-of-the-art defrag.

16. Finally, save a Windows 7 Backup image externally so you never have to reinstall again - just reimage the HD or it's replacement using DVD/Repair CD with the stored image.

17. Henceforth if required to contact your OEM Tech Support do not tell them you clean reinstalled but troubleshoot as if you have the factory install. OEM's may refuse to support Clean Reinstall but cannot void Hardware warranty. If you ship the unit back for repair under Hardware warranty save a Windows 7 backup image and then run Factory Recovery beforehand.

Installing the drivers now onto a disc. I did do the chkdsk previously so I don't really think anything was fixed.

Alright some bad news... I installed windows downloaded all the driver for the motherboard and I was installing Microsoft security essentials when I crashed. I got error code 0x24 and it said to run chkdsk /f. I have not ran that yet and I'm wondering what to do next. I have maybe a week left with the 30 day policy, but I believe I can get a RMA from the actual companies if something is wrong with my hardware. Let me know if you have any ideas.

Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with the updated reports.

You should also run a Disk Check with Automatically fix file system errors checked for all drives.

Post back with the logs from the disk check: Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk)

Ohh yes I apologize. Since I wiped everything I did not have the Event Viewer Blue Screen of death app and I forgot about it. I'll post those logs ASAP. I'll start those tests And I'll run chkdsk and get those logs to you very soon.

Here are the logs of the two things. Thanks

I just went through your logs with a fine toothed comb and found very little useful info. I see that your minidump failed to be written. Your hard disk came out clean with the disk check. The current suspect to me is your RAM. Try removing all but one module to test. Since your blue screen crashes occur regularly, we can test the memory through running Windows. Test the memory slots as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Which parts do you need to return to newegg that are not covered by their own warranties? Typically. the RAM, CPU, and Motherboard can all be RMA'd through the manufacturers to get replacements for bad parts.