[SOLVED] Inconsistent BSOD - Windows 8.1 x64

Code: 
1: kd> .bugcheck
Bugcheck code 0000004E
Arguments 00000000`0000008d 00000000`00056c79 00000000`00410001 fffff680`001667db

1: kd> !pfn 56c79
Unable to get PFN database address fffff800fbd760f0

The first parameter, 0x8D, indicates the page free list is corrupt.
The second parameter, .56c79, is the page frame number which has an inconsistent state.

This is almost certainly a hardware issue, and given that you've already replaced the RAM, it is either failing (unlikely), or you have a failing motherboard.
On top of all the random BSODs, it wouldn't surprise me.
 
It certainly looks like it.
Is it still under warranty?

Test the RAM again using Memtest86+, I'm curious to see whether there are any errors still.
 
I can't recall if my Motherboard has a warranty, but MemTest86+ reported no errors this time.
Would they actually take back over 2 year old Motherboard, heavily used with warranty? I mean, how can they be sure it's broken?
 
You need to run memtest86+ for at least 8 passes to ensure the results are reliable.
If it has warranty, and it is faulty through no fault of your own, then yes.
There is no way to be 100% sure with a motherboard, you cannot test the board itself, but rather the components.
Usually, if you are getting inconsistent and various crashes, it's a motherboard failure.
 
Well i did ran MemTest86+ 8 passes so there doesn't seem to be anything in the RAM.
And i've gotten crashes with wide variety, so it seems to be related to the Motherboard. I'll have to check the warranty.
 
My apologies, I presumed because of the small time frame it took you to run memtest, that you didn't run it for at least 8 passes.
 
So I just had a many crashes in a row. First one was something around "DRIVER_IRQ_NOT_LESS_OR_EQUAL (win32[some letters which I can't recall].sys). Then it crashes again and I got kicked into Custom Startup screen.
I tried to restart my computer, it got stuck in "GIGABYTE" start screen. I shut it down and then i got a new screen. It said something around: "Computer must be fixed, 0x000000034d has been detected" or something along those lines and requested a syster restore. I shut it also down and tried to restart and then the computer came back on like normal.
I hope that wasn't too confusing.

This is quite itchy situation.
I'll include the Minidump I got the first time, because no other dumps were generated.
(This might be overheating issue, since weather is getting quite hot and my computer is freaking hot when I look into it after crash. Also, it crashed after I had exited from a game, and went to another one and the computer starts working after I have let it cool down a bit.)
 

Attachments

Can you save your System event log, from the Event Viewer?
It's under Windows Logs > System on the left hand side when you open the Event Viewer.

Code: 
5: kd> .bugcheck
Bugcheck code 00000119
Arguments 00000000`00000001 00000000`00489deb 00000000`00489dee ffffe000`9e0e7010

5: kd> k
Child-SP          RetAddr           Call Site
ffffd001`9813a8e8 fffff800`b82049ca nt!KeBugCheckEx
ffffd001`9813a8f0 fffff800`b8223003 watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd001`9813a930 fffff800`b821925f dxgmms1!VidSchiProcessIsrCompletedPacket+0x8ec3
ffffd001`9813aa20 fffff800`b82190ca dxgmms1!VidSchDdiNotifyInterruptWorker+0x15f
ffffd001`9813aa80 fffff800`b8089a7e dxgmms1!VidSchDdiNotifyInterrupt+0x7a
ffffd001`9813aab0 fffff800`b87ae687 dxgkrnl!DxgNotifyInterruptCB+0x6e
ffffd001`9813aae0 ffffe000`9e193040 nvlddmkm+0xe3687
ffffd001`9813aae8 ffffd001`9813abb9 0xffffe000`9e193040
ffffd001`9813aaf0 ffffd001`9813ace0 0xffffd001`9813abb9
ffffd001`9813aaf8 ffffe000`9e2e9000 0xffffd001`9813ace0
ffffd001`9813ab00 fffff800`b87ae617 0xffffe000`9e2e9000
ffffd001`9813ab08 ffffe000`9e2e9000 nvlddmkm+0xe3617
ffffd001`9813ab10 00000000`00000000 0xffffe000`9e2e9000

Given the situation you're in, I don't really blame the Nvidia driver, it's most likely the graphics card or the motherboard.
But given the other bugchecks, I would say the motherboard.
 
Here's the error.

Code: 
{Registry Hive Recovered} Registry hive (file): '\Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD' was corrupted and it has been recovered. Some data might have been lost.

No idea how it got corrupted.
Run sfc /scannow from the elevated command prompt, post the results.

I'm still confident this is your motherboard.
If Gigabyte will allow it, RMA it.
 
It found corrupted files, so i'll post the Log Folder, since I have no idea what I should post.
(I had to upload it into Mediafire: CBS )
 
For what it's worth, I don't think it's worth fixing the logs given the situation your computer is in.
I can get somebody to resolve it, but given that it looks like your motherboard is failing, you'll need a replacement, thus a clean install.
It's up to you though, if you want somebody to try and resolve the errors.
 
From the crashes I have seen, it looks promising that is the cause.
We could test the disk drive to check for any errors if you want to narrow it down even more.

SeaTools for DOS | Seagate
 
I actually have replaced my hard disk recently, since the old one was broken. I used Seatools to test it and it worked fine.
Is there any way to test the Graphics Card?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top