New computer can't do anything......

[farscape]

Darn, but if this doesn't sound really familiar. Come to think of it, I had a quite similar prob on a Shuttle board I was setting up for someone. Wouldn't load Wdoze for nothing until I went into Bios and reset it all for Default settings and disabled all of the on-board stuff - NIC, sound. Then all loaded nicely, and I was able to turn everything back on.

Just an idea - hope this helps.

Best memory timings I've found on an nforce board are 2.5,3,3,11

 

[kcbass]

I'll try that. 

 

[ScrapSilicon]

Originally posted by: kcbass
I checked the hard drive, and it is not a WD. It is a white label brand from justdeals.com. It says platinum on it, so I did not remove the jumper. 

?

 

[kcbass]

I tried to run memtest on my memory last night to make sure it was stable (just for fun, really...) and mine stalled out on test 11, but my memory's been working for me for years now, so I don't quite know what to make of that 

 

[kcbass]

well farscape....no such luck. I shut down everything onboard except video (i'm using that), and it still freezes on getting list of files. I tried leaving the disk as-is, I tried a quick format, and I tried a full format, but they all froze in the same spot. I'm gonna try a memory swap later today, but for now do you have any other suggestions?  

 

[kcbass]

bump

 

[kcbass]

Well, I switched out a memory stick from my computer that i've been using for over a year now, and it worked pretty well, but it froze about 80% through transferring files the first time, and the second time it froze after tansferring 100% of the files, but it didn't go on to the next step. So, does that tell me that it's a bad power supply, or is there anything else I should try? 

 

[kcbass]

bump 

 

[Paperlantern]

From Microsoft:

This issue may occur if a system thread generates an exception that the error handler does not catch. This may occur if one or more of the following conditions exist:

* If this issue occurs after the first restart during Windows Setup, or after Setup is finished, the computer may not have sufficient hard disk space to run Windows.
* If this issue occurs after the first restart during Windows Setup, or after Setup is complete, the computer BIOS may be incompatible with Windows.
* Incompatible video adapter drivers.
* Damaged RAM.
* A damaged device driver or system service.
* If the issue is associated with the Win32k.sys file, it may be caused by a third-party remote control program.

original documentation here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;330182

not an EXACT match of problem, but the circumstances are almost never described to a T, but close

 

[kcbass]

hmm....that's good info, but like anything from microsoft, it doesn't tell me much. If it's bad ram that would make sense for the first stick, but the second runs fine in my machine. It's got plenty of disk space, and the latest BIOS. I haven't had a chance to load any drivers yet, and it's not associated with the Win32k.sys file, it's ntfs.sys most of the time. Well, the power supply should arrive on tues, and if it doesn't work with the ram, i've gotten clearance to RMA it also, but until then i'm gonna keep trying. Any more advice? 

 

[xbassman]

Here is another thing you can try....

I am using the same mobo as you.
I had a lot of stability problems initially. (I can't remember if it was overclock related completely though)

Your board tends to undervolt a little bit. You should try bumping up your chipset voltage one step at a time. When overclocking I had to bump this value to the max of 1.7v to become stable at all using onboard graphics.

When you are running memtest86 save yourself a little time and select test #5. If you can pass that one 3 or 4 times through, run the whole battery of tests.

You can burn a memtest cd. Google "memtest86 ISO"

 

[kcbass]

I'll try that voltage thing. Why test number 5 specifically? 

 

[xbassman]

Originally posted by: kcbass
I'll try that voltage thing. Why test number 5 specifically?

Test 5 is normally the first one to generate errors....

 

[kcbass]

Well, I ran test number 5 five times with no problem, so I set the tests to all and went to sleep. This morning it had frozen 100% through test 12 and 99% through total pass with zero errors and zero pass. 

 

[kcbass]

I upped the voltage to the chipset to 1.7, but it was already at 1.6 before I changed it, so if that doesn't work, should I try the lower levelse too? 

 

[kcbass]

The system was even more unstable at 1.7v, so I went back to 1.6 

 

[xbassman]

Just for grins....

Boot that thing up into bios...
go to pc health status and let it warm up for about 15 minutes.

What temps and volts are you reading?

Are you using the latest bios?
Early bioses incorrectly recognized some processors. (Thought mine was a 3200+ instead of 2500+)

 

[kcbass]

I updated the BIOS 2 days ago, so it better be the latest. I just turned it on, so I'll let you know in a little while 

 

[kcbass]

ok...

system temp: 27c
cpu temp 48c
cpufan 2265rpm
cpu core volt 1.64
vcc volt (+2.5v) 2.64v
i/o volt (+3.3v) 3.24v
+5v 5.08v
+12v 11.97v
-12v -12.11v
-5v -5.14v
3.3v dual volt 3.60v
standby volt (+5v) 4.92v

I hope that tells you something 

 

[kcbass]

computer's again consistently freezing on creating list of files to be copied. 

 

[kcbass]

So is this a power supply problem, because that's the only thing in the case I haven't switched out with a working part... 

 

[xbassman]

Actually those readings look fine.....
Could be that your power supply isn't giving your board a stable enough voltage. I have used power supplies that would vary up to .2 volts.

Your temps are a little high for idle, but you could bump the voltage up to 1.7 and see if your install will go.
I am leaning toward the power supply being the problem.

If it doesn't go with 1.7v I would wait until you get the new power supply.

If you get windows installed with a vcore bump watch your temps! That 48c idle could jump quite a bit higher under load. Mine jumps up about 9-10C from idle to 100% load with a Thermalright HS.

 

[kcbass]

Install didn't go at 1.7, but the temps I gave you were approximations, because they were jumping all over the place as I was typing them, and they were varying by a lot more than .2. I hope that's the problem, because if it's not I don't know what else I'll be able to do 

 

[xbassman]

You said your temps were varying alot...

Was your vcore varying alot? How much?

I remember running Prime95 and I had motherboard monitor running also.
The power supply I was using would vary giving a low voltage to the processor and Prime would fail as a result.

If it is ocassionally reading something like 1.45v Just wait for your power supply.

 

[kcbass]

You're right, I did say temps. What I meant to say was voltages.