Successfull OCs, but Windows acts up

[prochobo]

First off, I'm OCing a 3000+ winnie on an MSI K8N Neo2 Plat w 2x512 Patriot XBL PC3200. Divider is set at 3/4, HT is 3x and I was pushing 275 FSB. Voltage was 1.550 + 5% also.

After going past 275, Windows didn't recognize the processor. It shows up in device manager, but no properties for it. Under the Computer information, the CPU doesn't show up. CPU-z reports just fine.

It also takes FOREVER to startup once it gets past the boot screen (stuck on "Starting windows services" or something like that. ). The task bar is shot also. Every window I open doesn't appear on the bar.

Decreasing from 280 to 275 doesn't fix the problem. Even if I go all the way down to 260, it still fvcks up.

Is this normal or what?

 

[ocforums]

Set it back to stock and see how it reacts..

 

[theMan]

are you running prime95 or memtest?

 

[the cobbler]

Originally posted by: prochobo
First off, I'm OCing a 3000+ winnie on an MSI K8N Neo2 Plat w 2x512 Patriot XBL PC3200. Divider is set at 3/4, HT is 3x and I was pushing 275 FSB. Voltage was 1.550 + 5% also.

After going past 275, Windows didn't recognize the processor. It shows up in device manager, but no properties for it. Under the Computer information, the CPU doesn't show up. CPU-z reports just fine.

It also takes FOREVER to startup once it gets past the boot screen (stuck on "Starting windows services" or something like that. ). The task bar is shot also. Every window I open doesn't appear on the bar.

Decreasing from 280 to 275 doesn't fix the problem. Even if I go all the way down to 260, it still fvcks up.

Is this normal or what?

did you set PCI lock?

if not, you could fry Windows, maybe that's what's happening

 

[prochobo]

Yes, I did set PCI lock. I didn't run memtest or prime, but I have run SuperPi 32M and everything's fine. I was just wondering if anyone else had that issue. Right now, I'm restoring from an image so I'll see how that goes.

I doubt it's my memory since it was running 225mhz at the 275 FSB. It's done 250 on the same timings. Temps are not an issue either. 40c idle 60c load

UPDATE
Restore is now finished. I'm doing 275FSB now and everything's fine. Damn Windows. . .

 

[nealh]

you have not tested this chip properly to see if it is OCing stable at 9*275=2475

while it should run this fast OC is always YMMV...you need first to run memtest to make sure ram is ok..then run prime95 for at 4hrs to test cpu..(large,small ffts)


also on the Neo2 Plat are you using SATA? if so make sure you are on sata 3/4 ..sata 1/2 is not locked

 

[prochobo]

Originally posted by: nealh
you have not tested this chip properly to see if it is OCing stable at 9*275=2475

while it should run this fast OC is always YMMV...you need first to run memtest to make sure ram is ok..then run prime95 for at 4hrs to test cpu..(large,small ffts)


also on the Neo2 Plat are you using SATA? if so make sure you are on sata 3/4 ..sata 1/2 is not locked

Isn't Superpi enough? I guess not. I know for a fact that my RAM is OK since I've been running it for 6 months at 250 FSB. I am using SATA 3/4. I guess I've reached the limit then because Windows doesn't even see the processor there after a high OC! GRRR. . I could go so much higher. . .

 

[nealh]

if you have not run memtest on the memory..I am sorry but you can not guarantee that it is memroy free

I would strongly recommend running memtest for at 5 passes(about 2hrs) as a minimum and prime95 for at least 4hrs

I had ram that seem stable overclocked in windows but when i ram memtest it was erroring out after a hour..so it would lead to error and problems..a bump in vdimm or vcore can help stability

SuperPi is not a real good way to stress the system for errors IMHO...test is too short