Quote Originally Posted by Mysers Briggs View Post
Quote Originally Posted by topgundcp View Post
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.

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.