Win32k.sys Error When Going Past 2.7ghz.

N

Nobi125

[H]ard|Gawd
Joined
Jun 7, 2005
Messages
2,004
Now that I have new ram and better cooling, I'm trying to OC my Opty 170 further.

I'm giving it 1.486V in the Bios, which reads 1.5V in Windows.

Ram divider is at 333 and timings are stock, so it should be fine since I'm below stock speeds (note: the ram has ran fine at stock speeds).

HT Multi is at 3x.

I got up to 2.7GHZ and started to run into trouble.

I get a blue screen (with memory dump) over an error about a Page Fault In Nonpaged Area. The file with the problem is Win32k.sys.

I looked around online and some people are saying it's a ram related problem, but my ram runs fine 1:1 with my CPU at 260FSB. So with a 5:6 divider it should be fine at 270fsb.

When the system reboots, Windows Error Reporting tells me I had a Problem Caused by Device Driver.

I don't think that's the problem since I don't have this issue at 2.6GHZ.

Any idea on what's up?
 
Nobi125 said:
Ram divider is at 333 and timings are stock, so it should be fine since I'm below stock speeds...

I got up to 2.7GHZ and started to run into trouble...
.

I looked around online and some people are saying it's a ram related problem, but my ram runs fine 1:1 with my CPU at 260FSB. So with a 5:6 divider it should be fine at 270fsb.
Click to expand...

Clearly, something is wrong with your settings if you're getting errors like this.

Never make any assumptions when it comes to troubleshooting an overclock. Your descriptions of the problem suggest that, more than likely, the problem is RAM-related. Impose a bigger divider, or loosen up your timings. Saying "it should be fine since (you're) below stock speeds" implies an unwillingness to concede that your settings/equipment are holding back your attempt to reach higher CPU speeds.

If clocking down or loosening up your RAM and its timings doesn't work, then that may mean the problem is caused by something else. However, given what you've said previously, it's almost a dead certainty that it is RAM-related.

Hope that helps!
 
txtmstrjoe said:
Clearly, something is wrong with your settings if you're getting errors like this.

Never make any assumptions when it comes to troubleshooting an overclock. Your descriptions of the problem suggest that, more than likely, the problem is RAM-related. Impose a bigger divider, or loosen up your timings. Saying "it should be fine since (you're) below stock speeds" implies an unwillingness to concede that your settings/equipment are holding back your attempt to reach higher CPU speeds.

If clocking down or loosening up your RAM and its timings doesn't work, then that may mean the problem is caused by something else. However, given what you've said previously, it's almost a dead certainty that it is RAM-related.

Hope that helps!
Click to expand...

I must not have written it as clearly as I thought it, lemme try again.

The computer is stable with the CPU at 2.6ghz (260FSB) and the ram at 1:1

The reason i don't think it's a ram problem is because at 2.7ghz (270fsb) with the divider set to 333, the ram is running slower than it has proven to be capable of running stable at.

So under other conditions the ram has run faster and been stable.
 
Nobi125 said:
I must not have written it as clearly as I thought it, lemme try again.

The computer is stable with the CPU at 2.6ghz (260FSB) and the ram at 1:1

The reason i don't think it's a ram problem is because at 2.7ghz (270fsb) with the divider set to 333, the ram is running slower than it has proven to be capable of running stable at.

So under other conditions the ram has run faster and been stable.
Click to expand...

I've seen situations like this in the past where a certain board will run fine with one divider, and unstable with another.... The cause for this is almost always the clock is not in sync properly. Nothing you can do about it other then trying a different divider, or if your willing try a different board.
 
duby229 said:
I've seen situations like this in the past where a certain board will run fine with one divider, and unstable with another.... The cause for this is almost always the clock is not in sync properly. Nothing you can do about it other then trying a different divider, or if your willing try a different board.
Click to expand...

It's not worth it for me to pick up a new motherboard.

I'll mess around with different dividers later.

Thanks.
 
I've had a similar situation with my ram. It doesn't like the timings changed or to be underclocked. But it overclocks like crazy.....I just can't change the timings.
 
I had to drop my cpu multi to 9 so I could use a different divider to get my ram stable with the same cpu speed. Even though its the same exact speed. Probably related to the unseen timings the computer changes with different multi.
 
I messed around with different dividers, multipliers, and voltages for about an hour and still couldn't get it stable at 2.7ghz.

I guess my opty isn't that great of an overclocker.
 
So are you actually using a stability test to see what gives out and when?
Orthos for CPU stability
Memtest86 for memory
 
Nobi125 said:
I get a blue screen (with memory dump) over an error about a Page Fault In Nonpaged Area. The file with the problem is Win32k.sys.
Click to expand...

This still looks like a memory related problem to me. Run MemTest and see what it says about your ram settings.
 
Prime even with large FTTs isnt near as good as memtest86 at catching memory errors. Personally I just skip all the first tests and loop test 8. Test 8 is so brutal that settings that will get me into windows and let me game for hours will error out in under a minute sometimes.
 
Jakalwarrior said:
Prime even with large FTTs isnt near as good as memtest86 at catching memory errors. Personally I just skip all the first tests and loop test 8. Test 8 is so brutal that settings that will get me into windows and let me game for hours will error out in under a minute sometimes.
Click to expand...

Running memtest right now (posting from my laptop).

Cleared the first two passes of Test 8 just fine, it's about half way through Pass 3 right now.

How long do I need to let it run for?

I used the ram's stock settings for this test (250mhz, 3-3-3-8)
 
I should note that I had to do a repair install last week.

I think that may have something to do with the bluescreens.

Everything runs just fine when the CPU is at 2.6ghz though.
 
Your gonna want to let memtest run on whatever settings you want to use it at.... If your running OCd, then OC the memory and run the program.... What your interested in is seeing where and when your memory craps out. Then you can play with timings and voltages to see if you can get it stable.
 
duby229 said:
Your gonna want to let memtest run on whatever settings you want to use it at.... If your running OCd, then OC the memory and run the program.... What your interested in is seeing where and when your memory craps out. Then you can play with timings and voltages to see if you can get it stable.
Click to expand...

When I had my CPU at 2.7ghz, the ram was running at 225mhz, and it gets no errors in Memtest running at 250 with the same timings.

I played around with a bunch of dividers and multipliers and still had no luck.

I think it's just the CPU.
 
Do one pass while you are working the speed up, when you hit an error and have to back down though do about 3 passes each time while you hone in on the sweet spot. Then loop all tests next time you goto bed.
 
Jakalwarrior said:
Do one pass while you are working the speed up, when you hit an error and have to back down though do about 3 passes each time while you hone in on the sweet spot. Then loop all tests next time you goto bed.
Click to expand...

Could the bluescreens be related to a repair install?
 
Nobi125 said:
When I had my CPU at 2.7ghz, the ram was running at 225mhz, and it gets no errors in Memtest running at 250 with the same timings.

I played around with a bunch of dividers and multipliers and still had no luck.

I think it's just the CPU.
Click to expand...

If the CPU is passing dual prime I would be looking more at the motherboard. You cant test the parts individually sometimes when dividers and multis are involved though. Do memtest with the exact settings that make you blue screen.

Mine does this:

9x multi, 300htt, 133 divider = stable
10x multi, 270htt, 166 divider = unstable
10x multi, 245htt, 200 divider = unstable
 
Jakalwarrior said:
If it works at 2.6 perfectly fine then I wouldnt blame windows.
Click to expand...

It's just really weird, when I was trying to do the same thing a few months ago the computer would just reboot if it errored, now it bluescreens with a memory dump when I'm doing the same exact thing.
 
Does your board allow you to change Read Preamble or Max Asynchrnous Latency? If so try loosening them up about 1ns each.

Also its slightly possible your chipset needs a voltage bump. Also are you sure temps aren't a concern here?
 
acphydro said:
Does your board allow you to change Read Preamble or Max Asynchrnous Latency? If so try loosening them up about 1ns each.

Also its slightly possible your chipset needs a voltage bump. Also are you sure temps aren't a concern here?
Click to expand...

It's an Asus board, so I doubt it.

I did bump the voltage on the chipset up (this board only lets me go up 0.1v).

I tried bumping up the HTT voltage too and didn't have any luck.

The CPU temps aren't that bad at all, 53-54C max.

The chipset gets up to like 42-43C, it gets this hot at other speeds and doesn't cause any problems.
 
Here's what I have to work with Bioswise (these pics are old and don't show current settings):

Before anyone asks, I do have my PCI bus locked.

timingsgd7.jpg



dsc03115ba9.jpg
 
You must log in or register to reply here.
Back
Top