Sign in with
Sign up | Sign in
Solved

BSOD on new build Windows 7 64-bit

Last response: in Windows 7
Share

I built this rig 3 weeks ago. Never had any glitches or problems. Just randomly today while web browsing I got a BSOD. I don't know how to access the BSOD files to see the cause. Can someone please help me troubleshoot, i've never dealt with this before. I don't overclock just so everyone knows. I ran prime 95 for about an hour with all passes and perfect temps. Please help.

More about : bsod build windows bit

Related ressources

dodger46 said:
Is the BSOD continuing to appear? If so try updating your Ethernet Driver, your fault very similar to this
http://answers.microsoft.com/en-us/windows/forum/window...


No it was just once (so far). I updated the atheros ethernet driver via gigabytes website. Hopefully its fixed. This is definitely a ethernet driver error and not a hardware error or anything of that nature right? I only ask because Im still under warranty with these parts so I want to find the source of this issue asap. BTW thanks for responding

mgx42 said:
No it was just once (so far). I updated the atheros ethernet driver via gigabytes website. Hopefully its fixed. This is definitely a ethernet driver error and not a hardware error or anything of that nature right? I only ask because Im still under warranty with these parts so I want to find the source of this issue asap. BTW thanks for responding

If it recurs in the future you may have to consider a hardware issue, it's not unheard of, but you may have to prove the rest of your setup before RMA-ing your Board. Driver most likely, but if you start getting random BSODs there may be a breakdown occurring elsewhere. Just have to wait and see!

dodger46 said:
If it recurs in the future you may have to consider a hardware issue, it's not unheard of, but you may have to prove the rest of your setup before RMA-ing your Board. Driver most likely, but if you start getting random BSODs there may be a breakdown occurring elsewhere. Just have to wait and see!


Thanks for the info lets just hope it was just the driver lol, I'll keep updating this thread if it happens again.

Best solution

Its a new PC and only 3 weeks old as you mentioned. This is normal for New Builds and there is nothing to worry about now.

It is purely a driver issue and you will just have to give it time. Eventually all or the most important drivers will be update via Windows update or other sources.

Its a good practice to check your hardware OEM websites at least once every 6 months for updates.

Nedal0 said:
Its a new PC and only 3 weeks old as you mentioned. This is normal for New Builds and there is nothing to worry about now.

It is purely a driver issue and you will just have to give it time. Eventually all or the most important drivers will be update via Windows update or other sources.

Its a good practice to check your hardware OEM websites at least once every 6 months for updates.


Thanks that makes me feel a bit better about the situation.
!