What is wrong with my Comp...Help!!!

Enigma422

Limp Gawd
Joined
Mar 10, 2005
Messages
162
I've had this wierd and annoying problem with my computer for the past couple of days. The system in question is in my sig. If you don't feel like reading this whole thing the latest set of issues is in the last three paragraphs of this post. These events happened in series and I am not sure if they are connected in anyway, but I'll start from the begining.

It all started about a month ago, but back then I didn't think much about it. I am spending the summer with family out in California so I decided to bring my computer along. I packed it pretty good in the box my case was shipped in and checked it in on the airplane. Needless to say, when I arrived in California the box was in poor condition, and when openning the box my case window had popped off and my radiator came loose. Anyway, cosmetic damage and I was able to get things working.

About two weeks ago, when I downloaded the BF2 Demo and installed the 77.30 drivers on my computer my computer would all of a sudden start locking up randomly. Mostly whenever I either leave it for a while after playing a game or after I restart F@H after finishing a game and it would always lock up in the same way. First the computer would really slow down, then my mouse would not move at all, then the graphics would go bad (down to 256 color) and blue screen.

Anyway, this continued on even with the 77.50 and 77.72 drivers, it was an annoying problem, but it was just a matter of restarting the computer.

The real problem started happening last week after I installed the full version of BF2 on my computer. The first day I was using the program it ran fine, but on the second day I couldn't get it to run at all. As soon as I would start a level or within 5 minutes of starting a level the computer would either BSOD or the graphics would go bad and BSOD. I tried reinstalling the game and my graphics drivers and still the same thing. This was all on a non-OCed system. I even ran MemTest and no errors. On another attempt to fix my problem I noticed that the BSOD game me an error involving my RAID controller. So I go to uninstall all of my nVidia drivers and reinstall it. I go into safe mode to do the uninstallation and used Driver Cleaner to make sure when I reinstall it's a clean installation. When I go to restart my computer after cleaning out the nVidia drivers I immediately get a BSOD after the Windows boot screen shows. So I try to do it in safe mode, this BSODs to after a certain point in the OS load (don't remeber exactly where it does it). I turn off my computer and decide to call it a night.

When I got to work on my computer the next morning I notice a puddle of water on my sound card that had leaked from fittings on the bottom graphics card. I think, so this is the cause of all my problems. I remove the card, do a partial drain of the system and reattach my tubing making sure that the clamps are firmly attached. I then refilled my system and allowed it to bleed for 2 days to make sure that it did not leak. I even shook the tubing a little bit to make sure things were still firmly attached. While this happened, I had my sound card out and allowed it to dry.

This past Monday I put everything together and went to restart my system. Well I get the same problems I was getting earlier with Windows BSODing while loading even when trying to go into safe mode. I decided to reinstall the OS. This is where the problem gets wierder. No matter how many times I tried I could not complete installing Windows. I thought maybe my hard drives went bad so I ran Western Digital's quick diagnostic test to check my hard drives. No errors. So I disconnect and reconnect the SATA cables and try to reinstall again. Same thing, the installation would BSOD either when detecting the devices or at the end when it is finishing the installation. I then thought that maybe its my sound card, so I take it out, but same thing. I decide to do an extended test on both of my hard drives, and again they come back with no errors.

So I start to suspect my PSU, which is the last thing I would suspect since it is a PCP&C PSU. I started by disconnecting the BayBus on my computer, and low and behold I get thorugh the installation, but it is still not stable. While installing SP2 it crashes. This time I catch that the crash was caused by "win32k.sys." I once again try the installation process, but this time it crashes at the end of installation, but this time caused by "ntfs.sys." I try a third time and this time it installs. Even installed SP2 the nF4 drivers and my graphics drivers. I thought everything was in the clear. Then I go an install Windows updates and BSOD, caused once again by win32k.sys. I even try to incease my voltages to the voltages they were running at when OCed, but stil the same thing, and the crashes seemed to either caused by win32k.sys or ntfs.sys. Ocassionally others would cause the crash, but these two seem to the coming up the most in the BSODs I am getting. I even tried installing without the RAID array, but same thing.

While all of this is happening I start to notice a click right before my computer would crash. I am not sure if it is coming from my PSU or my hard drives since their right next to each other, but it sounds more like a click that a power supply makes than a hard drive. Plus the hard drive diagnostics came back good so I don't think its my hard drives.

Right now I am suspecting that my PSU is going bad, and there is a voltage drop when I hear the click that causes my system to crash, but I can't find my multimeter at the moment to verify this. This would suck because for a $240 PSU I shouldn't have to be dealing with any of this. I'm all out of ideas and was wondering if you guys can suggest anything else. I just got BF2 and managed to get 2 games in before this all started happening and I am really itching to get back on. Any help is appreciated. Thanks.
 
Who knows what was damaged when you shipped it on the airplane. That was probably the worst route to go. They call them throwers in Fight Club for a reason. I've seen everthing from cracked cores, to damaged harddrives from people putting their drives through airline luggage. You're just going to have to isolate it down and test each component until you find out what's wrong. And with that leak, who knows what else may have gotten water on it, splashed and short out at any point. There's a good chance the water on the sound card also caused damage to something else.
 
At first I was going to recommend rolling back the drivers to see if that would help. Then you got to your windows install problem. Got a spare hard drive? Try to install windows on a spare drive and compare the results.

The platters could have easily been damaged by being knocked around.

And you obviously have a nice rig, but are you sure you have enuff RAM? I dont know what BF2 is. What are its requirements? New games coming out are becoming bigger and bigger RAM hogs. Everquest2 recommends a MINIMUM of 1 gig.
 
It's very possible that it is the PSU. But then again, PCP&C's are really good. What I would do, is find a friend with a computer that works, and start changing all of his parts with yours. When his computer starts fucking up after a new edition, you have your culprit. Anyway, that totally sucks ass, and I'm sorry to hear it. :( Never ship sensitive equipment on a passenger plane. Heheh.
 
upriverpaddler said:
At first I was going to recommend rolling back the drivers to see if that would help. Then you got to your windows install problem. Got a spare hard drive? Try to install windows on a spare drive and compare the results.

The platters could have easily been damaged by being knocked around.

And you obviously have a nice rig, but are you sure you have enuff RAM? I dont know what BF2 is. What are its requirements? New games coming out are becoming bigger and bigger RAM hogs. Everquest2 recommends a MINIMUM of 1 gig.
It really isnt that likely hard drive issues, IIRC they are rated to survive ~100Gs of impact when off.

Have you reseated everything? The first few errors, bsods etc, sound like overheating, and the install issue is nearly always ram in my experience. Try memtest86 after reseating everything.You shipped it with the water out right? God knows where it could have gotten if you didnt, also if your window/rad was rattling around you may have chipped a die on one of the mem chips.
 
I have switched the positions of the memory chips, but I have not yet tried it with just one DIMM. I just zeroed out all of my drives and will reattempt again, if that doesn't work I'll try with just one drive at a time. I don't think that the damage came from the plane, since it was working fine for the first week or so, but then this problem is so puzzling to me who knows. Thanks for all your suggestions.
 
Okay, I tried it with one hard drive at a time and with both hard drives I get a BSOD whenever I install Windows. One thing I noticed though is that whenever I unplug my Baybus about 60% of the time I am able to sucessfully install Windows, but the installation is unstable. However, when I have my Baybus plugged in I can't get past the installation no matter how many times I try. This is making me suspect the PSU is really the problem.

My last BSOD I managed to note the error:

Stop: 0x000000BE

When I did a Google search on this it says it is an error involving an attempted write to read only memory. Anybody have a clue what this means? I have somewhat of an idea, but not sure if this can be corrected in the BIOS.

Thanks again for the help.
 
Enigma422 said:
Okay, I tried it with one hard drive at a time and with both hard drives I get a BSOD whenever I install Windows. One thing I noticed though is that whenever I unplug my Baybus about 60% of the time I am able to sucessfully install Windows, but the installation is unstable. However, when I have my Baybus plugged in I can't get past the installation no matter how many times I try. This is making me suspect the PSU is really the problem.

My last BSOD I managed to note the error:

Stop: 0x000000BE

When I did a Google search on this it says it is an error involving an attempted write to read only memory. Anybody have a clue what this means? I have somewhat of an idea, but not sure if this can be corrected in the BIOS.

Thanks again for the help.

That does sound like a psu issue, if youve reset bios have you put your ram/chipset voltages back up? Lanparty nf4s are notorious about power issues, so it could be something really tiny. Do you have another decent psu you can try?
 
I have my Fortron BlueStorm that's in my file server. I was thinking of trying this, but I need an adapter for my second graphics card. I am running MemTest and will leave it on overnight to make sure that it isn't my memory, but I don't suspect my memory that much since before these problems occured I was running a series of Memtests to find out what my max summer OC would be and at default speed and loose timings Memtest passed 8 hours as expected.

Tomorrow I will try to reset my BIOS, maybe even try flashing another BIOS to see if that does anything.
 
You dont still have the gpu that got water on it plugged in do you? Try pulling one out, if it works theres your problem.
 
My brother was having problems installing windows on his new A64 rig. I swapped RAM, a new brand completely, and that fixed the problem. A guy in another post has reboots and I told him the same thing, swap in new RAM, just borrow it from someone, that is one of the easiest things to check, and then atleast you can eliminate it as a suspect. From what I know RAM often causes random reboots. Especially problems with files being copied during installation.

Oh yeah and I used to have OCZ RAM, when I setup my computer it would give me random reboots, then I exchanged DIMMs, worked fine, but it would cause lockups in Max Payne 2.
 
Herulach said:
You dont still have the gpu that got water on it plugged in do you? Try pulling one out, if it works theres your problem.

Actually it was my sound card that got water on it. The leak was on the bottom graphics card above the sound card.

jubs said:
My brother was having problems installing windows on his new A64 rig. I swapped RAM, a new brand completely, and that fixed the problem. A guy in another post has reboots and I told him the same thing, swap in new RAM, just borrow it from someone, that is one of the easiest things to check, and then atleast you can eliminate it as a suspect. From what I know RAM often causes random reboots. Especially problems with files being copied during installation.

Oh yeah and I used to have OCZ RAM, when I setup my computer it would give me random reboots, then I exchanged DIMMs, worked fine, but it would cause lockups in Max Payne 2.

After running memtest overnight I don't think its the memory, but I'll give it a try. Anybody know how well Kingston HyperX memory plays with a DFI nF4 board. I know these boards are pretty picky with the memory you use. That's why I went with G.Skill TCCDs in the first place.
 
Im thinking it could be a micro fracture somewhere that just got worse with use. Try to swap out as many components as you can and then go from there. But this could be a costly problem if more than one component is hosed.
 
If you booted memtest, dosen't that have to mean the mobo/proc/memory/video has to be functioning to some degree? Toss a Linux Live CD into that slot and see what happens.
 
Okay, it's not the memory, I am 95% sure of that since I was able to run memtest86 for 12 hours without error, and this is in a very hot room. I pulled out the PSU and am going to clear the CMOS and try once more.

Does anybody think if I flash to a different BIOS, say the 510, will fix my problems. Right now I am running the offical 310 BIOS from DFI's website.
 
Update:

I just cleared my CMOS and pulled out the PSU and I am still having problems installing Windows XP. I also noticed that the clicking noise was not coming from my PSU but from the hard drives. Right before my computer BSODs I hear "click-click" right before I get the BSOD. The funny thing is that WDs Diagnostics utilities find nothing wrong with the the HDs when running a quick and full media scan. I even zeroed both drives. Could my cables be behind this? I remeber hearing that the cables that came with the DFI boards weren't that good.

I think I will try plugging my drives in the SiI3114 controller next.
 
Update 2:

Well I looked around several forums and found somebody at DFI-Street who had to set his timings to 2T in order to get his system stable. Well I did that and I am finally able to get my system to work, but I can no longer use 1T timings for my system.

My question now is why would all of a sudden I not be able to use 1T timings when it was running fine at this setting for two months? I can't even use 1T at default speed .
 
Back
Top