HP MCP61PM-HM (Nettle2) 5.27 With Unlocked Overclocking Options

[banana19]

Has anyone else experienced problems with the dram settings? If I even enable the option to change the dram settings witout actually making changes it causes my pc to beep repeatedly and not boot upon saving the changes in bios and restarting. I have a HP A6130n with two sticks of the factory samsung ram and two sticks of pny ram with heat spreeders. Also, I'm using the abit.bin bios posted a few pages back.

have not had any problems, not using factory ram. try changing to 2T, or raising voltage.

Nick

[jbreedlo]

Has anyone else experienced problems with the dram settings? If I even enable the option to change the dram settings witout actually making changes it causes my pc to beep repeatedly and not boot upon saving the changes in bios and restarting. I have a HP A6130n with two sticks of the factory samsung ram and two sticks of pny ram with heat spreeders. Also, I'm using the abit.bin bios posted a few pages back.

have not had any problems, not using factory ram. try changing to 2T, or raising voltage.

Nick

I have left all default settinsgs which would include 2t I think. The only thing I am changing is to enable dram timing settings but not actually changing anything. I did raise the voltage to the maxed allowed in the bios of 1.9 and that is ok. However, once I enable the dram timing settings and reboot, the pc just beeps and I have to remove the battery to reset bios settings. I guess I could try and remove the factory ram and use only the pny ram. I just don't understand why enabling the timing changes without actually changing anything would cause issues. Unless once you enable the dram timing settings the values change to values other than what would be set if that setting was left disabled

[Vancete]

Im trying to back to M613Z_19 because I have now Biostar and have a lot of errors, but when I try to flash witch awdflash M613Z_19.BIN /py /sn /cc /cd /cp /wb /r /f but it shows "Flash ROM is Write-Protected Please make sure wether lockout jumpers is set to correct or not"

Anyone knows whats happen?

Thanks!

Solution for this?

[TheWiz]

Well if you are jumping from 667 to 800 yeah the mobo will beep because your ram can't handle it, you need to bump things in very small increments and get it stable. As for the CPU upgrade, its a work in progress.

Thanks,
TheWiz

[Vancete]

Waiting for solution for "Flash ROM is Write-Protected Please make sure wether lockout jumpers is set to correct or not" :p

[MrTangoWhisky]

read this:
http://forums.pcper.com/showthread.php?p=2906947&postcount=15
and
http://forums.pcper.com/showthread.php?s=&threadid=263636
I hope this could be the solution!
In my environment (Ijust tried it out!) it is working with an A7N8X-LA and with a MCP61PM-AM!
Maybe you have to detach the board from it's case and try again without *GND* anywhere...

[tuxit09]

I have Mainboard MCP61PM-HM Rev:2:2

Said board is now bricked.

Flashed with command and mentioned file "awdflash M613Z_19.BIN /py /sn /cc /cd /cp /wb /r

Flash appeared successful, upon re-boot. no video output, no beep codes, stripping the ram out does not give no memory beep codes, will not POST. removed PCI-e video card, used on board video, no output. pressing power for 5 seconds throws fans into high speed mode. Must dico A/C power to power off unit.

I even tried to boot the usb dos disk to see if i could blindly re-flash from the keyboard either the hacked (fatal) one or oem HP bios. = no boot.

Removed main board battery, used clear cmos jumper. = totally dead.

Flash chip for BIOS is removable. Could probably be repaired. Too depressed to deal with it.


Bummer. This was my main rig.

Anyone got any tricks?

[1234s282]

Sorry to hear about your unsuccessful flash , however i dont think the chip in the picture is your bios chip! (as these chips are not easily removable and VIA doesnt make bios chips)

Please supply a picture of the whole motherboard , read our bios recovery instructions on the main site and we can see what we can do!

UPDATE: you can buy a replacement chip here for $1! http://cgi.ebay.com.au/Bios-Chip-HP-A635...2c5593ab60 Ask them to preprogram it and we can walk you through the replacement procedure

Regards
Admin

[tuxit09]

Sorry to hear about your unsuccessful flash , however i dont think the chip in the picture is your bios chip! (as these chips are not easily removable and VIA doesnt make bios chips)

Please supply a picture of the whole motherboard , read our bios recovery instructions on the main site and we can see what we can do!

UPDATE: you can buy a replacement chip here for $1! http://cgi.ebay.com.au/Bios-Chip-HP-A635...2c5593ab60 Ask them to preprogram it and we can walk you through the replacement procedure

Regards
Admin

Thanks for support.

I have attached the photo of entire MB, initial photo was really only to confirm that I had used a file intended to be used with my board, hacked albeit. I just wanted to eliminate my user error of mother board model. Have I mistaken the intended recipient board of M613Z_19.BIN? In the morning going to try and ask the wife for a new mobo, she was there when flash failed, I told her it was risk before doing it, don't I look like an idiot now? lol

I'm heading to the recovery information now. thanks.

I need my box like yesterday, bios chip replacement is more hassle than replacement of mobo.

might blacklist my board with this bios version. I am 99% sure it was not operator error, Unit powered by UPS so power fluctuation should not be culprit, it reported it wrote all blocks to flash, then failed upon reboot attempt.    

[TheWiz]

Hey tuxit09,

Hate to be the pessimest here but you didn't read instructions. This BIOS is for the NETTLE 2 ONLY! The rev 2.2 of your board indicates it is a NETTLE3 and IS NOT the same BIOS.

On a happier note I had another user make this same mistake and I have reprogrammed this mobo before if you send the chip into our programming service.
We still haven't gotten a good Nettle3 BIOS yet, but the info was available if you read into the Nettle3 thread. (And earlier in this thread)

Anyways, a mistake is a mistake, easily fixable

Thanks for your understanding,
TheWiz