bsod on startup help

OpenToSuggestions · 4 May 2008 at 18:49

I have a pc (sig) which had has new ram in the last week, and all was fine until today. I was using vista 32bit, did a vista update then an adobe acrobat reader update and upon restart bsod's happene very time. with error code 0x000000f4, and says something about physical memory dump complete.

The new memory has been installed a week with no problems, yet after this update I get bsod before log in every time, even with bios in fail-safe settings and upped voltage (I dont think the problem is the ram).
Windows safe mode solves no problems.

Any ideas?

TIA

neoboy · 4 May 2008 at 19:01

Error code is usually associated with HD problems rather than RAM. Tried doing a chkdsk?

OpenToSuggestions · 4 May 2008 at 19:11

it did one and found LOADS of problems. However this has not solvd the issue

OpenToSuggestions · 4 May 2008 at 20:13

just tried diff ram sticks and deffo is not the ram. just booting off vista disk, its all i can think off really

neoboy · 4 May 2008 at 21:03

Well if you're finding errors with chkdsk, then really chances are your HD is responsible for all this. Try reformatting and reinstalling Windows, if that doesn't do it then it's RMA time.

Jesus · 4 May 2008 at 21:19

0x000000f4 - Relates to the hdd as previously said. According to MS, the code means there is either a master/slave conflict on the boot drive, or a corrupt hdd/windows installation.

This problem occurs on a computer in which Windows XP or a later operating system is installed on a hard disk that is configured as a subordinate and no other device is connected to the same IDE controller channel (primary or secondary).

To resolve this behavior, use one of the following methods:
• For Parallel Advanced Technology Attachment (PATA) hard disks, configure your disk drive as master only. For Serial Advanced Technology Attachment (SATA) hard disks, connect the hard disk cable to a master channel SATA connector on the motherboard.
• Connect another device as a master, such as another disk drive or a CD drive or DVD drive.
• Change your PATA cables, your SATA cable, or your IDE cable even if the cable does not appear worn.
• Install Windows on a new hard disk because it is possible that your hard disk or your Windows installation may be corrupted.

Also try fixmbr /r and fixboot in the recovery console, always worth a shot before you wipe.