V2000Z BIOS F.24 & RM CPU Clock 2.05

I recently did a fresh install of my notebook. Prior to this, I was running 4x at 0.900V and 10x at 1.200V rock solid. After the reinstall, I encountered two freezes at light load, so I increased the voltage by 0.025V to every P-State. Then today, I encountered the blue screen of death... I upped the voltage again by 0.025V to 4x at 0.950V and 10x at 1.250V. The other interesting I've found is that sometimes I notice my CPU running at 833MHz and 1633MHz via MobileMeter. Any thoughts on this?

 

Reload, bios defaults at once see. I am not sure, but sometimes with the all the fiddling we are doing bios is getting screwed up. Letus know if loading defaults in bios helped.(Helped for me)

 

I experienced a similar thing when I upgraded to F.23 and RMClock 2.05. I simply returned to RM 1.8 and the problem disappeared.

 

Do you mean exit RM Clock to go back to the default settings? I know you can't touch the BIOS settings with the exception of the boot order.

F.24 and RM Clock 2.05 was working fine till I did a reinstall. But if things don't work out, I may take your advice.

 

Just got the blue screen of death again... it's funny, but this only happens towards the end of the day. I usually turn my notebook on at 9am and don't shut it off till about 7pm. Yesterday, the same thing happened around the same time at 6pm.

 

I know we can only change Video memory and boot options, but you can select option load setup defaults. After that you can change whatever you want to change in bios and reload.

I had problem when I was fiddling with A64Tweaker and RMClock initially, and had this random BSOD, then I reset the bios( with default settings) everything is working fine after that.

So, it hardly takes a minute, so would suggest trying that first.

 

I actually did that. I also killed RM Clock to reset to the default values in Windows... still no luck. I'll try it again and upping the voltage one more increment. See how that works. Thanks.

 

Ambient temperature is probably higher later in the day? More than a few overclocks that worked just fine in the Michigan winter have blown up in the summer. Same goes for undervolts.

 

Do you mean that getting a good cooling pad will produce better undervolting results?

 

Slightly better, maybe. Lifting up the back of the notebook slightly so the fan intake get better airflow and convection moves heat up and out will help a bit too. I'd say you're just pushing your voltage settings a little too far though.

 

I've actually got a notebook cooler and my CPU temps stay in the low 40s. I just had another crash at 4x @ 0.950V ~ 10x @ 1.250V in the morning, so I don't think it's the temperature. As for the voltage... it was rock solid at 4x @ 0.900V ~ 10x @ 1.200V till I did a reinstall. I followed chinna_n's advice, but still no luck. I'm going to try vassil_98's advice and go with RM Clock 1.8 to see if that fixes things. Again, thanks for all your help guys.

 

Using RM Clock 1.8 at 4x @ 0.975V ~ 10x @1.275 with two crashes thus far. I also noticed minor glitches in other programs. For instance, MobileMeter not being able to detect my HDD. Anyway, I'm beginning to think that something went wrong doing my install of Windows. I may have to reinstall everything this weekend.

 

By any chance is it related to Memory? I have been running with 0.95v at 4x and 1.25v at 10x since last october, never had a problem or crash. Did you run memory test, if not test it overnight and see if it has anything todo with crashing.

 

That's a good idea. I've never done a memory test.

 

I've been running Memetest86 for just under 40 minutes and have 2 errors already. How do I know which stick is faulty? Do I have to pull one and test it and do the same for the other? Here's what I have so far:

Tst = 4
Pass = 0
Failing Address = 0003a4d2744 - 932.1MB
Good = 4fcf3e39
Bad = 4cf3e3b
Err-Bits = 000000
Count = 2
Chan = 1

 

Yes, test each one individually. Could be one, could be both, and possibly they only fail when paired together. Most likely it's just one of them that's failing though. I'd buy one of two of these and eBay whatever HP sends you to replace your faulty SODIMM(s)... but then, I'm always looking for excuses to buy new computer toys .

As soon as you find one error in a SODIMM you can stop testing.

Nice catch chinna_n.

 

I've been using Corsair ValueRAM PC3200 1GB + 512MB since last September without issue. This must be a recent thing. Thanks for all your help.

 

Generally, it should not be related to windows installation. So, if RM Clock started failing like that, then it must be some hardware problem. First thing I suspect is memory, then MB. CPU is the lastone and very unlikely candidate.

I hope, that is only Memory sticks issue, not memory slot and/or MB problem.

 

Sh*t. I don't think it's the memory. I tried both sticks in both slots one at a time without error for at least 2 hours. I only get errors when both sticks are in place. I'm guessing this is a motherboard problem.

 

No, it's probably still the memory. I had that same problem with two Corsair 512MB sticks in my old zv5000z. Replacing them with two Crucial sticks fixed things. I'm not very impressed with Corsair's ValueRAM line.

 

I doubt I can return my memory this late in the game... and I don't want to shell out any more money on this particualr notebook. I guess I'll just have to live with the 1GB stick till I buy a new notebook early next year. At least I'm back to 4x @ 0.900V ~ 10x @ 1.200V. Thanks for your help.

 

John,
I have similar situation earlier with my previous v2000z. It was the mobo.
Yours might be the same case....
Check out my threads here;
(please ignore my "whine" about the HP support quality)
http://forum.notebookreview.com/showthread.php?t=38011
http://forum.notebookreview.com/showthread.php?t=38961
http://forum.notebookreview.com/showthread.php?t=41268
http://forum.notebookreview.com/showthread.php?t=44051

 

Thanks tempoct, but I actually figured out what the problem was. Even though I get errors during Memtest86, I'm running solid at 4x @ 0.900v ~ 10x @ 1.200V with both my memory slots filled. I realized I updated the AMD Processor driver during reinstall. Reverting it back to the one that came with my installation disc fixed everything. Though I have no idea why that would make a difference.

 

Or you're just not accessing the bad bits in a way that crashes the machine this time. As a rule, when MemTest says you have errors, it's not kidding. To be thorough, get a second opinion from Microsoft's memory diagnostic.

 

I completely agree. If Memtest says there are errors, then you have errors whether your laptop crashed or not. May be these errors did not come into any critical application yet. Run prime95 for 24 hours and see. Even if it is not crashing it is potentially giving wrong results in some calculations.

 

I'll try Microsoft's memory diagnostic tonight. However, if I keep getting errors, I'll just pull the 512MB stick again and live with only 1GB. I ran Memtest86 for 4 hours each with one stick installed and had no problems whatsoever. Again, thanks for all your help.