BSOD apparently caused by ntoskrnl.exe

Rekcart · 09 Oct 2015

I am assisting a friend with his computer. He states that he will be using the computer and all is well, then he will get up to go do something, i.e. put his daughter to bed, eat dinner etc. On returning to the computer he finds it off and a message saying there was an error. He didn't give me too many details.

I looked at his error log; it's showing 41 critical errors related to Kernel-Power (EventID 41). That prompted me to get BlueScreenView to look at the .dmp files; it's showing 50 of them from Sep, 10-today. There is clearly a problem, and I feel like it may be the memory, but I am not extremely experienced in analyzing BSOD errors, so I came here.

The specs of the system are as follows:
-Windows Professional 64-bit
-Gigabyte GA-Z97X-UD5H Motherboard
-Intel Core i7-4790k
-32 GB of Corsair Vengeance DDR3-1600 (I remember now he bought 2 16GB(8x2) sets on accident)
-2x WD2003FZEX 2 TB HDD's
-1x Samsung 850 Pro 512GB SSD
-Nvidia Quadro K2200
-EVGA Supernova NEX750G

**axe0** · 09 Oct 2015

Hi Rekcart,

Welcome to the 7forums.

There are multiple causes for the crashes.
The 0x24(NTFS_FILE_SYSTEM) usually points to hard drive problems.
The 0x1A(MEMORY_MANAGEMENT) usually points to memory problems.
It appears there are also problems with the GPU.
Please follow instructions below

Diagnostics Test

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia
Please note the temperatures of the GPU when idle and under load

Diagnostic test

GPU TEST

Run Furmark to test your GPU. Furmark tutorial

Note

Run Furmark for around 30 minutes

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

Please try following just to make sure there are no problems with the system files:

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Graphics driver marked

Code:

STACK_TEXT:  
fffff880`0bb67d50 fffff880`0585b923 : 00000000`00000001 fffff8a0`0421acf0 fffff880`05867400 fffff880`05867410 : dxgkrnl!DoublyLinkedList<DMMVIDEOPRESENTSOURCE>::Clear+0x40
fffff880`0bb67d80 fffff880`0585b838 : 00000000`00000001 fffff8a0`03ecb6a0 fffff880`05867410 fffff880`05867410 : dxgkrnl!DMMVIDPNTARGETMODESET::~DMMVIDPNTARGETMODESET+0xbf
fffff880`0bb67db0 fffff880`05855e34 : 00000000`00000000 00000000`00000001 00000000`4e506456 00000000`00000798 : dxgkrnl!DMMVIDPNSOURCEMODESET::`scalar deleting destructor'+0x14
fffff880`0bb67de0 fffff880`0585f099 : fffff8a0`04eca620 fffff8a0`04fa2130 fffffa80`20cac000 00000000`00000000 : dxgkrnl!ReferenceCounted::Release+0x20
fffff880`0bb67e10 fffff880`0585ef08 : 00000000`00000005 00000000`00000001 00000000`00000000 00000000`00000798 : dxgkrnl!DMMVIDPNSOURCE::~DMMVIDPNSOURCE+0x165
fffff880`0bb67e40 fffff880`0585f4b6 : fffff8a0`04b186b8 fffff8a0`04f9f830 fffffa80`20cac000 00000000`00000000 : dxgkrnl!DMMVIDPNSOURCE::`scalar deleting destructor'+0x14
fffff880`0bb67e70 fffff880`0585f5df : 00000000`00000005 00000000`00000001 fffff8a0`4e506456 00000000`00000798 : dxgkrnl!DoublyLinkedList<DMMVIDPNTARGET>::Clear+0x42
fffff880`0bb67ea0 fffff880`0590ce72 : fffff8a0`04435d60 fffff8a0`04435d60 00000000`00000000 fffffa80`20cac000 : dxgkrnl!DMMVIDPNTARGETSET::`vector deleting destructor'+0x63
fffff880`0bb67ed0 fffff880`0585d4d0 : fffff8a0`fffffdfc 00000000`00000001 00000000`00000000 fffff880`058f121b : dxgkrnl!DMMVIDPN::~DMMVIDPN+0x262
fffff880`0bb67f10 fffff880`05855e34 : 00000000`00000000 fffffa80`ffffddc6 fffff880`0bb68080 fffff880`058e38c3 : dxgkrnl!DMMVIDPN::`vector deleting destructor'+0x14
fffff880`0bb67f40 fffff880`058ebb66 : fffff8a0`034b8160 00000000`00000003 00000000`00000000 00000000`c01e0338 : dxgkrnl!ReferenceCounted::Release+0x20
fffff880`0bb67f70 fffff880`058f27ae : fffff8a0`ffffd9df fffff8a0`034b8160 00000000`00000000 fffffa80`20cac000 : dxgkrnl!VIDPN_MGR::CacheLastClientCommittedVidPnRef+0x7e
fffff880`0bb67fa0 fffff880`0587a282 : 00000000`00000000 00000000`00000000 fffffa80`1a55e010 fffff8a0`00000000 : dxgkrnl!DmmCommitVidPn+0xcee
fffff880`0bb680e0 fffff880`058a7610 : fffff8a0`001f0101 fffff8a0`0b64b400 fffff8a0`0b76a901 fffff8a0`00000000 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546
fffff880`0bb683f0 fffff880`0589187b : fffff8a0`03138740 fffff8a0`00c0d620 00000000`00000000 fffff8a0`0b64b410 : dxgkrnl!CommitVidPn+0x68
fffff880`0bb68490 fffff960`007b682d : fffff900`c00ce020 00000000`00000000 fffff880`0bb68b90 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x166b
fffff880`0bb687e0 fffff900`c00ce020 : 00000000`00000000 fffff880`0bb68b90 00000000`00000000 fffff880`0bb688d8 : cdd+0x682d
fffff880`0bb687e8 00000000`00000000 : fffff880`0bb68b90 00000000`00000000 fffff880`0bb688d8 00000000`00000002 : 0xfffff900`c00ce020