Need help with BSOD's

June 10, 2012 at 06:55:19
Specs: Windows 7, Phenom II
Periodicity I get a BSOD. I'm not much good at deciphering these can any one help?

Image link to errors:

See More: Need help with BSODs

Report •

June 10, 2012 at 07:44:04
In your image of the errors....

The STOP error string = the Bug chec.... string.

E.g. 0x0000000a = STOP: 0x0000000a

You get a STOP error when Windows encounters a problem it can't recover from.

You can look up the possible causes of the STOP error on the web by searching with the STOP error string, e.g. STOP: 0x0000000a, but there are a huge number of possible causes in most cases. It's only relevant if other info in the "hit" fits your situation.

You could try searching the web for: WhoCrashed, download it, install it, run it, click on Analyze in the top bar, but that may yield you no more info than that on your image. (It finds your minidump files automatically and analyzes them.)

The text before that in all capitals with underlines between is the description of the STOP error

The Parameters to the right of Bug Chec... are usually unique to your own computer and useless regarding searching for what your problem is

The Caused by address info is probably unique to your own computer too,

The files listed under Caused by Driver are not necessarily what actually caused the problem - Windows often cannot tell you what actually caused the problem and names a file that is affected by the problem instead.

The Crash time indicates when the event happened - apparently you are not getting the STOP errors very often.

When you are able to start up the computer again after getting the STOP error, if it doesn't happen repeatedly, don't worry about it.

If the STOP error only happens when you use a specific program, that's a good clue..

Games tend to have more bugs in them that the vast majority of software does.
There may be info about the error and an update or patch for the game that cures the problem on the game maker's web site. .

Report •

June 10, 2012 at 08:38:34
"I'm not much good at deciphering these can any one help?"

All you need to do is google the Bug Check String. For instance, the most recent one, IRQL_NOT_LESS_OR_EQUAL

It could be a driver issue, but my guess is you have bad RAM. Did you ever test it with memtest86+ or Windows Memory Diagnostic?

Report •

June 10, 2012 at 10:02:43
I was aware of most of that information and I do appreciate it. I was hopping all the info may help narrow it down. The problem only occurs at idle never during use. As you mentioned its so seldom its impossible to recreate. I'm 99% sure its related to the cpu or memory given the history with the system. Though I can bench test the heck out of it with no issue at all. Memtest also shows no issues. Given the timing it tends to happen on rainy days ( lots of power surges ). I find that hard to point fingers at because its running on an APS backup.

I guess I will have to continue to live with it.

sorry riider, didnt see you post but I think I commented on most of it.

Report •

Related Solutions

June 10, 2012 at 13:46:35
It's extremely rare for ram that worked fine previously in the same mboard to go "BAD", but ram can develop a poor connection in it's slot(s) that can cause a small amount of ram errors, and/ or you can certainly have problems if all the ram isn't 100% compatible.

You don't have a large amount of ram errors, otherwise either the computer would not boot, or if it did the operating system would not load, or if it did load you would be having constant problems.

If they were caused by a small amount of memory errors problem or the CPU you would be frequently getting STOP errors - you're not.

"Given the timing it tends to happen on rainy days ( lots of power surges ). I find that hard to point fingers at because its running on an APS backup."

Power spikes or surges that are caused by lightning strikes can get past any protection. Data on the hard drive and the computer components can even be damaged in that situation even when the computer is not running if it's still plugged in, and/or if whatever it is connected to that is protecting it is still plugged in. Voltage spikes can be produced by a lightning strike that can jump across switches that are switched off. .

Report •

June 10, 2012 at 14:18:43
"I'm 99% sure its related to the cpu"

CPUs work or they don't, there's no in-between. It doesn't sound like you want to take the time to troubleshoot & you've decided to live with the problem, so I guess I'm done here.

Report •

June 10, 2012 at 22:59:50
One very good possibility is your hard drive might be showing signs of going bad. Happened to me last year. I had bsod's and freeze ups constantly. I tried checking my memory with Memtest86 and found no errors. So then I decided to assume my hard drive was the culprit. I used 's Hirem's Boot CD to back it up to an external hard drive and replaced the hard drive. Then I took the back up image and wrote it to the new hard drive. The last thing I did was repair my Win XP installation with a slipstreamed version of the system CD. After that, I was back in business.

It has quite a few utilities that could help you diagnose bsod problems if it is not your hard drive.

Hope this helps.

One more thing I found on bsod causes in general. Note what it says for hard drive problems.

Report •

June 11, 2012 at 00:26:11
After looking at your link I notice it doesn't always seem to be the same issue. A few years ago I had the same sort of problem. It started fairly random but at times it happened more often. What I found on the net was telling me either ram (which I baulked at having wasted about a week with memtest) vid card drivers needed updating ( they were the most up to date and I tried three other cards ) or nvidia driver issues ( I had nothing that used nvidia drivers ). While I was pulling my hair out my psu went bad. After replacing it the problem persisted. It was suggested that I try "speedfan" to check the output voltages of my new psu. All was as should be. I did remember that with the old psu some of the voltages fluctuated a good deal. It was then suggested that I check my ram voltage. My ram required 1.8v and in the bios it was set to Auto. I set it to 1.8v (the lowest setting I had) and the BSODs came on a good deal more. Either at boot or by the time I opened say the fourth program whatever they may be, IE, a game, a video, etc..etc..I went back in and set the voltage to 1.9v. No more BSODs. I checked the voltage with speedfan and it said it was 1.8v so I think the setting is messed up in some way on that board/bios.

I am not much into the whole overclocking thing but did experiment with other voltages. At 2.3v I started having troubles with both heat and BSODs. Been at 1.9v since (at least 2 years) with no troubles at all.

I may be way off but it may be worth checking those voltages.


Report •

June 11, 2012 at 01:15:30
Here's a page with some info of things you can try as a last ditch effort:

If you have a Radio Shack in your area, get a can of contact cleaner and a can of compressed air at any store that sells it. Pull all of your PC's cards (pci, memory, cpu if on a board with edge connectors) and clean all of the edge connectors. Then reseat. Use the compressed air to clean out any dust if it is needed. Pull devices from your PC one at a time to see if the BSOD error disappears. If it does then either that device is defective or it has a defective driver.

Report •

June 11, 2012 at 05:34:53
great info guys thx, will keep me busy ;)

Report •

Ask Question