• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

BSOD in Windows XP :(

CDdude55

Crazy 4 TPU!!!
Joined
Jul 12, 2007
Messages
8,178 (1.26/day)
Location
Virginia
System Name CDdude's Rig!
Processor AMD Athlon II X4 620
Motherboard Gigabyte GA-990FXA-UD3
Cooling Corsair H70
Memory 8GB Corsair Vengence @1600mhz
Video Card(s) XFX HD 6970 2GB
Storage OCZ Agility 3 60GB SSD/WD Velociraptor 300GB
Display(s) ASUS VH232H 23" 1920x1080
Case Cooler Master CM690 (w/ side window)
Audio Device(s) Onboard (It sounds fine)
Power Supply Corsair 850TX
Software Windows 7 Home Premium 64bit SP1
I was on the Internet then all of a sudden my PC just flashed a BSOD and my whole PC restarted.

Plus my BIOS didn't show my CPU when it came back on, after that i have not seen anything bad happen.

Here's some of the Error info shown in Event Viewer:

Error Code:1000008e Event ID:1003 Category: (102)


Couldn't read the BSOD info, went really fast.
 
Do you have anything overclocked?
 
^ i know for a fact this guy doesnt overclock. So thats that ruled out at least.
 
Control Panel--> Administrator Tools --> Event Viewer. Look in there for warnings or errors.
 
Control Panel--> Administrator Tools --> Event Viewer. Look in there for warnings or errors.

googled it and in 2 minutes found what most believe the issue is....why cant ppl use google...is it hard to spell?;)
 
Control Panel--> Administrator Tools --> Event Viewer. Look in there for warnings or errors.

Ya, its in there, i put the info of it in my original post.
 
googled it and in 2 minutes found what most believe the issue is....why cant ppl use google...is it hard to spell?;)

I actually did Google it, but i couldn't find a for sure answer.
 
You would need a CD.Download the ISO and then burn it onto a CD and boot from it.
 
says it was a driver not the ram!
 
says it was a driver not the ram!

Sorry Peety :oI didn't check out your google search, I had done my own and some of them pointed to RAM being the problem but I see with yours that some point to drivers as well.

Can't do no harm checking the RAM anyway.
 
Sorry Peety :oI didn't check out your google search, I had done my own and some of them pointed to RAM being the problem but I see with yours that some point to drivers as well.

Can't do no harm checking the RAM anyway.

no problem just the 3 or so I read said that the users did try memtest to no avail. then it was directed to a driver error.

And +1 memory is always the #1 thing to look at and there is absolutely no harm in ruling things out!
 
Back
Top