BSOD after desktop loads: 0x0000000a

[ebforest]

I'm getting a BSOD within minutes of the desktop loading. I have update the mobo bios hoping it would fix things but no luck there. Any help would be greatly appreciated.

 

[ICIT2LOL]

Hello and welcome ebforest mate this might take some time but worth a try in the dump files there is a reference to some driver problem - though I stand to be corrected as I have only just started looking at this stuff Run Selective Startup using System Configuration

 

[ebforest]

Thanks for the response. I'll go through the various startup processes and see if it helps. The biggest problem is that it seems the BSOD is intermittent, sometimes 2 in a row then I'm good for a while. Frustrating for sure.

 

[ICIT2LOL]

Hmm might be worth trying this as this component is very often overlooked as a source of problems and in fact it can be very common


UsingHWInfo PSU

Download HW Info and pick the right bit version - HWiNFO,HWiNFO32/64 - Download -(copyand paste this siteinto the search bar) If you do not need the runninginformation in the smallerright hand panel close it. In the left hand windowclick on the + for theindividual device groupings and they will open out tothe various components.

Go on opening out further until you get to the device itself. click on it anditwill highlight. In the right hand window there will be a verydetaileddescription of that device as in brand, speeds model number etc etcThese arevery detailed and are just what is needed for searching for driversetc.

To getthe PSU volts you need to select the Sensor buttoncircled in yellow in the picfor PSU testing do the same and scroll down thereadout as in my pic to whereit has Nuvoton = yours might be a differentsection name / title. Post back apic of that please.

If you want a more definitive test see this http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html butlease only use a digital multimeter and not an analogue asthey injecttypically 9v into a circuit to test and into a 3.3v or 5v rail - nota good idea!!see the partial pic of the correct sort of meter in that tutorial.details ifyou scroll down that listing.

Now a good reference article is this
Voltage Rails -Power Supply 101: A Reference Of Specifications it will explain in detail what the voltages are and functionsof the PSU/

 

[ebforest]

I'm not sure this is what you are looking for but here is the pic.

 

[ICIT2LOL]

Well done that ITE is the power supply section and yes it is all good bar the 5v rail is a tiny bit short but not enough to be what is causing the problem .

If you can scroll though that screen again and just check out the volts to the GPU and other gear - no need to post back a shot unless you want to but let us know if you are suspicious of anything.

 

[ebforest]

Boo, BSOD is back.

Four weeks without a BSOD, I thought I was in the clear. I guess that is what I get for actually shutting down my computer.

I've attached a new debug file as things may be different (not sure but I'm guessing it is still the same "driver" error.) Any help is appreciated.

 

[ICIT2LOL]

Ok ebforest mate there is something regarding (I think) a USB problem itmight be worth updating the USB drivers. Now I have spent the best part of an hour trying to locate the drivers for your board and frankly the Asus site is one of the most convoluted ones I have ever come across. There are two USB controllers according to this Motherboards - M5A97 R2.0 - ASUS and the chipset one I have searched for but again have come up with a heap of convoluted stuff that I cannot make head nor tail of. What I might suggest is that if you have the installation disk from Asus you might try and find the chipset and / or the USB drivers on it because right at the moment I ma going round chasing my tail. The Asus site is in my mind a disgrace seeing what we pay for. But have a look and let us know what - if anything you can get from that disk. The only problem is that when they make the disk the software is invariably out of date by the time it gets to the consumer - you and I.

But if you can and in safe mode run these as well

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html < use the /f and /r options in Option 2 ifnecessary

Another option might be a system restore to when it was working and by the way have you downloaded any Windows updates since it started working properly?

 

[derekimo]

Additionally, try getting rid of Norton for the time being, your last few dumps are flagging it as well,

Unable to load image \SystemRoot\System32\Drivers\N360x64\1506000.020\SYMNETS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS

For the time being, uninstall your Anti-Virus,

AV Uninstallers

And Install Microsoft Security Essentials which we know doesn't cause BSOD's.

 

[ebforest]

Updated USB drivers, BSOD.
Ran SFC and Checkdisk, no errors, BSOD.
Uninstalled Norton 360...booted fine.

I'll try a few more restarts to confirm but I have a sneaking suspicion it was indeed Norton AV which gets me pretty steamed. I was using Security Essentials when I realized I had a subscription to Norton from my wife's computer so I figured why not use something more robust...should of known better.

Will update with results of multiple restarts in a bit.

 

[ICIT2LOL]

Yep well I am not a fan of Norton and I assume you used the removal tool for it as it is a lingerer.

Plus I often open up the registry HKEYS LOCAL MACHINE and CURRENT USER go to Software and scroll down the list to see if there is any Symantec is left.

 

[ebforest]

Restarted a few times yesterday and then again this morning. Everything seems to be working. I'll give it another day or two before marking as solved, but I'm encouraged by the results. Thanks to everyone for the help.

 

[ICIT2LOL]

Hope it is fixed mate and just as an exercise try looking in the registry as I described for left overs.

Am doing a fix right now and uninstalled Norton with the special tool they give you and there was still Symantec entries in the registry so out they came!