General [M]ayhem

Go Back   General [M]ayhem > Real Time Sub-Forums > CompuGlobalHyperMegaNet
Register Members List Mark Forums Read [M]erchandise Calendar

Reply
 
Thread Tools
MrCodeDude
Epox Whore
 
Horrible Windows XP BSOD Problems

I'm updating my Uncle's computer and I'm running into quite a bit of trouble.

I installed a wireless card and NEC 3550 DVD burner. Installed their drivers, fixed a couple of network concerns and then installed DVD Decrypt and DVD Shrink. Everything was running great, test ripped a DVD.

Then I went to show my uncle and we started getting BSODs. A lot of them. Note that this machine was working perfectly fine beforehand.

The BSOD reads something along the lines of:
Quote:
STOP 0x000000F4 (0x00000003, 0x82143978, 0x82143AEC, 0x805F9F88)
I didn't bother copying down the 5 error codes after the F4 one, but the last three always alternated.

First thing I did was do a System Restore, that didn't solve the problem.

So then I disabled the new DVD burner, that didn't solve the problem.

I disabled both DVD drives, that didn't solve the problem.

I took out the wireless card, that seemingly solved the problem.

I repositioned the wireless card (which has been working great), re-installed all the drivers, even flashed the firmware for the 3550A. But then DVD Shrink stopped working, it kept giving me this "Error occured with the I/O device" etc. So I thought I fixed that, but now when I load up DVD Decrypt anytime and start to rip it, it gives me that original BSOD.

The rig specs are:
AMD XP 1800+ w/ ECS K7S5A
512mb Memory
GeForce4 MX
Windows XP SP2

The computer is running fine right now (and it's been on for about 15 minutes), but when I leave (I'm in Ohio, but live in California), I can't have him dealing with often BSODs.
__________________
If at first you don't succeed, give up and make a thread. :rolleyes: - baloneyflaps
Old 08-22-2006, 07:24 PM MrCodeDude is offline  
Reply With Quote
#1  

Advertisement [Remove Advertisement]

zumpiez
This is what Bush is doing to our Freedoms and Country!
 
Sometimes a BSOD will tell you what file blew up. A .sys or some such. This can be helpful in isolating what's up.
__________________
Grand supreme leader of the zumpiez army. FEAR US.
Old 08-22-2006, 07:37 PM zumpiez is offline  
Reply With Quote
#2  

MrCodeDude
Epox Whore
 
I think the first time it BSOD'd it said atapi.sys.
__________________
If at first you don't succeed, give up and make a thread. :rolleyes: - baloneyflaps
Old 08-22-2006, 08:02 PM MrCodeDude is offline  
Reply With Quote
#3  

Syk0tiK
Mongoloidal cunt of Lindsay Lohan proportions who can't fathom the rules. <3 Sarah
 
atapi is the IDE controller and/or cdrom driver thingy.

run a windows repair, see if that helps.
Old 08-22-2006, 08:05 PM Syk0tiK is offline  
Reply With Quote
#4  

MrCodeDude
Epox Whore
 
Run this: /sfc scannow ?
__________________
If at first you don't succeed, give up and make a thread. :rolleyes: - baloneyflaps
Old 08-22-2006, 08:08 PM MrCodeDude is offline  
Reply With Quote
#5  

drasticactions
 
I've seen bugcheck F4 mean a disk drive failure. check all the IDE cables, try scandisk, try removing the new DVD drive, etc. If none of these work, the new DVD drive or some bad connections may have fried the hard drive.

you might get more details by making a minidump, loading it up in WinDBG and running "!analyze -v".
Old 08-22-2006, 08:19 PM drasticactions is offline  
Reply With Quote
#6  

Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT -7. The time now is 06:06 PM.



Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.