normally that particular error msg... I believe it's "IRQL_NOT_LESS_OR_EQUAL" will be followed by the name of the device driver that caused the crash dump. It's not immediately below that string of text... I think it's halfway down the blue screen and it's easy to miss, especially if you have it set to reboot after BSOD. There's a KB article on it on MS's support site. Could have been a complete fluke, for all we know... does it do it regularly or is that the first time it's happened? Did you change anything prior to it happening? (new soundcard/video card/mobo drivers?)Here's the link to the KB article in question. Basically it's just windows blowing up when a driver tries to touch an area of memory that it's not allowed to touch.
thanx for your help, no, there never was a device listing... however... i noticed, having the case apart and eventually watching it... that there was a resistor that started to glow after a few minutes of being on. As soon as that happened, the whole system started going hay wire... so i have since bought a new motherboard and harddrive so that i could raid the system... mmmm
but thanks again.
Gigabyte GA-7m400 Pro2 Mainboard
Athon XP 2200, Topped with a CoolerMaster Jet 7
1GB Crucial PC3200 Dual Channel DDR
Ati Radeon 9500 Pro
Creative SoundBlaster Audigy 2 Gamer
DVD Drive (Soon to be upgraded to a burner, Plextor 8x?!?)
CD Burner 48x
2 WD Caviar 120GB, 8MB buffer Stripe partition via onboard Raid controller
Supports SATA RAID as well, but too broke to upgrade to a couple of those drives.
4 80mm fans, 1 120mm fan
Shockingly fast, amazing speed in all areas. stays cool, 3dmarked at 3594pts
Ep, glad to see you come back and tidy up...did want to ask a one day favor, I want to enhance my resume , was hoping you could make me administrator for a day, if so, take me right off since I won't be here to do anything, and don't know the slightest about the board, but it would be nice putting "served administrator osnn", if can do, THANKS