19 replies to this topic

[IndyLux]

Hi guys,

I'm still getting occasional BSODs on my HTPC. I'm looking in my event viewer and there are several events that seem interesting, but I don't know how to interpret the codes or debug.

I downloaded the microsoft debugger, but I've never used it and don't know how to proceed.

Can any of you fine gentlemen help?

Thanks,
Chris

-------------

Here are a few examples of the 'Kernal Power Errors'....

BugcheckCode 80
BugcheckParameter1 0xfffff8800e5dc5d4
BugcheckParameter2 0x0
BugcheckParameter3 0xfffff8000314f9ae
BugcheckParameter4 0x2

BugcheckCode 30
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffffa800188cdcc
BugcheckParameter3 0x1
BugcheckParameter4 0x3

BugcheckCode 30
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80003165c64
BugcheckParameter3 0x1
BugcheckParameter4 0x2210f929f

[jmwills]

Is there an nVidia Graphics card in this equation? If not I would start running chkdsk on all the drives to start eliminating HDD issues.

[ikon]

All I've ever done with those codes is search for them using google or Bing. Sometimes that helps; sometimes not.

[IndyLux]

No NVidia graphics - onboard intel (core i3). I can run the check disk tomorrow.

[IndyLux]

Do you guys know of any software to check for driver updates beyond windows update? I've updated everything I know to update.

[Joe_Miner]

Do you guys know of any software to check for driver updates beyond windows update? I've updated everything I know to update.

Indy:
I've found Intel's Driver Udate Utility useful from time to time.
Joe

[ikon]

Do you guys know of any software to check for driver updates beyond windows update? I've updated everything I know to update.

There are a number of so-called driver update sites on the web, but I don't trust them as far as I can throw them. To me they're pretty much snake-oil salesmen, trying to give you malware in the back door while promising great service through the front.

[IndyLux]

The Intel driver update utility was something I tried last night. I think it found a few things to update. As for the snakeoil products, I did try one (maybe two) just to see what they said and they both flagged EVERY Intel driver I had installed then pointed me to things that wouldn't install or were older than what I had. They also pointed to the Realtek HD Audio drivers that I do not use (I use Intel HD Audio) as well as some kind of Intel SSD rapid architecture thing that it wanted me to install 'prior' to the OS. Too late for that NOW. We'll see if the stuff I updated makes a difference. BTW Checkdisk scans were all 100% normal as was a MemTest so that's good!

[ikon]

It's always good to eliminate hardware issues as much as possible

[jmwills]

Here's what I do. Run Belarc Advisor to get an accurate inventory of your system. The report will show every piece of hardware and the current driver version. Research each one at the manufacturer's site and see what is available. I do no trust that update utilities.

[IndyLux]

Great tip on Belarc. Lots of info. Unfortunately, no new answers.

And I had a kernal error / BSOD reboot at 5AM when I wasn't even home and the monitor was off.

I did a disk cleanup yesterday and saw that there was about 300 megs of cache dumps. Any of you know where they're stored and how to analyze them?

[jmwills]

I would start tearing that build apart and put it back together....you know..."Frankenstein it".

[IndyLux]

Yeah, I kind of did that a month ago. I feel like it has to be one of the billions of capaciters on the motherboard. Is it crazy to buy a replacement (same model) to see if it helps?

[jmwills]

You could always RMA it and pay the restock fee.

[ikon]

And I had a kernal error / BSOD reboot at 5AM when I wasn't even home and the monitor was off.

You weren't home at 5am?? Oh wait, that's right, you have some vague affiliation with the medical community, don't you?

[IndyLux]

UPDATE: When I ran memtester before, it didn't find anything. I read somewhere that I should let MemTester run for more than a couple cycles. I let it run all day and at some point, it must have rebooted because it was back in Windows when I woke up. Think this points to a RAM problem? That would be an easy fix.

[jmwills]

I thought about RAM yesterday when posting but the Stop Error (BSOD) should have referenced it. An easy fix indeed.

[ikon]

It's worth a try. It could still be something else (e.g. quirky power supply) that caused the reboot, but it's a start. BTW, do you have the system plugged into a UPS? Your local power could cause problems too; a UPS would help mitigate that.

[IndyLux]

It IS on a UPS. Even if the memory doesn't fix it, I only have 2 gigs in that machine so I don't mind getting more ram and replacing what's in there. I did have an incident in the past where I questioned my power supply, but it turned out that the case wire for the power button had fallen off the motherboard (HOW?!?) so I may try another power supply in the future if the memory doesn't fix it. This all makes me feel like less of a PC builder.

[ikon]

Nah. We all get problem children like this once in a while. Some PC's just don't want to grow up and fly right.