BSOD issues on Windows 8.1, said to be due to ntoskrnl.exe

cheesycoke · Apr 25, 2015

Around the start of the year and the end of last year, I was having frequent BSOD errors which would also cause the computer to go into a loop of turning off, trying to turn on, then beeping as it turns back off. I am using an Alienware x51 PC. Back when this was happening, I posted this post to the forums, only to be informed that I must install plenty of drivers and update whatever else. I have since done that, and reinstalled none except for updating the tablet driver. A month ago I got one BSOD, but it was only once so I didn't care much. I got two today, with only one showing an error, being "PFN_LIST_CORRUPT." I tried uninstalling the tablet driver on the first BSOD, but that clearly didn't work.

Here is the dump log: View attachment 60846

I'm assuming this is the same thing as last time. If anyone can help, can you also help with how to avoid this in the future? Thank you.

Addictive Gamer · Apr 25, 2015

Hi,
It could help if you in addition to provided files can perform a memory test:

Open Memory Diagnostics Tool by opening [FONT=WOL_Bold]Control Panel[/FONT]. In the search box, type [FONT=WOL_Bold]Memory[/FONT], and then click [FONT=WOL_Bold]Diagnose your computer's memory problems[/FONT].*

If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
Choose when to run the tool.

Select an option to reboot your PC and wait for completion then post results.

cheesycoke · Apr 27, 2015

Addictive Gamer said:
Hi,
It could help if you in addition to provided files can perform a memory test:

Open Memory Diagnostics Tool by opening [FONT=WOL_Bold]Control Panel[/FONT]. In the search box, type [FONT=WOL_Bold]Memory[/FONT], and then click [FONT=WOL_Bold]Diagnose your computer's memory problems[/FONT].*

If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

Choose when to run the tool.

Select an option to reboot your PC and wait for completion then post results.

Sorry for taking so long to respond.
I just had it run next time I turned on the computer last night and turned it on again today, where do I find the results and if it even ended up working?

Addictive Gamer · Apr 27, 2015

First time you turn on PC after enabling memory check, the memory check will automatically start.
It will take some time to complete, you can either sit in from of your PC and watch or leave it alone.

See this if you choose 2nd option:
Memory Diagnostics Tool - Read Event Viewer Log - Windows 7 Help Forums

cheesycoke · Apr 27, 2015

Addictive Gamer said:
First time you turn on PC after enabling memory check, the memory check will automatically start.
It will take some time to complete, you can either sit in from of your PC and watch or leave it alone.

See this if you choose 2nd option:
Memory Diagnostics Tool - Read Event Viewer Log - Windows 7 Help Forums

The results I got were that no errors were detected in the diagnostic, for both parts that it did.

Addictive Gamer · Apr 28, 2015

OK,
We'll perform another test.
Here is a link to download a tool from Intel website:
Intel® Processor Diagnostic Tool (64-bit)

On the above link you need to accept the agreement, download and install the tool by performing these steps:
1. Close all programs you currently have opened
2. Run installer and it will show you following:
View attachment 60922

3. Hit OK to start extraction and setup will start ( Next, accept and so on )
4. Once setup is complete leave the check box enabled like in image bellow click "Finish" and test will run.

View attachment 60923

6, Take a screenshot of test results and paste it here like I did mine bellow:

View attachment 60924

cheesycoke · Apr 28, 2015

Addictive Gamer said:
OK,
We'll perform another test.
Here is a link to download a tool from Intel website:
Intel® Processor Diagnostic Tool (64-bit)

On the above link you need to accept the agreement, download and install the tool by performing these steps:
1. Close all programs you currently have opened
2. Run installer and it will show you following:
(image)
3. Hit OK to start extraction and setup will start ( Next, accept and so on )
4. Once setup is complete leave the check box enabled like in image bellow click "Finish" and test will run.
(image)
6, Take a screenshot of test results and paste it here like I did mine bellow:
(image)

This program looks shady, but whatever it seems real enough.
Here are my results.

View attachment 60925

Addictive Gamer · Apr 28, 2015

OK, First Please tell or better give a link where you downloaded your drivers.

For now I can only say to uninstall Avast! antivirus, it's known to cause BSOD's with Windows 8.1
Windows defender will activate it self automatically so you don't need to worry about AV. Windows defender is updated by using Windows updates so update Windows afterwards.

topgundcp · Apr 28, 2015

You have 3 .dmp files. 2 crashes were caused by: steamwebhelper process which is part of steam and the third crash was caused by memory corruption.

I suggest to turn off steam by disabling it from startup and also turn off avg as suggested above.

Mysers Briggs · Apr 28, 2015

topgundcp said:
You have 3 .dmp files. 2 crashes were caused by: steamwebhelper process which is part of steam and the third crash was caused by memory corruption.

I suggest to turn off steam by disabling it from startup and also turn off avg as suggested above.

Not really.
Just because a process is running at the time of the crash, it doesn't mean that was the cause.

Without a Kernel dump for those two 0x101 CLOCK_WATCHDOG_TIMEOUT bugchecks, we'll never know.
The latest crash isn't helpful because of the minidump's size.

Code:

0: kd> .bugcheck
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`0007a58b 00000000`00000006 00000000`00000011

0: kd> k
Child-SP          RetAddr           Call Site
ffffd000`324dc778 fffff802`a367a737 nt!KeBugCheckEx
ffffd000`324dc780 fffff802`a34c0032 nt!MiBadRefCount+0x4f //Bad PFN count
ffffd000`324dc7c0 fffff802`a34bfd21 nt!MiInsertNonPagedPoolOnSlist+0x2e2 //Insert a non paged pool memory onto a singly linked list
ffffd000`324dc820 fffff802`a34bf8c2 nt!MiFreePoolPages+0x5d
ffffd000`324dc850 fffff802`a3720bcc nt!ExFreeLargePool+0x492
ffffd000`324dc8f0 fffff802`a3840f20 nt!ExFreePoolWithTag+0x72c
ffffd000`324dc9e0 fffff802`a3a84eae nt!PfpFlushBuffers+0x24c
ffffd000`324dca90 fffff802`a357d36c nt!PfTLoggingWorker+0x156 
ffffd000`324dcc00 fffff802`a35d42c6 nt!PspSystemThreadStartup+0x58
ffffd000`324dcc60 00000000`00000000 nt!KiStartSystemThread+0x16

0: kd> !pfn
Unable to get PFN database address fffff802a37e00f0

It looks like a driver has referenced memory which has been locked on a list, meaning that it shouldn't be accessing the PFN because it is preforming I/O work. What driver? Impossible to tell with a minidump because the context prior to this trap frame hasn't been saved in this dump.

When you next get a crash, go to C:\Windows\MEMORY.dmp copy it to the desktop, compress it in a .zip folder and upload it to a file sharing site. If it's a 0x101, it should help us find out what has gone wrong. Could be a memory issue, could be a bad processor, or even a failing motherboard. Impossible to tell unless you can find your motherboard manual, identify what the beeps were when you started up your PC and identify what they mean.

cheesycoke · Apr 28, 2015

Mysers Briggs said:
topgundcp said:

You have 3 .dmp files. 2 crashes were caused by: steamwebhelper process which is part of steam and the third crash was caused by memory corruption.

I suggest to turn off steam by disabling it from startup and also turn off avg as suggested above.

Click to expand...

Not really.
Just because a process is running at the time of the crash, it doesn't mean that was the cause.

Without a Kernel dump for those two 0x101 CLOCK_WATCHDOG_TIMEOUT bugchecks, we'll never know.
The latest crash isn't helpful because of the minidump's size.

Code:

0: kd> .bugcheck Bugcheck code 0000004E Arguments 00000000`0000009a 00000000`0007a58b 00000000`00000006 00000000`00000011 0: kd> k Child-SP RetAddr Call Site ffffd000`324dc778 fffff802`a367a737 nt!KeBugCheckEx ffffd000`324dc780 fffff802`a34c0032 nt!MiBadRefCount+0x4f //Bad PFN count ffffd000`324dc7c0 fffff802`a34bfd21 nt!MiInsertNonPagedPoolOnSlist+0x2e2 //Insert a non paged pool memory onto a singly linked list ffffd000`324dc820 fffff802`a34bf8c2 nt!MiFreePoolPages+0x5d ffffd000`324dc850 fffff802`a3720bcc nt!ExFreeLargePool+0x492 ffffd000`324dc8f0 fffff802`a3840f20 nt!ExFreePoolWithTag+0x72c ffffd000`324dc9e0 fffff802`a3a84eae nt!PfpFlushBuffers+0x24c ffffd000`324dca90 fffff802`a357d36c nt!PfTLoggingWorker+0x156 ffffd000`324dcc00 fffff802`a35d42c6 nt!PspSystemThreadStartup+0x58 ffffd000`324dcc60 00000000`00000000 nt!KiStartSystemThread+0x16 0: kd> !pfn Unable to get PFN database address fffff802a37e00f0

It looks like a driver has referenced memory which has been locked on a list, meaning that it shouldn't be accessing the PFN because it is preforming I/O work. What driver? Impossible to tell with a minidump because the context prior to this trap frame hasn't been saved in this dump.

When you next get a crash, go to C:\Windows\MEMORY.dmp copy it to the desktop, compress it in a .zip folder and upload it to a file sharing site. If it's a 0x101, it should help us find out what has gone wrong. Could be a memory issue, could be a bad processor, or even a failing motherboard. Impossible to tell unless you can find your motherboard manual, identify what the beeps were when you started up your PC and identify what they mean.

Oh cool, thank you for this giant detailed post. According to Dell, the beep code means "BIOS ROM checksum failure - Possible MB failure"
So yeah, it's most likely an issue with the motherboard.
I haven't gotten the crashes ever since I made that post, but here's the current one which hasn't been modified since that day.
MEMORY.zip :: Free File Hosting - File Dropper: File Host for Mp3, Videos, Music, Documents.
Thank you for attempting to help. I desperately hope it isn't a hardware issue, or at least one that can't be easily fixed.

BSOD issues on Windows 8.1, said to be due to ntoskrnl.exe

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Well-Known Member

My Computer

Member

My Computer

New Member

My Computer