My system:

CPU: AMD FX-55
Mobo: Fatal1ty AN8 SLi
Video: 2 x BFG GeForce 6800GT OC (SLi)
Memory: 4 x 512mb - OCZ EL DDR PC-3200 Platinum Revision 2 (OCZ4001024ELDCPER2-K)
Power: OCZ Powerstream 600W
HD: Maxtor Raptor - 36gb - 10,000RPM (SATA)- Windows install drive
Segate - 200gb - 7,200RPM (IDE) - Storage drive (currently disconnected)
Rom: Pioneer DVD-RW DVR-109
TSSTcorp DVD-ROM TS-H352A
Operating System: Windows XP Professional SP2
OTHERS: Mouse (ps/2)
Keyboard ( ps/2)
Printer x 2 (USB)
Scanner (USB)
uguru panel


Drivers:
Display: Nvidia 77.77
nForce4 Chipset Driver for Fatal1ty AN8 SLi - 8/16
Bios Verison 17



Well, I put the listed system together a couple weeks ago and Ive been having serious problems with it since. I resolved all/most of my problems last week, but they resurfaced again 6 days later (I connected my 2nd hard drive and they seemed to have started again after that - since then however, ive disconnected the drive)

Currently, I'm getting random freezing both when playing games and when just browsing the web. I've run memory tests, but no errors are reported.

Before, a majority of my crashing/BSOD problems were fixed by changing the comand rate from 1T to 2T.

Anyone know of any secret resolutions for my woes?

Attached Thumbnails

 

Umm out of curiosity, what are your problems exactly?
oh and if you haven't been welcomed before, welcome to pimprig. I'm sure Thrasher will be around to give you a proper welcome :-p

Hi, thanks for the welcome...

Well, to get into depth....

The following is a list of problems I had when I first put the computer together:

1) After installed the most recent board drivers, upon restart, the computer went to a blue screen of death reporting 0x000000FC. Since the screen disappears so quickly, I couldn't make out everything it said, but I also remember seeing the phrase: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY.

After hours of trying to get the damn thing just to BOOT, my brother and I finally stubbled upon this next link from microsoft:

http://support.microsoft.com/defaul...kb;en-us;878474

With that in mind, my brother (the networking expert) figured that the Nvidia Forceware Networking Manager was conflicting with Microsoft's software. Eventually (by luck it seems) we finally got the thing to boot into safe mode long enough for us to uninstall the software. After that, it ran fine....so it seemed.

2) After we resolved the previously mentioned problem, a new problem arose. The system will randomly freeze/restart (after about a half hour of operation - in fact it both frooze AND restarted on two seperate occassions while writting this). So far, I've tried uping the memory voltage to 2.8, but it has had no effect.

3) This is the strangest problem...The computer won't shut down. When I instruct windows to shut down, the computer will restart. So, everytime I want to shut the computer down, I have to hold down the power button.


I resolved the first problem by doing what I described above. I resolved the second problem (I thought) by changing my memory setting (command rate) from 1T to 2T (that's what people on the Abit forums suggested). After doing that, the freezing stopped and I experience no more BSOD. I resolved the third problem by unplugging my firewire CF card reader.

After about a week of stable computing, I felt it was safe to plug in my second hard drive (IDE). Once I did that, the crashing came back.

I unplugged the hard drive, cleared CMOS, installed the newest BIOS (from BIOS 16 to BIOS 17), ran stock memory settings, and the suggested 2T setting. All changes have had no effect.

The sytem with randomly freeze, either in game or when I'm just browsing the web. In fact, I JUST received a blue screen of death when I tried playing BF2. I checked my event log and it reported the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082805-01.dmp.



I looked further, and that isn't the only 'Save Dump' reported.


On the previous day (I had gotten a BSOD then too), it reported:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbfa62218, 0xb3598a74, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082705-01.dmp.


I'm a complete n00b when it comes to memory timings, so I'm a lose of what to do....

i would get an hdd diagnostic program (dos based)

you can find them at the manufatures webpage....


when you plug in your hdd ... is it ide or sata? is it cable select or slave/master?channel ide 0 or ide 1?

but more then likely its your power supply.... what is it specs??

IDE


Cable Select

Power Supply: OCZ Powerstream 600W

Technical specs:

http://www.ocztechnology.com/products/PSUSpec.pdf

Dang, that sucks... All that awesome hardware and it doesn't want to play nice...

Is any of the hardware newer than the rest, i.e.: you scavenged the HDD and PSU from a previous build, and bought all the rest new? If that was the case, I would be looking at the newest piece(s) as likely culprits.

I'm guessing you got it all at once, though, and it was straight from the wrapper/box to the case...

Here's something that just popped in my mind: just for poopsicles and giggles, pull everything out of the case and set it up on an anti-ESD mat or non-conductive counter-top, etc. See if you can get it to duplicate the BSODs and crashes. If you can, nevermind that, I would be thinking case/mobo grounding there.

If at all possible, swap out components with other known-to-work fine machines, and see what pops...

That's about all that comes to mind right now... Good luck, and yes, definitely welcome to PR.

Quote: Originally Posted by spzero414 Hi, thanks for the welcome.......

to PimpRig............


Please check out the Sweeet Pimp Links..

• http://team.pcapex.com/
• http://gallery.pcapex.com/
• http://articles.pcapex.com/
• http://forums.uberw00t.com/
• http://www.stanford.edu/group/pandegroup/folding/
• BF2 Game Sever for Pimps

Sorry for all your problems with your Hardware.....More pimps will be coming soon to help you out

This may sound a bit tedious but, in order to find the hardware issue. I would take it down to bare minimum. Only attach what is need to boot and run windows.

Set your bios back up to default values. Run your system with only the cpu, ram, video, 1 hard drive, and 1 cdrom. Install a fresh new copy of windows. Update your windows service packs and any sound, video, chipset, and network drivers. Next i would torture test it with BF2 and see if it bsods. Now if it bsods there are less pieces of hardware to diagnose but, If it runs great with no problems. Add another piece of hardware and run it again to see if it bsods. Keep adding hardware till the problem arises. This should hopefully narrow down the problem to the faulty hardware.

It also wouldnt hurt to check out your event viewer to see what errors are showing up in there. It could give you a clue as to the cause of the problem.

I hope this helps.....

Thanks for the help thus far.

I checked my event logger and it reports a 'Save Dump' each time it BSOD:


The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082805-01.dmp.




The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbfa62218, 0xb3598a74, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082705-01.dmp.


The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbfa62218, 0xb2eaca74, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082505-01.dmp.


The computer has rebooted from a bugcheck. The bugcheck was: 0x000000fc (0xb8a208c4, 0x2c8c4163, 0xb8a20800, 0x00000001). A dump was saved in: C:\WINDOWS\Minidump\Mini123104-01.dmp.



Those are all the BSOD since I tried my second hard drive. Other than these, the system likes to just freezes.



First thing I'm going to try is running just two sticks of memory. I was able to resolve my problems before by removing two sticks of memory...why oh why do boards hate 4 sticks of mem

Wow...I just turned the computer on to do some work (haven't removed the memory yet...was going to after I finished what I needed to do), and sure enough, I got another BSOD. However, this time it gave me the message:

IRQL_NOT_LESS_OR_EQUAL

with parameters:

0x0000000A

I checked microsoft's website and it said:

http://support.microsoft.com/defaul...kb;en-us;130802


Even logger still logged it as a 'Save Dump.' So, memory issues? Do I need to adjust the timings from Auto? If so, anyone have an idea of what to changed (Im a complete n00b when it comes to memory timings....I have no idea what most of the settings do). Or, does the board just not like having 4 sticks (i have heard that is an issue with a lot of boards) and should i just trade these in for 2 sticks of 1gb?

I would try turning the RAM timings to something like 2.5-3-7-3 or 3-3-8-3, just to see if it will stop the crashes. You can adjust these in the BIOS menus. From what I understand, the earlier revision cores (in your case the Clawhammer instead of the Rev E. San Diego) has a slighty buggy memory controller, and doesn't like working with all 4 slots filled. If you want everything to run at full speed, you may need to trade it in for the San Diego core FX-55.

just for the heck of it pull all but one stick of memory and try setting your HT multiplier to 4.

Well, I pulled two sticks of RAM out and ran BF2 with no problem for about an hour. I then ran a memory test up to 2000% coverage with no errors...

That was with RAM voltage set to 2.8v and Command Rate set to 2T still...

Quote: Originally Posted by spzero414 Well, I pulled two sticks of RAM out and ran BF2 with no problem for about an hour. I then ran a memory test up to 2000% coverage with no errors... That was with RAM voltage set to 2.8v and Command Rate set to 2T still...

Try swapping the RAM at this point. If it doesn't crash, then the all of the RAM is good; the proc just doesn't want to play.

So, I've tested 3 sticks of the RAM (individually) so far and this is what I've got:

1st stick:

12 hours of memtest w/ no errors

2nd stick

9 hours memtest with no errors


3rd stick

This is where it gets confusing. With the 3rd stick, the computer wouldnt post. I would get a black screen in ANY slot I put the memory in. I must have cleared CMOS about 5 times with no success. Finally, I put the 2nd stick in along with the 3rd stick (in slots 3,4) and the thing posted. It went to memtest and ran for 8 hours w/o error.


I'll do the last stick tonight, but that 3rd stick confuses me. Why would it not work by itself, but then report no errors when it was running with stick 2?