New blue screen issues

[Dagnis]

This started around the time I had to update my computer to play MCC (for some reason it wouldn't let you pick up weapons unless you had up to a certain W10 update). I checked my last crash in the event log and I got the following:
The bugcheck was: 0x0000004e (0x000000000000008d, 0x00000000003ff382, 0x0000000000410001, 0xffffbb87d3908f60). 

I believe that the 04e and 8d points me to a hardware issue, but I don't know what the other numbers mean. Trying to find out exactly what the cause is and how I can fix it (assuming it is hardware and w10 isn't being stupid because of updates).

[Boomwebsearch]

31 minutes ago, Dagnis said:

This started around the time I had to update my computer to play MCC (for some reason it wouldn't let you pick up weapons unless you had up to a certain W10 update). I checked my last crash in the event log and I got the following:
The bugcheck was: 0x0000004e (0x000000000000008d, 0x00000000003ff382, 0x0000000000410001, 0xffffbb87d3908f60). 

I believe that the 04e and 8d points me to a hardware issue, but I don't know what the other numbers mean. Trying to find out exactly what the cause is and how I can fix it (assuming it is hardware and w10 isn't being stupid because of updates).

The PFN (Page Frame Number) list is corrupted, this is used by your hard-disk-drive to locate your files' physical location on the drive's magnetic platters. This makes sense to have occurred after updating, run a disk check for errors, and it should be fixed.

 

How to Run a Disk Check for Errors:

 

1. Press the Windows Key on your Keyboard and "R" at the same time.

2. When you get the run box, type "cmd" and then press CTRL+SHIFT+ENTER

3. Select "Yes" when you get the User Access Control Prompt

4. When the command prompt opens, type in "chkdsk  /r " followed by Enter

5. Wait until you get a message stating “Chkdsk cannot run because the volume is in use by another process.” 

6. Type "Y" followed by Enter

7. Restart your PC

 

 

Visit Microsoft's Website on this issue:   https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x4e--pfn-list-corrupt

[Dagnis]

On 3/26/2020 at 4:04 PM, Boomwebsearch said:

The PFN (Page Frame Number) list is corrupted, this is used by your hard-disk-drive to locate your files' physical location on the drive's magnetic platters. This makes sense to have occurred after updating, run a disk check for errors, and it should be fixed.

 

How to Run a Disk Check for Errors:

 

1. Press the Windows Key on your Keyboard and "R" at the same time.

2. When you get the run box, type "cmd" and then press CTRL+SHIFT+ENTER

3. Select "Yes" when you get the User Access Control Prompt

4. When the command prompt opens, type in "chkdsk  /r " followed by Enter

5. Wait until you get a message stating “Chkdsk cannot run because the volume is in use by another process.” 

6. Type "Y" followed by Enter

7. Restart your PC

 

 

Visit Microsoft's Website on this issue:   https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x4e--pfn-list-corrupt

I did this for the C drive and it seemed to work for a little bit. I was able to game no problem. 

Then suddenly today I got three crashes back to back and it sent my computer into recovery mode or whatever on start up. 

Each time I got different error codes. The second two crashes happened nearly right away after boot up. I went straight to event log to try to find out what happened, and in the process it crashed. Not sure if that was the blame since I did it right after boot. 

The bugchecks in order of crashes are (for some reason I can only find 2 for today):
0x0000001e (0xffffffffc0000005, 0xfffff80355aa58e8, 0x0000000000000000, 0x000000000000002f). 
0x0000004e (0x0000000000000006, 0x000000000034452b, 0x0000000000000000, 0x0000000005520000). 

I've also encountered the follow in the last week:
0x0000007f (0x0000000000000008, 0xffffc90149f6f190, 0x00000000000000f8, 0xfffff8000b0bbeb2). 

0x0000000a (0x0000000000000969, 0x0000000000000002, 0x0000000000000001, 0xfffff8023ce9b90f). 
0x0000000a (0x00000000418b4944, 0x00000000000000ff, 0x0000000000000000, 0xfffff8026dac0903). 

 

This is really starting to get on my nerves to say the least. 

Could it be the drive itself is failing physically? It's an SSD and not the newest one, but not terribly old either. Or could it be ram?

[Dagnis]

Small update of my attempts to fix it. 

I ran a windows memory diagnostics. Came back clean. Just did a 'sfc /scannow' in cmd line.  It said it found corrupt files and successfully repaired them. Why didn't chkdsk find these? 

 

[Boomwebsearch]

59 minutes ago, Dagnis said:

Small update of my attempts to fix it. 

I ran a windows memory diagnostics. Came back clean. Just did a 'sfc /scannow' in cmd line.  It said it found corrupt files and successfully repaired them. Why didn't chkdsk find these? 

 

"SFC /scannow" and "chkdsk /r" are not the same and are for slightly different purposes. Check disk is for checking a drive for any file system errors and/or bad sectors and attempting to repair/isolate them if they are present. While sfc /scannow is for checking for any missing, modified, or corrupted Windows System Files to repair/replace them with a fresh version from the component store, this works generally better for system files errors in Windows specifically.

 

 

Please download (if you have not done so previously) and run Crystal Disk Info with your drive and post the results that it gives from the scan process.

 

Link to Crystal Disk Info:    https://crystalmark.info/en/software/crystaldiskinfo/

[Dagnis]

38 minutes ago, Boomwebsearch said:

"SFC /scannow" and "chkdsk /r" are not the same and are for slightly different purposes. Check disk is for checking a drive for any file system errors and/or bad sectors and attempting to repair/isolate them if they are present. While sfc /scannow is for checking for any missing, modified, or corrupted Windows System Files to repair/replace them with a fresh version from the component store, this works generally better for system files errors in Windows specifically.

 

 

Please download (if you have not done so previously) and run Crystal Disk Info with your drive and post the results that it gives from the scan process.

 

Link to Crystal Disk Info:    https://crystalmark.info/en/software/crystaldiskinfo/

First time ever using this so I hope I provide all the info you want.. 
for my C drive it says Good, 100%. 

Some other stats that seem interesting:
Raw Read Error Rate Current, 95, worst, 95, threshold 50. 
Retired Block Count, Current 100, worst 100, threshold, 3
Reported Uncorrectable Errors, Current 100, worst 100, threshold 0

SSD Life Left Current 100, Worst 100, threshold 10. 

 

Power on Hours, 23426.

Power on count 2435. 


I went to function and did rescan to get these. 

Is there anything in particular I should be looking for?

[Boomwebsearch]

6 minutes ago, Dagnis said:

First time ever using this so I hope I provide all the info you want.. 
for my C drive it says Good, 100%. 

Some other stats that seem interesting:
Raw Read Error Rate Current, 95, worst, 95, threshold 50. 
Retired Block Count, Current 100, worst 100, threshold, 3
Reported Uncorrectable Errors, Current 100, worst 100, threshold 0

SSD Life Left Current 100, Worst 100, threshold 10. 

 

Power on Hours, 23426.

Power on count 2435. 


I went to function and did rescan to get these. 

Is there anything in particular I should be looking for?

You want to look for the reallocated sector count values and the overall health status indicator most importantly. Is the C drive a separate drive or is it a lettered partition on one drive? 

 

What is the manufacturer and model of the SSD?

[Dagnis]

10 minutes ago, Boomwebsearch said:

You want to look for the reallocated sector count values and the overall health status indicator most importantly. Is the C drive a separate drive or is it a lettered partition on one drive? 

 

What is the manufacturer and model of the SSD?

Reallocation event count is 100 for each, threshold 3. 

The drive is it's own full drive. 

It's a kingston SV300S37A240G according crystal disk (been a while since I put it in)

 

[Boomwebsearch]

Try Microsoft's suggested repair/fix for this issue, if it doesn't work then we can try other troubleshooting strategies:    https://support.microsoft.com/en-us/help/2764302/0x0000001e-stop-error-occurs-intermittently-in-windows-7-sp1-and-windo