My new PC has died after a day of use HELP !!

Trifid

Trifid

Trifid

Soldato
Joined
18 Feb 2006
Posts
9,785
Just bought a new PC. Specs:
AMD 64 3000 s939 Venice
Gigabyte GA-K8N51GMF-9 NF4 s939
256Mb Sapphire ATI X1600PRO
1GB Corsair Value Select
Aspire X-Qpack
160 Gb Hitachi sata2 Hdd

It ran first time, and I got a day of gaming out of it, but whilst in counterstike it restarted on its own. It came up with the menu to select "safe mode" , "normal mode" etc, I selected normal mode and it kept restarting over and over again.

After another attempt later on I got back to the screen and selected safe mode, which sent me to a blue screen of death and an error:

PFN-LIST-CORRUPT

I have managed to get to windows once when selecting "last known good config" but the screen kept flickering, and i got windows errors, ati errors and sound errors popping up so I shut it down.

I decided to reformat and install windows again but its not copying the files over properly..coming up with error.

So does anyone have any ideas? Is the harddrive dead perhaps even though it worked fine before?

Any help would be great. Thank you.
 
Sorry about your probs.

Just Googled This ;

0x0000004E: PFN_LIST_CORRUPT
(Click to consult the online MSDN article.)
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

Error Message:

STOP: 0x0000004E (parameter, parameter, parameter, parameter) PFN_LIST_CORRUPT
Explanation:

This is a Windows 2000 Executive character-mode STOP message. It indicates the memory management page file number (PFN) list is corrupted.
User Action:

If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.


"Can be caused by corrupt physical RAM"

I notice you have 1.5g's of RAM ( odd number is that 1g + 512 or 3 x 512 ? )
Would suggest you start with just one stick in your board and test them individually.

( Also Checkout the "Blue screening on brand new set-up" Thread , Same error message ,same Geil RAM )

Cheers,

Mark
 
Last edited:
The specs in my sig are from my main PC, with 2x 512 and 2x 256 (despite what a lot of people say, it does run in dual channel.)

This isn't the first time after booting with new hardware. The whole PC is new hardware yesterday, with Corsair Value RAM, but it has been booted several times with it previously.

I am installing Windows with a different stick of RAM now. I have just set up the partitions, so it is copying files over now. I will keep you updated.

Edit: It has got further than before, I am now on the windows bit of the installation. It is in Windows now.
 
Last edited:
OK its working with this different RAM, does this mean I need to return the RAM? Should I perhaps put the corsair stuff back in to make sure it is definately broken?
 
try running memtest86+ to test the RAM and see if you get any errors with the original configuration you had when your system went pair shaped after one day...

you mentioned you have used diff RAM now....is it 2 x 512 or 2 x 256....

how did you get it to work?
 
yeap memtest http://www.memtest.org/

download the following version:

memtest86+ v1.65 (10/01/2005) Download - Pre-Compiled Bootable ISO (.zip)

unrar it and then burn it as an image to cd and then in the bios change to boot from cd

so stick to the original fault RAM configuration see if memtest finds any errors..

the program should start running as soon as it opens...run it for at least 3 - 4 hours and see if you get any errors...

good luck...
 
You must log in or register to reply here.
Back
Top Bottom