windows keeps on crashing

attgig · 03-23-2009, 06:03 PM

I have vista with a homebrew pc, and my vista keeps on crashing. it happens at least twice a week.
I leave my computer on, so when I see it, I get a black screen like when it boots up, and says it can't find a hard disk.

I get this error once turn off the computer and turn it back on:

Code:

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.0.6001.2.1.0.256.1
  Locale ID:	1033

Additional information about the problem:
  BCCode:	1000007e
  BCP1:	FFFFFFFFC0000005
  BCP2:	FFFFF80001E99AEA
  BCP3:	FFFFFA60005AFA08
  BCP4:	FFFFFA60005AF3E0
  OS Version:	6_0_6001
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini032309-01.dmp
  C:\Users\matt\AppData\Local\Temp\WER-39578-0.sysdata.xml
  C:\Users\matt\AppData\Local\Temp\WER1C3D.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

and i hit check for a solution, and it just disappears.
once, it actually came back, and said my raid drivers needed to be updated, which i did, but crashing continued.

I also checked those files, but the first one is bunch of binary junk, and the other two aren't there.

I'm assuming it's something with my raid.

this is what i got in my device man.

TIA

Jeffbx · 03-24-2009, 05:29 AM

What RAID are you using - hardware or software, and what level (0, 1, 5)?

That message doesn't help too much - it pretty much just says there was a crash. The real data is in that mini.dmp file, but you need someone to read it for you.

I'd recommend 2 things - first, set your computer to stop at a serious error. That should allow you to get the actual info on the bluescreen. To do this, go to control panel, System, Advanced, Startup and Recovery Settings, and under 'system failure', uncheck 'automatically restart' and check 'write a log file'. (sorry, those instructions are for XP. Vista should be similar). Next time you get the bluescreen, google the error message on the screen.

Second, check your event viewer for more detailed info (administrative tools, Event Viewer). Look for errors written at the time of the crash, and google those.

Good luck!

attgig · 03-24-2009, 09:46 AM

I'm using the onboard raid that's built into the motherboard - ABIT IP35 Pro LGA 775 Intel P35 ATX Intel Motherboard - Retail

attgig · 03-24-2009, 12:30 PM

just happened again. i got the xml file and the tmp.version.txt files this time.

the xml file shows:
http://attgig.com/stuff/WER-34218-0.sysdata.xml

and the tmp.version.txt file shows:

Code:

Windows NT  Version 6.0 Build: 6001 Service Pack 1
Product (0x1): Windows Vista (TM) Ultimate
Edition: Ultimate
BuildString: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033

nothing too useful. I'm trying the other thing you told me about not restarting.

attgig · 03-24-2009, 12:33 PM

Quote:

Originally Posted by Jeffbx

Second, check your event viewer for more detailed info (administrative tools, Event Viewer). Look for errors written at the time of the crash, and google those.

Good luck!

hmmm... the only thing i see in the event viewer was someone trying to log onto my iis-ftp that I have on my box (they couldn't get in - username/password invalid).

....

that worries me on a different level, but nothing regarding hardware...

Jeffbx · 03-24-2009, 05:15 PM

Heh - keep an eye on your firewall!

Since the error is not captured in the event viewer (which is sometimes the case if the machine stops before it has a chance to write the log) the most useful info for YOU will be the actual text of the blue screen when it crashes.

The errors on the blue screen will at the very least give you a direction to look, and best case you may find the exact error with a solution on Google or in the MS KB.

attgig · 03-30-2009, 04:20 PM

ok. got the bsod:
found my computer to have this error message:

then, I just hit restart, and got this message:

then, I shut down, and let it stay shut for a few minutes, restarted, and it returned to normal....

i googled the error messages, and most posts just says drivers are bad (but the bsods don't say which driver). one thing that i did see was bad ram. I'll be running some tests later tonight. but anyone have any other ideas?

TIA

LPMiller · 03-30-2009, 04:59 PM

have you updated the bios recently? Or is there an update available? It may be firmware causing the problem. It could also be a flaky cable, though I'd guess that was not terribly likely.

InfiniteNothing · 03-30-2009, 06:44 PM

Long shot but worth mentioning: I got an error like that once with a bad PCI wireless card.

attgig · 03-31-2009, 09:39 PM

i'm checking to see if i have firmware updates, and any other rogue cards/drivers now... I'm also doing windows update.
but... this is my new bsod error:

Jeffbx · 04-01-2009, 06:31 AM

That sucks... that last error could still be either hardware or a driver issue.

You might want to try to check for updated drives for all of your devices - video, network, system board, etc.

renovation · 04-02-2009, 06:55 AM

look at the mb really close -it could be the problem .i had one not long ago doing that. it turned out a usb header on the mb smoked was really hard to see the damage .but sure enought it there right between the pins a black speck from a short. also had the mouse and keyboard lock up for no reason at all.i had to do a reboot things ran fine for hours and then i walk away and a computer would be locked up. sometimes its best to just swap out a mb then spend days trying to find a problem.

attgig · 07-07-2009, 02:48 PM

Quote:

Originally Posted by InfiniteNothing

Long shot but worth mentioning: I got an error like that once with a bad PCI wireless card.

thanks IN.

so, since then, I had a new driver for the raid contorller come out, and i thought i was good.

but then, it started crashing again.

I then realized the fan on my vid card died, and so, i replaced the vid card. sofarsogood *knocks on wood*

MrGreg · 07-07-2009, 05:37 PM

Maybe it was an overheating issue. Would explain the "wait a few minutes and it works again" aspect.

attgig · 07-16-2009, 01:04 PM

ok, I'm going to chalk it up to the bad vid card. 0 crashes since.

thanks everyone for your help. I'm now back to playing spider solitaire without any problems. :-)

rajatQ2 · 07-16-2009, 06:59 PM

cool, glad it wasn't so difficult in the end!

Other things I would have done would be to run SeaTools which is like a bootable HD Diagnostic Utility, and Memtest, which is a bootable memory checker. They take a couple of hours but smoke out all HD and memory problems, as well as a lot of mobo problems too. Itw ouldn't have found your graphics card issue though.

03-23-2009, 06:03 PM	#1
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	windows keeps on crashing I have vista with a homebrew pc, and my vista keeps on crashing. it happens at least twice a week. I leave my computer on, so when I see it, I get a black screen like when it boots up, and says it can't find a hard disk. I get this error once turn off the computer and turn it back on: Code: Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF80001E99AEA BCP3: FFFFFA60005AFA08 BCP4: FFFFFA60005AF3E0 OS Version: 6_0_6001 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\Mini032309-01.dmp C:\Users\matt\AppData\Local\Temp\WER-39578-0.sysdata.xml C:\Users\matt\AppData\Local\Temp\WER1C3D.tmp.version.txt Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409 and i hit check for a solution, and it just disappears. once, it actually came back, and said my raid drivers needed to be updated, which i did, but crashing continued. I also checked those files, but the first one is bunch of binary junk, and the other two aren't there. I'm assuming it's something with my raid. this is what i got in my device man. TIA __________________

03-24-2009, 12:30 PM	#4
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	just happened again. i got the xml file and the tmp.version.txt files this time. the xml file shows: http://attgig.com/stuff/WER-34218-0.sysdata.xml and the tmp.version.txt file shows: Code: Windows NT Version 6.0 Build: 6001 Service Pack 1 Product (0x1): Windows Vista (TM) Ultimate Edition: Ultimate BuildString: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Flavor: Multiprocessor Free Architecture: X64 LCID: 1033 nothing too useful. I'm trying the other thing you told me about not restarting.

03-30-2009, 04:59 PM	#8
LPMiller Chief News Editor & Master of His Domain Join Date: Aug 2000 Location: Minnesota Posts: 8,161	have you updated the bios recently? Or is there an update available? It may be firmware causing the problem. It could also be a flaky cable, though I'd guess that was not terribly likely. __________________ lpmiller Chief News Editor Nobel Prize Nominee Reverend in the Universal Life Church Once Shot A Man For Snoring Too Loud Way Too Lazy To Change His Signature "The strength to change what I can, the inability to accept what I can't, and the incapacity to tell the difference." - Calvin and Hobbes

03-30-2009, 06:44 PM	#9
InfiniteNothing Chief of Naval Operations Join Date: Aug 2002 Location: San Diego Posts: 10,086	Long shot but worth mentioning: I got an error like that once with a bad PCI wireless card. __________________ As for our common defense, we reject as false the choice between our safety and our ideals.

03-31-2009, 09:39 PM	#10
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	i'm checking to see if i have firmware updates, and any other rogue cards/drivers now... I'm also doing windows update. but... this is my new bsod error: Last edited by attgig : 03-31-2009 at 09:44 PM.

03-24-2009, 05:29 AM	#2
Jeffbx Fleet Admiral Join Date: Mar 2000 Location: Michigan Posts: 9,390	What RAID are you using - hardware or software, and what level (0, 1, 5)? That message doesn't help too much - it pretty much just says there was a crash. The real data is in that mini.dmp file, but you need someone to read it for you. I'd recommend 2 things - first, set your computer to stop at a serious error. That should allow you to get the actual info on the bluescreen. To do this, go to control panel, System, Advanced, Startup and Recovery Settings, and under 'system failure', uncheck 'automatically restart' and check 'write a log file'. (sorry, those instructions are for XP. Vista should be similar). Next time you get the bluescreen, google the error message on the screen. Second, check your event viewer for more detailed info (administrative tools, Event Viewer). Look for errors written at the time of the crash, and google those. Good luck!

03-24-2009, 09:46 AM	#3
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	I'm using the onboard raid that's built into the motherboard - ABIT IP35 Pro LGA 775 Intel P35 ATX Intel Motherboard - Retail

03-24-2009, 05:15 PM	#6
Jeffbx Fleet Admiral Join Date: Mar 2000 Location: Michigan Posts: 9,390	Heh - keep an eye on your firewall! Since the error is not captured in the event viewer (which is sometimes the case if the machine stops before it has a chance to write the log) the most useful info for YOU will be the actual text of the blue screen when it crashes. The errors on the blue screen will at the very least give you a direction to look, and best case you may find the exact error with a solution on Google or in the MS KB.

03-30-2009, 04:20 PM	#7
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	ok. got the bsod: found my computer to have this error message: then, I just hit restart, and got this message: then, I shut down, and let it stay shut for a few minutes, restarted, and it returned to normal.... i googled the error messages, and most posts just says drivers are bad (but the bsods don't say which driver). one thing that i did see was bad ram. I'll be running some tests later tonight. but anyone have any other ideas? TIA

04-01-2009, 06:31 AM	#11
Jeffbx Fleet Admiral Join Date: Mar 2000 Location: Michigan Posts: 9,390	That sucks... that last error could still be either hardware or a driver issue. You might want to try to check for updated drives for all of your devices - video, network, system board, etc.

04-02-2009, 06:55 AM	#12
renovation Admiral Join Date: Jan 2003 Location: You could pick up Lindsay Lohan for less than a intel 990x, and still have money left over to bail her outta jail Posts: 5,029	look at the mb really close -it could be the problem .i had one not long ago doing that. it turned out a usb header on the mb smoked was really hard to see the damage .but sure enought it there right between the pins a black speck from a short. also had the mouse and keyboard lock up for no reason at all.i had to do a reboot things ran fine for hours and then i walk away and a computer would be locked up. sometimes its best to just swap out a mb then spend days trying to find a problem. __________________ You could pick up Lindsay Lohan for less than a intel 990x, and still have money left over to bail her outta jail Last edited by renovation : 04-02-2009 at 07:04 AM.

07-07-2009, 05:37 PM	#14
MrGreg Captain Join Date: Jul 2000 Location: Beaverton, OR Posts: 1,529	Maybe it was an overheating issue. Would explain the "wait a few minutes and it works again" aspect. __________________ -The nerd formerly known as vectorcalculus

07-16-2009, 01:04 PM	#15
attgig Chief of Naval Operations Join Date: Jun 2000 Location: the burbs of baltimore Posts: 11,924	ok, I'm going to chalk it up to the bad vid card. 0 crashes since. thanks everyone for your help. I'm now back to playing spider solitaire without any problems. :-)

07-16-2009, 06:59 PM	#16
rajatQ2 Commander Join Date: Jan 2001 Location: boston, ma Posts: 1,020	cool, glad it wasn't so difficult in the end! Other things I would have done would be to run SeaTools which is like a bootable HD Diagnostic Utility, and Memtest, which is a bootable memory checker. They take a couple of hours but smoke out all HD and memory problems, as well as a lot of mobo problems too. Itw ouldn't have found your graphics card issue though. __________________ Find some free Comcast or Verizon on-demand movies to watch at home tonight: www.movie-cat.tv

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

User Name
Password
Remember Me?