Meh 2 BSOD's

[Judo Flounder]

Ok just a few minutes ago I booted up but as soon as the Windows loading screen popped up I got a BSOD.

It said: 0x0000004E

PFN_LIST_CORRUPT

I rebooted and wanted to check the error but a few minutes after logging on I got another one that said: 0x0000001E

ClassPNP.sys

Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFFA6000DA9031
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information: 7dc11f1b-e881-40a0-bbd4-a56f08c21922

Anyone know what the problem might be?

Thanks

 

[KrossX]

I just searched for your errors in google and found this.

PFN_LIST CORRUPT means that the system went to swap memory between the RAM and the VRAM on the hard drive, and couldn't. either: Pagefile.sys is not properly addressed.. did you change it's location in the registry? HDD Corruption -- The bad sector is located inside the pagefile.sys (although usually this would just cause a hang) BAD RAM -- (usually would give you a Page Fault Error instead)

Source.

Basicly, do a Memtest86+ to ensure your memory is working properly. Or try leaving only one stick of RAM and see if the problem is gone.

Also, have you messed with your BIOS before the error?

 

[Judo Flounder]

I just searched for your errors in google and found this.

PFN_LIST CORRUPT means that the system went to swap memory between the RAM and the VRAM on the hard drive, and couldn't. either: Pagefile.sys is not properly addressed.. did you change it's location in the registry? HDD Corruption -- The bad sector is located inside the pagefile.sys (although usually this would just cause a hang) BAD RAM -- (usually would give you a Page Fault Error instead)

Source.

Basicly, do a Memtest86+ to ensure your memory is working properly. Or try leaving only one stick of RAM and see if the problem is gone.

Also, have you messed with your BIOS before the error?

I ran Memtest for 8 hours and no errors and didn't touch BIOS at all. Will disabling virtual memory help you think?

 

[KrossX]

You can never diable the swap file completely... but it's worth the try.
Do so, then do a chkdsk on your disk.

If the problem is gone with the swapfile "disabled", defragment the disk before recreating it. And once you do so, put the minimum and maximum values the same, to avoid fragmentation.