How to find cause of BSOD??

[earthbrown]

Getting BSOD on a newly built machine, had 1 problem with g-link driver, removed that ran fine, then it came back.

BSOD only on startup, and it will repeat startup, and eventually start on the 2 or 3rd try. Once up she runs FLAWLESS.

any ideas on how to find problem?



K

[SatCam]

did you build it or did you buy it? try to reinstall windows and start from scratch and install each driver one at a time.

safe mode should get you into windows without crashing for now

[earthbrown]

did you build it or did you buy it? try to reinstall windows and start from scratch and install each driver one at a time.

safe mode should get you into windows without crashing for now

ugg, thats what I was afraid of.

there is no magic utility to figure it out?

K

[Death Metal Moe]

http://www1.istockphoto.com/file_thumbview_approve/964428/2/istockphoto_964428_horseshoe_magnet.jpg

Stick one of these directly on the processor and it will suck the problem out of the computer.

[bnceo]

Can you please list all the parts on your PC? It will help us examine it a little better.

[KC2OSO]

What's the OS? Maybe Jon or Mikey could put a sticky up there to have folks state the OS/Service Pack/Proc Type/Ram/HD Size yadda and anything else relevant when the question is posted.

So the drivers are incompatible with the OS? Can you remove the device in safe mode? Or just pull it? Being GLink I assume its a wireless card spazzing out?

[MadMatt]

What are the codes you are getting on the BSoD? Where it says:

0x000000?? (0x00000????, 0x000000????, 0x000000????, 0x0000000???)

All you need is the first code on the outside of the parenthesis (in blue above). The other four sets of 0x00????????? just point to where the error has occurred. That first set on the outside is the error code itself.

Also, is it giving you a reason for the shutdown near the top of the error screen? Sometimes it will say Page_Fault_Error or something like that. It is usually words separated by underscores.

Both the error name (if there is one - sometimes there isn't) and the code outside the parenthesis will give you/us the info to point you in the right direction.

[JustJon]

There are log files created when you boot up and reboot after a crash. You can try checking those.

[bnceo]

BSOD show log files. Crashes like freezes don't (at least through my experiences).

[JPMNICK]

could be bad RAM

[earthbrown]

MB Abit 1L9 Pro
945p chipset(I know the cheap one)
Pentium Dual core 3.ghz x2
Seagate 160gig ide hd (from old computer but completely wiped before install)
Lite-on DVD drive
3 gig of ddr2-667mhz ram
xfx geforce 8600gt 512
nyko airflo ps2 style usb controller
logitec wheel mouse usb

got this from event viewer.
Error code 100000c5, parameter1 08458c00, parameter2 00000002, parameter3 00000001, parameter4 8054afd2.

The computer is 100% fine when it starts up, I can play COD4 with 100% no problems.

When I power up or restart I get the BSOD.


Thanks guys

[bnceo]

It would not shock me if it was a bad install of the operating system. Sometimes, stupid files tend to do that. I don't think it's a heating issue either. It might be a bad motherboard. That's the only product really that can be fishy. No clue on XFX does their VGA cards, I usually stay with BFG or eVGA.

A clean install with installing fresh drivers (brand new ones from the mfg website might do the trick too. I even get go crazy and install the Microsoft .Net framework one SP at a time.

[MadMatt]

If you are getting a 0x000000c5 error, that usually means a corrupt driver. I frequently check Jim Eshelman's tech site (http://aumha.org/a/stop.htm)that lists almost every error you can run into. Here is an excerpt RE: your BSoD:

0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt occurred to touch invalid memory at a process IRQL that is too high. This is almost always caused by drivers that have corrupted the system pool. If you’ve recently installed any new software, check to see if it’s properly installed; and check for updated drivers on the manufacturer’s web site.

You can also find a lot of info by just popping the 'error code 0x000000c5' or 'error code 100000c5' into Google or another search engine.

Since you just reformatted/built your system it may be tough to determine exactly which driver is flinxed, but at least you have a starting point. Let us know if you need more. :thumbup:

[badmonkey]

So it's not BSOverDose caused by his posts in the political forum?

:unsure:



















:tongue: