Sign in with
Sign up | Sign in
Your question

Random Blue Screens about 4~6 hours

Tags:
Last response: in Windows 7
Share
July 15, 2012 12:53:31 AM

Hi,

I installed recently my brand new Crucial M4 128GB.
Also a fresh version of the Windows 7 Ultimate x64.

But sometimes, about 4 and 6 hours I got random blue screen and reboot almost instantly.

When I get back to the desktop I see the following mensage:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1046

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 000000000041B8CE
BCP3: 0000000000000006
BCP4: 0000800000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071412-10342-01.dmp
C:\Users\Bergami\AppData\Local\Temp\WER-12043-0.sysdata.xml

I've done memory diagnostic but it has found no error.
Temps are ok, hottest core with 50C when load.
VGA hardly ever goes over 70C

That blue screen NEVER happened while I was playing a game, it happens when I am doing "nothing".

I' installed that system yesterday, this blue screens begun today.

How would I fix it?

Thank you


My config:

I5 3570K / Antec H2O 620 / EAH6870 / GA-Z77X-UD5H / Crucial M4 128GB / Sansung 1.5T 5200RPM / LG E2260 / Corsair Vengeance 1600Mhz 4x4GB / Upsai FHT-1200 / Seasonic 620W S12ii / Sentey GS-6000 / Tecl X7 G800V / Razer Imperator 2012 BF3 Edition
July 15, 2012 10:37:44 PM

Noone?
m
0
l
a b $ Windows 7
July 16, 2012 12:21:08 PM

Quote:
Bug Check 0x4E: PFN_LIST_CORRUPT

This indicates that the page frame number (PFN) list is corrupted.


For a BCP1 of 0x99:

Quote:
A page table entry (PTE) or PFN is corrupted.


Suspected bad RAM. Run memtest86 and check to see if you get any errors.
m
0
l
Related resources
July 16, 2012 1:48:47 PM

Can I use Prime95 instead of memtest86?

I ran Windows Memory Diagnostic and there were no errors.
m
0
l
a b $ Windows 7
July 16, 2012 5:18:14 PM

You can use Prime 95's blend test.

I don't have a very high opinion of windows memory diagnostic, and still recommend using memtest at some point. Then again, I've seen plenty of RAM failures that neither test catches [generally an occasionally stuck bit...]
m
0
l
July 16, 2012 5:42:29 PM

the bluescreen said it dump the errors to a file. Download bluescreenviewer and look at the logs. It should show which file/driver is causing the issue. Good luck
m
0
l
July 16, 2012 9:24:01 PM

I had not any blue screens/reboots today yet.

it's stable for about 8 hours, I am not sure how but...

The only thing I did, yesterday, was pressing F8 while the startup and select: "Start with the last valid configuration" or something like that.

I also ran today the "windows error-cheking".

I ran today the Prime95 and I left it about 25 minutes, had no problem.

m
0
l
!