Something wrong with these readings?

[blurry]

Particularly the temp and voltage readings..

My PSU is a Seasonic Super Silencer 400 and the CPU is cooled with a Zalman CNPS7000A-Cu @ 1875RPM.

[EWBatOVAclockin]

Look good to me. Nice temps. What kind of CPU do you have running?


Woops srry I didn't see your sig. I got a 2.6c too. Man those are some nice temps. What are your temps on load. My idle temps with the stock are 35c @3ghz

[dicecca112]

looks great to me. The 3.3 is a little low for my tastes, but I'm a perfectionist and that is well within acceptable limits.

[blurry]

Look good to me. Nice temps. What kind of CPU do you have running?


Woops srry I didn't see your sig. I got a 2.6c too. Man those are some nice temps. What are your temps on load. My idle temps with the stock are 35c @3ghz
I don't remember exactly how much it was under load, but it was approaching 40c. At another forum someone said it was absolutely impossible to get such temps on a P4 with what I had, so I double-checked here to be sure.

looks great to me. The 3.3 is a little low for my tastes, but I'm a perfectionist and that is well within acceptable limits.
The 3.3v rail is exactly what I was worried about. I get readings of 3.184, 3.216, and 3.264. Is that enough to cause BSODs?

[xTrEmEoVrClOcKr]

Yay, a 2.6C thread :D. Lower the V-Core a bit ... your just waiting for GNDS / SNDS. My 2.6c was capable of this before it hit GNDS, lay off the voltage :D.

http://img.photobucket.com/albums/v392/xtremeovrclockr/3.jpg

[EWBatOVAclockin]

Hey extremovaclocka, how long did you have your 2.6 running at those speeds and how stable was it??? I would love to get those speeds :santa:.

PEACE

[xTrEmEoVrClOcKr]

I burned it in for around 3 weeks straight with CPU burn-in, and I started to OC it. I noticed on the forums that they normally bottom out at around 3.25. I had it at 3.5ghz on stock HSF. After another week, I got my PC4000 ram and decided to push the ram. After getting to 3.63Ghz, I decided to stop pushing it. Then, I decided to raise the voltage :rolleyes: I pushed 1.75V through it for around a week. (Didn't know about GNDS until I subscribed here :() And BOOM. The thing droped its OCs to 3.2ghz and never made it over 3.4 stable again. Just to prove that GNDS really does kill chips :). Oh btw, it primed stable 12 hours at 3.55Ghz, 3.6ghz was pushing it. My temps were like 19C when I pushed it, and it loaded at around 25C.

[EWBatOVAclockin]

Wow very nice, and what kind of cooling did you have??? I think I might give it a go for 3.5. I'm about to burn it in at 3 tonight and tommrow and see how that goes. Thanks for the input.

[xTrEmEoVrClOcKr]

I cooled it with Stock HSF for the majority of the time, When I attempted 3.6ghz, this is what I used, Modded Zalman 7000CU:http://img.photobucket.com/albums/v392/xtremeovrclockr/IMG_0136_2.jpg

Sorry for thread jacking, nothing personal :(.

[EWBatOVAclockin]

Sheesh that looks like a beast :eek: . How is it modded BTW?? And how much do those go for because I sure do love the sound of 20idle :D

[xTrEmEoVrClOcKr]

The 7000CU goes at around $45 (US) on www.newegg.com. Its modded with the Thermaltake Fan on it, so get some beefy fan that pushes a lot of air, and put double sided tape on the bottome of the fan and attach it. Make sure its good stuff cause, the last thing you want is a fan at 4 or 5k RPM hitting your video card / other components. My 2.6C ided at around 22C all the time.

[EWBatOVAclockin]

Wowwwwwwwwwwwwwwwwwwwwwwwwwwww..................I love the sound of that, what kind of tape did you use and where did you get it. And what kind of fan did you buy to replace the stock one. I'm probably going to get the same thing you have because like I said before I love the way those temps sound :D . Thanks also.

[xTrEmEoVrClOcKr]

Its basic 3M Double Sided Tape, make sure to get the thick stuff. I got my tape at Staples and this Thermaltake Fan I salvaged off a Volcano 12, So you might have to get a Thermaltake Smart Fan 2, 92mm Tornado (if you can bare the noise), or something that pushes a lot of air. You have to cut the actual fan out of its casing, put double sided tape on the bottom, and make sure it holds. BTW, if you have AIM, PM me and we can talk about this .. .cya.

[blurry]

Yay, a 2.6C thread :D. Lower the V-Core a bit ... your just waiting for GNDS / SNDS. My 2.6c was capable of this before it hit GNDS, lay off the voltage :D.


The VCore reading is for a majority of the time at 1.584 (maybe dropping to 1.504 and 1.552 once) and I actually reverted all BIOS settings to their defaults. Previously I had not messed with the VCore either.

[blurry]

Asus Probe readings also differ a tad from Everest Pro.

[hawtrawkr]

Particularly the temp and voltage readings..

My PSU is a Seasonic Super Silencer 400 and the CPU is cooled with a Zalman CNPS7000A-Cu @ 1875RPM.

i wouldnt put much stock in what asus probe says your rails look like best bet has always been to check them with a dmm.

as far as the temp goes it looks right when you factor in asus uses an external probe instead of a calculation across the core so their temps tend to be a little higher than they are reported as.

[xTrEmEoVrClOcKr]

Ok, thought you were really pumping 1.66V through it, good to here its at 1.6V or under.

[blurry]

So the general consensus is that the BSODs I am encountering are not caused by the PSU.

I just got this BSOD moments ago- bad_pool_caller stop: 0x000000c2 (0x00000007, 0x00000cd4, 0x0000003a, 0x86486008)

The ram has been tested with memtest twice.

edit- new stop error: driver_irql_not_less_or_equal stop: 0x00000001 (0x00000004, 0x00000002, 0x000000000, 0x858153e0)

[SolidxSnake]

just a suggestion on ASUSProbe...

mine reads REALLY accurate to what the bios says... maybe like .5°C off... its a P4P800 rev2 board... if it does read low tho, then my cpu has been at 80+°C... (it was at 72° after a few minuts of primin... the crap thermalgoop ibuypower used was doing a badd job)

eek

[betterlife18]

So the general consensus is that the BSODs I am encountering are not caused by the PSU.

I just got this BSOD moments ago- bad_pool_caller stop: 0x000000c2 (0x00000007, 0x00000cd4, 0x0000003a, 0x86486008)

The ram has been tested with memtest twice.

edit- new stop error: driver_irql_not_less_or_equal stop: 0x00000001 (0x00000004, 0x00000002, 0x000000000, 0x858153e0)

BAD_POOL_CALLER is usally caused by some jacked up hardware plugged into the USB ports, most likely a modem or printer, but could also indicate memory. IRQL_NOT_LESS_OR_EQUAL, hmm, my favorite blue screen. Most likely driver, also could be memory.

So it's either memory or something in your USB port (I'm thinking something in your USB port).

[blurry]

BAD_POOL_CALLER is usally caused by some jacked up hardware plugged into the USB ports, most likely a modem or printer, but could also indicate memory. IRQL_NOT_LESS_OR_EQUAL, hmm, my favorite blue screen. Most likely driver, also could be memory.

So it's either memory or something in your USB port (I'm thinking something in your USB port).
Thanks for the reply.. I have nothing plugged into the USB ports (my printer is on the parallel port). I've also tested the memory with memtest- is there another way to find out if they're faulty or not?

I've just reverted back to 43.45 from the previously installed 66.93. We'll see if that puts a stop to the BSODs.

I was getting the occasional BSOD even before I added another hd and did a fresh install of WinXP Pro. Also, I'd like to note that I have SP1 installed.

[betterlife18]

66.93? Are you talking about the NVidia drivers? If so... I find 56.72 to be the best drivers from pre-6800 series cards.