New computer reboots randomly, BSODs on boot...

[stultus]

Building a new system based on the MSI mATX nforce2 board, 2500+, 2x256 Corsair valueram PC3200.

The problem: system reboots randomly or crashes on loading windows. Originally started crashing when copying large files over network off a fresh windows install.

Now, gives a blue screen when loading windows. Flashes up VERY briefly, then the computer reboots. What I can read has "unable to write" "missing or corrupt" etc. Can't really read it as it's gone in a flash.

What I've tried:
prime95 (back when I could get in to windows) - error after 5 min
1 stick of ram in each slot - still crashes
full format of HD - HD is fine

What I think the problem may be:
motherboard isn't on standoffs, because this case has "preformed standoffs" directly on the removable motherboard tray.
bad ram somewhere

I haven't run memtest86 yet, but it's on my list.

Anyone have any other ideas? Could ground be causing intermittent problems?

PSU is a Antec 380W, so I've got plenty o' juice.

 

[PCHPlayer]

Can you boot into safe mode? Hold down F8 right after POST completes.

 

[stultus]

Will also reboot when loading safe mode. So, I'm thinking it's hardware (ram or motherboard).

 

[Pothead]

turn off the reboot so you can see the error.

under system properties, advanced, start up and recovery

 

[stultus]

Ah, but I can't get to windows.

 

[sandorski]

Double check all your BIOS settings and check for a BIOS update.

 

[blodhi74]

had a similar issue with gigabyte N7400PRO, barton 2500 with 512 pc2700 ram ....after a full format the windows would not load and reboot as soon as I saw the windows logo .... after a long night on trouble shooting the culprit was front USB panal ....once removed every thing worked like a charm

 

[stultus]

I have flashed the BIOS - there is no change.

I am able to *install* windows just fine. On bootup, windows informs me that it's just saved the machine from a very critical error. After installation, I changed the system so it would not reboot on error. I tried playing the "welcome to windows" flash animation, but the program crashed. Very soon after (like, 15 seconds), I BSOD'd with a IRQL_NOT_LESS_THAN_OR_EQUAL error.

Ever since then I've been unable to load windows, either normally or in safe mode. (In safe mode, the system hangs when loading "mup.sys").

I'm running memtest86 overnight on the box. If nobody else has any ideas, I'll RMA it tomorrow.

 

[stultus]

Extra things I've tried: Booted it with an extra video card (not the integrated), tried booting with motherboard outside of case, flashed the BIOS to the new version, used only one dimm, turned off everything in the BIOS. Always dies on loading windows. And yes, I want to run windows

 

[sandorski]

Try upping the voltage of CPU, ram, AGP, or other adjustable voltage setting. Search the AT database, the IRQ Less Than error is a common error.

 

[stultus]

Being a mATX board, it has fewer voltage settigns. I did increase the "vdram" a bit, no change.

 

[chocoruacal]

Originally posted by: stultus

What I think the problem may be:
motherboard isn't on standoffs, because this case has "preformed standoffs" directly on the removable motherboard tray..

I HATE cases like that. Tip: put some electrical tape on the standoffs then screw into them. Better yet, setup the mobo on a piece of cardboard. People crack me up...you shouldn't need to raise voltages...the system should boot and install windows right out of the box. Chances of a bad CPU are slim. Chances of a bad mobo are pretty good. Chances of bad RAM is likely. If the RAM tests good, or Memtest won't run at ALL on either stick (testing separately) then you might want to last ditch effort try a another power supply before sending back the board.

 

[stultus]

I have run the motherbaord outside of the case, and it didn't make a difference, so I don't think it's a grounding issue any more. Windows does in fact install right out of the box without any tweaking.... it's just not stable IN windows, and afterwards it won't let you boot to windows. memtest had finished 4 passes before I left it today.

I may have another power supply to test with soon. When I was using the antec without the P4 power connector (I know, P4 12V connector on an athlon mobo!) there was no video, so I have to use a power supply that's not terribly old.

 

[xenocyd3]

try using different ram

 

[sandorski]

Originally posted by: chocoruacal

Originally posted by: stultus

What I think the problem may be:
motherboard isn't on standoffs, because this case has "preformed standoffs" directly on the removable motherboard tray..

I HATE cases like that. Tip: put some electrical tape on the standoffs then screw into them. Better yet, setup the mobo on a piece of cardboard. People crack me up...you shouldn't need to raise voltages...the system should boot and install windows right out of the box. Chances of a bad CPU are slim. Chances of a bad mobo are pretty good. Chances of bad RAM is likely. If the RAM tests good, or Memtest won't run at ALL on either stick (testing separately) then you might want to last ditch effort try a another power supply before sending back the board.

No, you shouldn't "need to" up voltage, but sometimes that fixes certain problems.

 

[een]

That's ram my man, had the same problem, before rma-ing get a stick of ram from your mates and stick one in. I had exactly the same problem, it turns out to be bad ram for BOTH sticks

 

[stultus]

Wouldn't memtest tell me if the ram were bad?

 

[PCHPlayer]

A few things to try:
1. Check IDE cables. I once had a problem with BSOD's that was due to a loose IDE cable. Try a different cable.
2. Disable all integrated peripherals (USB, serial, parallel) to see if you can get any further in windows.

 

[stultus]

I have previously tried both of those

 

[shimsham]

tried a different power supply?

 

[stultus]

Not yet, I need a PSU with a 12V connector (I believe). I'll try tomorrow. However, I would think if the PSU were flaky then I'd have problems during the windows install. Nevertheless, I'll give it a shot.

 

[sandorski]

Oh, you don't have the 4pin 12v plugged in? That would be your problem right there, I'mm 99.44% sure.

 

[stultus]

No, I *do* have that plugged in. The problem is that I don't have any other PSUs at the moment that have that connector, so I can't try another supply.

 

[jmagg]

The ram may not be bad, but the mobo may not like it. Relax ram timings?
Is this a new harddrive? Possibly write zeros to the first few hundred sectors to wipe the mbr if not. Format leaves the mbr untouched.
Bad install disk?
Disable all onboard peripherals(lan?)
Bad mobo out of the box?


All outside shots but what the hell

 

[stultus]

I think it may just be this board not liking this ram. That's about all I have left, though I've never heard of nforce2 mobos not liking corsair before. I'll try relaxing the timings down further, though I'm not sure how much bios control over them I have with this board.

HD is new. Install disk is fine. I've already tried diabling *everything* in the bios.

It could be a bad mobo, but I wouldn't expect it to install windows fine.

I'm really scratching my head here. Please give me more longshots