New HTPC Build... New BSOD Problems...

27 posts / 0 new
Last post
Offline
Joined: 1 Mar 2011
New HTPC Build... New BSOD Problems...

Hey guys, so i finally got my HTPC up and "running" but ive run in to some show stoppers.  Specifically getting BSODs all with kernal power errors causing shut down.  Ive researched the event viewer as much as possible and have narrowed the problem down to drivers.  Has anyone else run into this issue?  Is there a third party program to determine specifically what drivers are causeing the issue (windows update obviously isnt cutting it)? 

System specs are below, thanks for the help in finally deciding on the parts.

 

Win7 Home Premium (64-bit)

Gigabyte H67 mobo

Intel Core i5-2500k

Gskill DDR3 8gb (2x4gb)

60GB Vertex 2 SSD

Segate 2TB HDD

WD Caviar Green 2TB HDD

LG Blu-Ray ODD

Ceton InfiniTV4 Tuner

Offline
Joined: 30 Nov 1999

http://www.resplendence.com/whocrashed will read your memory dump after a crash and help you figure out what went wrong.

Aaron Ledger's picture
Offline
Joined: 6 Aug 2010

Have you installed drivers from the manufacturers? For example, if your board has Realtek NIC and audio chip, have you gone to Realtek and downloaded/installed the latest available drivers? Chipset drivers from Intel? etc.

Have you verified the RAM is good? You can run a test by clicking start and typing "mdsched" into the search box.

I had standby issues with a Vertex 2 drive when using Intel storage drivers. You may want to verify you are using the Microsoft Standard AHCI drivers. It also could have been my particular drive which I had to RMA for other reasons as well.

Senior Editor | @swoon_

Mike Garcen's picture
Offline
Joined: 1 Oct 2006

what power supply are you using? Try to get the system as MINIMAL as possible. So remove EVERYTHING except the OS drive, 1 stick of RAM...then give it a go. Then work 1 by 1 back.

Power supplies are KNOWN to cause this, as well as faulty memory.

Mike Garcen (shadymg) MissingRemote Editor-in-Chief Windows Entertainment and Connected Home MVP (formerly Media Center MVP) Twitter @mikegarcen MissingRemote on Facebook

Offline
Joined: 1 Mar 2011

well as far as i can see i have tried everything. removed all devices, flashed bios, ensured all drivers were up to date, etc.  Ran the memory check, passed the standard test.  It seems the problem now is with the intel hd graphics, i cannot connect an hdmi cable without it crashing, naming one of the graphics drivers as the cause.  This is concerning considering i JUST updated that driver, also tried rolling back the driver as it was working previously.  I am currently securely erasing the boot drive and doing a clean install of win7 hoping that there were some bugs left over when i reinstalled windows without wiping the drive first. I am on the verge of taking this to a professional because im about at my limit.

I have a rosewill 650w (80+) power supply, if that may be the cause.  Thanks for the help by the way

Offline
Joined: 30 Nov 1999

The Intel HD graphics driver is known to have that issue.  Version 8.15.10.2279 works for me, the newer versions crash on HDMI if I use them.

Mike Garcen's picture
Offline
Joined: 1 Oct 2006

i would try another PSU if you can (you can always return it if it ends up not being the problem). Good call on the fresh installation.

If you truly think it's the HDMI, then you could always install a separate HDMI video card from ATI or Nvidia and see if that works ok...not a solution but one to help you narrow it down to the board's graphics

Mike Garcen (shadymg) MissingRemote Editor-in-Chief Windows Entertainment and Connected Home MVP (formerly Media Center MVP) Twitter @mikegarcen MissingRemote on Facebook

mikinho's picture
Offline
Joined: 19 Mar 2007

oliverredfox wrote:

The Intel HD graphics driver is known to have that issue.  Version 8.15.10.2279 works for me, the newer versions crash on HDMI if I use them.

+1 I've had to help various people rollback to 2279 due to BSOD w/ the latest Intel HD Graphics drivers.

Mikinho | Missing Remote | Windows Entertainment and Connected Home MVP

Offline
Joined: 1 Mar 2011

So I reset everything back to factory defaults and ran the full memory diagnostic, coming up clean. Let the computer run with no open programs and was fine for about 24 hrs then I restarted it and opened a webpage, and bam, bsod. I got several of them during the reinstall, all of them for different random reasons. Is there a way to test the psu without replacing it?

Mike Garcen's picture
Offline
Joined: 1 Oct 2006

They sell a Power Supply Checker, but i think all that actually does is check to see if all the pins are working. At that point you'll be buying it anyways, so just buy a PSU and then return it if it's not the PSU (or to get the one you want). You don't need to install the PSU in the chassis, just connect the critical cables.

Mike Garcen (shadymg) MissingRemote Editor-in-Chief Windows Entertainment and Connected Home MVP (formerly Media Center MVP) Twitter @mikegarcen MissingRemote on Facebook

Aaron Ledger's picture
Offline
Joined: 6 Aug 2010

I recommend a multimeter. Just check your voltages with it while running and verify they are close to where they should be. ATX spec says +/- 5% tolerance on all positive voltages and +/- 10% on all negative voltages. If they're off by more, you have a bad PS for sure.

Senior Editor | @swoon_

Offline
Joined: 30 Nov 1999

Have you doubled checked to make sure your heat sink is on good?

The newer power supply testers will give you LCD readouts of the stats.  http://www.newegg.com/Product/Product.aspx?Item=N82E16899706001  But it tends to be cheaper and easier to just grab a 2nd power supply and return it if it wasn't the issue.

Mike Garcen's picture
Offline
Joined: 1 Oct 2006

oliverredfox wrote:

Have you doubled checked to make sure your heat sink is on good?

The newer power supply testers will give you LCD readouts of the stats.  http://www.newegg.com/Product/Product.aspx?Item=N82E16899706001  But it tends to be cheaper and easier to just grab a 2nd power supply and return it if it wasn't the issue.

Wow those have gotten way fancier than the old Antec one i still have that would just green light Tongue

Mike Garcen (shadymg) MissingRemote Editor-in-Chief Windows Entertainment and Connected Home MVP (formerly Media Center MVP) Twitter @mikegarcen MissingRemote on Facebook

Aaron Ledger's picture
Offline
Joined: 6 Aug 2010

FYI, from a review on that PS tester on Newegg (and this is why I never would trust any of these cheap black box testers and instead use a multimeter)

Don't trust this, get something better. The screen only lights up for the 20/24 pin connector and when you plug in a modular connector the device simply looks for any amount of voltage. It does not see if the voltage is too high or low, the light will light up green regardless. I connected my 5V rail to the 12V on this device and light was still green, same with connecting the 5V to the 12V on the device. Useless because if the PSU has 2 rails and one rail is failing this might fail to detect the other rail while your power supply kills off hard drives and optical drives, as it was doing in my case. A cheap voltmeter can put this device to shame.

 

Senior Editor | @swoon_

frijones's picture
Offline
Joined: 18 Dec 2006

Just to throw another idea out, I was having a problem with BSODs on my fresh install of W7 and it turned out that my GPU was overheating and causing it to lock up.  A little extra cooling and all problems were solved.  You might wanna run HWMonitor to see if something is overheating.

Offline
Joined: 3 May 2010

You might have a bad CPU.  I just upgraded my main HTPC to an i3-2100t and the first chip I received was bad.  One thing strange was that the CPU worked for the first install, then a couple of days later failed to boot.  I thought maybe corruption issue or driver issue, so attempted to re-install then discovered that Windows install media wouldn't boot.  Of course, I had to rebuild the system several times, using different motherboard, different power supply, different RAM, etc, before it boiled down to a bad chip.

Offline
Joined: 1 Mar 2011

I really appreciate all the coments.  Just dug out my multimeter and checked the connecteions, they were all right in line with the specs.  I kind of doubt its a bad cpu as it only seems to fail when im doing something with a higher load on the gpu (usually).  I just switched channels for the memory too, hoping that will make a difference. As far as the GPU overheating, i have 2x 120mm and 2x, 80mm fans so i really cant see that being a problem since the h67 chipset was built to be run without a cooler. anyone got any other ideas??

By the way, just got the logitech dinovio mini.  awesome...

skirge01's picture
Offline
Joined: 21 Dec 2006

I know there have been a number of suggestions here, so things may have slipped by.  Did you try rolling back the graphics drivers, as was pointed out here?  If that doesn't do it, I would strongly suggest trying another PSU, even though the readings came back ok.

captain_video's picture
Offline
Joined: 6 Jul 2007

Have you installed Win 7 Service Pack 1?  I had all sorts of BSOD issues before I updated to SP1.  Now my system is considerably more stable with no BSODs.

Mike Garcen's picture
Offline
Joined: 1 Oct 2006

best way to test the CPU (and PSU really) is to run a burn-in test. I forget which ones are out there since it's been a while since i've been an OEM, but that will peak out your system for hardware stability.

i believe he said he reinstalled windows clean as well. When you reinstalled, you should not install any drivers until you have a chance to do some testing.

Mike Garcen (shadymg) MissingRemote Editor-in-Chief Windows Entertainment and Connected Home MVP (formerly Media Center MVP) Twitter @mikegarcen MissingRemote on Facebook

Offline
Joined: 30 Nov 1999

Prime95 is good for stress testing.  You run it off 'Ultimate Boot CD for Windows' to eliminate your Windows 7 build as being a test variable.

Offline
Joined: 1 Mar 2011

So after doing some digging in the Intel forums it seems that this problem is rampant with people using the H67 chipset's integrated GPU.  Intel is trying to come up with a driver that works but seems to have yet to be able to.  Looks like i might bite the bullet and buy a graphics card for a computer designed not to need one.  So word to the wise for anyone thinking about the H67, not ready for use without a graphics card apparently.

Thanks agian for the help, definetly learned alot.  Ill let you all know if a graphics card solves the problem.

Offline
Joined: 3 May 2010

I see you've got all that memory there (8GB), and it would seem a shame to waste over half of it, but you could go 32-bit temporarily until Intel fixes the 64-bit side of things.  From what I can tell so far, 32-bit doesn't have the issue... at least not with my Intel motherboard based core i3-2100T and pentium G620T systems.

mikinho's picture
Offline
Joined: 19 Mar 2007

* Knock on wood *

Only a single of my DH67 or DH61 boards were affected and rolling back to an older Intel HD Graphics driver resolved it for me.

Mikinho | Missing Remote | Windows Entertainment and Connected Home MVP

Offline
Joined: 1 Feb 2007

Thanks for all the information in this thread. I built my new HTPC based on the DH67CF and i5-2400s combo. Everything was working flawlessly for nearly a month, even the CIR module. I was gearing up for recording all the E3 coverage when I somehow messed up permissions for the workgroup I was sharing and locked out the Media Center service. I had to reinstall and used the latest Intel drivers (after deleting the old ones). Then I started running into BSOD's, corrupted guide listings, the CIR wouldn't work -- it's a nightmare! I just installed the 8.10.15.2219 drivers that came with the board -- hopefully this will work. If not, I guess I can do another reinstall using 32-bit drivers. I about ready to drop this nonsense and go back to an H55 micro-ATX board (or jump to AMD).

Offline
Joined: 1 Mar 2011

Hey thanks again for all the comments, I believe I have solved the problems. it was a combination bad intel graphics driver ( intel's fault) and some faulty memory. Some cannibalized memory and a graphics card seem to have soled the problem.

Pretty disappointed that intel would release the integrated gpu knowing it can't support hdmi on x64, kinda defeats the purpose of a media chipset

mikinho's picture
Offline
Joined: 19 Mar 2007

Taylordown wrote:
Pretty disappointed that intel would release the integrated gpu knowing it can't support hdmi on x64, kinda defeats the purpose of a media chipset

Driver conflicts happen, it definitely isn't across the board either.  I have anywhere from 4-6 Sandy Bridge systems running, all x64.  I had the BSoD issue on 1 system and reverting back one driver revision fixed it.  That was my only non-Intel board, an ASUS that had it.

Mikinho | Missing Remote | Windows Entertainment and Connected Home MVP

Login or register to post comments
Website design by Yammm Software
Powered by Drupal