new systen crashing on startup!

[waggy]

Ok i built my new system. installed xp and updated. it was running fine.

but then it would crash and reboot itself when you start to do anything in XP. it usually does it 3-5 times then its fine and works great until you shut it off again.

not sure what the error is. it happens to fast! i would see the blue screen then it reboots.
anyway the system specs are below.



segate Barracuda ES ST3400620NS 400GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM
Item #: N82E16822148157
1 Intel Core 2 Duo E6600 Conroe 2.4GHz LGA 775 Processor Model BX80557E6600 - Retail
Item #: N82E16819115003
1 SABRENT SBT-SP6C 5.1 Channels PCI Interface Sound Card - Retail
1 CORSAIR CMPSU-620HX ATX12V v2.2 and EPS12V 2.91 620W Power Supply - Retail
Item #: N82E16817139002

1 MSI NX8800GTS-T2D640E-HD OC GeForce 8800GTS 640MB GDDR3 PCI Express x16 HDCP Video Card - Retail
Item #: N82E16814127280

1 CORSAIR XMS2 DOMINATOR 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model TWIN2X2048-6400C4D - Retail
Item #: N82E16820145168

1 ZALMAN CNPS9500 LED 92mm 2 Ball Cooling Fan with Heatsink - Retail
Item #: N82E16835118223

1 ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard - Retail
Item #: N82E16813131032

Item(s) shipped from TN Tracking Number:
1 Antec Nine Hundred Black Steel ATX Mid Tower Computer Case - Retail
Item #: N82E16811129021

1 SAMSUNG 720N Black 17" 8ms LCD Monitor - Retail
Item #: N82E16824001084

 

[amdskip]

Do this:

When you are running Windows XP, you may have noticed that every so often (rarely) that Windows reboots without you asking it to. This tends to be caused by a Blue Screen error. If you want to see what this error is, you will have to check the error log list because Windows reboots too quickly for you to read what happened. Well with this tip you can disable the Auto-Reboot so you can finally read, and see the blue screen error.

1. Go to Start -> Control Panel -> System
2. Go to Advanced
3. Under the Startup and Recovery section, click Settings...
4. Under System Failure un-check "Automatically restart"

 

[waggy]

ohh thanks.

this is annoying. usually i have extra parts to swap out to find out what is wrong. heh i have nothing (well HDD and v-card) to swap out.

 

[waggy]

hehever since i have changed that setting it has not crashed. bah

 

[BucNews]

When you are having crashes it also pays to check the event log.

 

[GuitarDaddy]

I'm going to wager a guess that it's a device driver causing the problem. Check to make sure you have the latest drivers for sound card, GPU, NIC, wireless, etc....

 

[waggy]

hmm updated drivers to be safe. went to play COD2 and it crashed.

then took like 15 minutes for the computer to restart.

 

[panipoori]

Overheating, bad memory? Maybe the memory speed is set to high. I built a system once where the motherboard would set the memory speed above what it was rated for causing alot of reboots.

 

[waggy]

Originally posted by: panipoori
Overheating, bad memory? Maybe the memory speed is set to high. I built a system once where the motherboard would set the memory speed above what it was rated for causing alot of reboots.

thats what i thought at first. that maybe the cpu or mem was set ot high *(no i did not overclock at all).

checked it out and everything seems fine. Also it will be fine for hours even playing games such as oblivion and goofing off on ATOT.

 

[waggy]

ok had a string of blue screens.

first was "IRQ_NOT_less_OR_EQUAL" i rebooted.

during boot process or right after (not sure was not watching) i get PFN_LIST_CURRUPT and i rebooted.

Page_fault something something ...i spilled water on the paper heh

 

[Roguestar]

I got a whole bunch of those too. IRQ_NOT_LESS_OR_EQUAL and PFN_LIST_CORRUPT and BAD_SOMETHING_SOMETHING and the page fault one. I'm having major diffs with my memory and have just contacted Crucial to get an RMA number. Run memtes86+ from a CD and see what the results are like.
www.memtest.org

 

[waggy]

Originally posted by: Roguestar
I got a whole bunch of those too. IRQ_NOT_LESS_OR_EQUAL and PFN_LIST_CORRUPT and BAD_SOMETHING_SOMETHING and the page fault one. I'm having major diffs with my memory and have just contacted Crucial to get an RMA number. Run memtes86+ from a CD and see what the results are like.
www.memtest.org

just did that. it wouldnt finish it had a bunch of errors. i think we found the problem.

damnit. not having mem is goign to suck heh.

 

[waggy]

grr no other mem ot put in it. had to go back to my old. 3200+ amd

 

[waggy]

and wouldnt you know. newegg does not cross-ship. well they will let you buy some then refund you when the old ones come in.

 

[GuitarDaddy]

Your memory is spec'd to run at 2.1v, have you set it to 2.1v manually in bios?
All P965 boards set default voltage at 1.8v, if you haven't manually set it to 2.1v and are just leaving the ddrvolts at auto that is definately your problem

 

[Cheezeit]

Originally posted by: GuitarDaddy
Your memory is spec'd to run at 2.1v, have you set it to 2.1v manually in bios?
All P965 boards set default voltage at 1.8v, if you haven't manually set it to 2.1v and are just leaving the ddrvolts at auto that is definately your problem

Thats a prime suggestion. If the memory is running higher than usual specs at 1.8v, it won't be stable. Also try memtest on one stick at a time to see if you can nail out one stick. The chances of 2 bad sticks are very slim.

 

[waggy]

Originally posted by: Cheezeit

Originally posted by: GuitarDaddy
Your memory is spec'd to run at 2.1v, have you set it to 2.1v manually in bios?
All P965 boards set default voltage at 1.8v, if you haven't manually set it to 2.1v and are just leaving the ddrvolts at auto that is definately your problem

Thats a prime suggestion. If the memory is running higher than usual specs at 1.8v, it won't be stable. Also try memtest on one stick at a time to see if you can nail out one stick. The chances of 2 bad sticks are very slim.

that wouldnt matter. even with 1 bad stick i would have to send in both.


yeah i found out fast that the board does not set the mem at the correct setting. have to do that manuelly.

 

[GuitarDaddy]

Looking at the newegg reviews on that ram your not alone But it is a very popular ram so you would expect some bad sticks getting out. Bummer that it happened to be you

 

[Puffnstuff]

Bad memory sucks, I'm going through it right now with corsair with a set of matched xms sticks. I had all kinds of problems with irq, memory management, machine stops and the like. Software that would move to occupy that bad space would suddenly stop and crash. It was a real pita until I ran memtest and saw all of the bad addresses. I had to explain that to the corsair rep plus I tried it on another machine and got the same errors.

 

[Roguestar]

Well for what it's worth I just sent off my bad RAM today too. RMA'd my Crucial 10th Anniversary sticks . Hopefully they'll give me some Crucial Ballistix DDR2-800 in exchange. I'll not have a PC at home at all for almost a week now!

 

[MrsWaggy]

(this is waggy can't get my computer running long enough to post)



got some kinston ram. ran memtest (first thing i did) and its fine! woot!

but got a error on startup (not sure wha it is)

now getting NV4_dis.DLL. getting new drivers hopefully that wll clear it up. but have a feeling something else is bad also.

 

[GuitarDaddy]

Your bad ram probably corrupted your window install. I would pop in the windows disk and do a repair install(replaces windows files but leaves your data files intact) and see if that fixes it. If that doesn't fix it you may have to do a complete fresh install

 

[MrsWaggy]

Originally posted by: GuitarDaddy
Your bad ram probably corrupted your window install. I would pop in the windows disk and do a repair install(replaces windows files but leaves your data files intact) and see if that fixes it. If that doesn't fix it you may have to do a complete fresh install

can't it keeps locking up. ten the bios seems messed up (seen some thers had the same problem in reviews).

i got XP reinstalled. but i had the NV4 error. went to redo the driver for the v-card. but it locks after 4 minutes of use. no error given at all. it just locks.

the cpu does not seem to be overheating. so now wonder if the board or v-car could be bad


oh also got th irq error once.



this is really ticking mne off. wish i had other parts to throw in and see what works. bah

 

[jondl]

Originally posted by: MrsWaggy

Originally posted by: GuitarDaddy
Your bad ram probably corrupted your window install. I would pop in the windows disk and do a repair install(replaces windows files but leaves your data files intact) and see if that fixes it. If that doesn't fix it you may have to do a complete fresh install

can't it keeps locking up. ten the bios seems messed up (seen some thers had the same problem in reviews).

i got XP reinstalled. but i had the NV4 error. went to redo the driver for the v-card. but it locks after 4 minutes of use. no error given at all. it just locks.

the cpu does not seem to be overheating. so now wonder if the board or v-car could be bad


oh also got th irq error once.



this is really ticking mne off. wish i had other parts to throw in and see what works. bah

Are you overclocking at all? Try clearing CMOS and manually setting the timings of your memory as well as the voltage. Take out anything that isn't required to install windows like extra HDs, drives, soundcards, etc.

// check your temps in bios to see if anyting is overheating. Your heatsink might not be seated properly. Check all your fans.

 

[MrsWaggy]

Originally posted by: jondl

Originally posted by: MrsWaggy

Originally posted by: GuitarDaddy
Your bad ram probably corrupted your window install. I would pop in the windows disk and do a repair install(replaces windows files but leaves your data files intact) and see if that fixes it. If that doesn't fix it you may have to do a complete fresh install

can't it keeps locking up. ten the bios seems messed up (seen some thers had the same problem in reviews).

i got XP reinstalled. but i had the NV4 error. went to redo the driver for the v-card. but it locks after 4 minutes of use. no error given at all. it just locks.

the cpu does not seem to be overheating. so now wonder if the board or v-car could be bad


oh also got th irq error once.



this is really ticking mne off. wish i had other parts to throw in and see what works. bah

Are you overclocking at all? Try clearing CMOS and manually setting the timings of your memory as well as the voltage. Take out anything that isn't required to install windows like extra HDs, drives, soundcards, etc.

// check your temps in bios to see if anyting is overheating. Your heatsink might not be seated properly. Check all your fans.

no overclcking at all. cleared the cmos a few times. also only have a drive v-card and DVD burner in. all fans are fine.