Persistent BSOD ntoskrnl.exe

Hello-
I had been doing some troubleshooting on this issue over at tomshardware and the admin sent me here... I keep getting random BSODs pointing to ntoskrnl.exe at odd times - normal working conditions and even at idle. The admin at toms seemed to think it was software related and here's that thread. DM log is also attached to this post. Please help.Attachment 197193
cheers-
r

Hello Ryan and welcome to TenForums

Here is a breakdown of all the BSOD events:

Code:

2018-07-11T07:00:07.075		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffffb007f8cc2040, 0xffffe90e81d6b900). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 85fd410f-1dfc-431b-8936-7031c90256cf.
2018-07-11T13:46:45.923		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffa884c173a820, 0xffffa884c173a778, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 81c4cc39-283b-4d2c-8a89-dfbed033c24e.
2018-07-11T14:11:51.351		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8054185581f, 0xffff85008e483740, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 49039359-fb45-45cf-b4dc-0bf24ac827a0.
2018-07-12T13:07:18.262		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000f7 (0x00001317f3c9a37b, 0x00001317f3c9a36b, 0xffffece80c365c94, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 51b666a1-3992-45ba-9980-740de7b4b632.
2018-07-14T10:51:17.226		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000001, 0x0000000000000002, 0x0000000000000000, 0xfffff801e02cf87c). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6ca5c32d-2ce0-4762-b55c-3bfd9f9423a5.
2018-07-15T05:17:14.820		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000000, 0x000000000000000e, 0x0000000000000001, 0xfffff80e198ba4d6). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3c20398f-71b8-4e84-8af2-1f22fd6bcb26.
2018-07-15T06:11:27.047		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9c39eb7e-1dc1-415d-ab2a-5b115f3c5fe3.
2018-07-15T06:11:35.704		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff8002c0c1acb). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6332a3f3-b941-4c30-825f-7d2d87897dfe.
2018-07-17T16:35:45.886		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000018 (0xffffcd0aae81b2e0, 0xffffcd0ac750b9e0, 0x0000000000000001, 0xffffcd0ac750b9b8). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8a377a29-a3a1-4063-be0e-7ad6474af394.
2018-07-18T05:52:22.636		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000f7 (0x000072dc629d7bbd, 0x000072dc629d7bad, 0xffff8d239d628452, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0a8a3c5e-9a1f-4137-95ee-2a40b641f8d5.
2018-07-19T23:36:44.817		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000f7 (0x000061206da2a4d4, 0x000061206da2a4c4, 0xffff9edf925d5b3b, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e8f7f6e5-4e5e-4d4c-a2ea-58e2a43e1d44.
2018-07-23T13:32:21.710		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffff3085746f7d0, 0xfffff3085746f728, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8667bc70-4000-494a-b14c-14eb618a16d9.
2018-07-25T00:56:34.241		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000018 (0x0000000000000000, 0xffffc9016424f8e0, 0x0000000000000002, 0xffffc9015b540d7f). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6b12de65-ca48-4679-8413-fd419b825eba.
2018-07-25T08:35:31.321		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000018 (0xffffe48b625ff8a0, 0xffffe48b8d4fcdb0, 0x0000000000000001, 0x0000000000080027). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c0ee5bb3-c2cb-4291-a1e0-0bf8fa904c1c.

With this many different events but no crash dumps to analyse it is difficult to know if it is software or hardware. Please try and repost a new set of logfiles after you get a BSOD so that we can get the mini-dump files. All your existing ones seem to have been deleted, make sure CCleaner is not set to delete memory dump files!

Hey Phil thanks for the warm welcome and response! I actually do have some recent mini dump files that can be found here. Do they help?

Other than noting that the process running for the two 0x18 stop codes was Cinema 4D in both cases there is not a lot I can deduce from the crash dumps. The 0x139 stop code crash dump does not reveal much but the Cinema 4D process was not running at that time.

Looking at your error reports (WERs) I can see that the Nvidea GeForce experience is crashing a lot. It might be worth uninstalling all your Nvidea graphics related files and then just installing the latest driver.

The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

If you are concerned about hardware vs software just run your system in safe mode for a day or two. If you crash in safe mode you can be fairly sure it is a hardware problem.

Will do on display drivers. I think I'll also run MemTest overnight as well to ensure my memory isn't corrupt. Thank you Phil.

RyanTScott said:

Will do on display drivers. I think I'll also run MemTest overnight as well to ensure my memory isn't corrupt. Thank you Phil.

With your 128GB of memory it will take many days to complete 8 passes of Memtest86+ which is the one we recommend. If you can run with less memory I would do it in stages just checking your RAM in pairs.

Diagnostic Test

 RAM TEST

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

   Note

MemTest86+ needs to be run for at least 8 complete 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.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.

Ok understood. I'm not at a place where I can do that at the moment because of work... Do you feel MemTest is advisable?

RyanTScott said:

Ok understood. I'm not at a place where I can do that at the moment because of work... Do you feel MemTest is advisable?

Yes it is, some of your other stop codes are sometimes caused by memory failure. My feeling is that you may have multiple causes for this range of stop codes - most are likely to be drivers but possibly some are related to hardware.

Ok understood. Regarding your instructions for MemTest, will it take less time to test the entire 128gb in pairs vs testing the entire 128gb all at once?

RyanTScott said:

Ok understood. Regarding your instructions for MemTest, will it take less time to test the entire 128gb in pairs vs testing the entire 128gb all at once?

No it won't take less time but you have to complete the 8 passes in one go and you are effectively locked out of your PC for all that time. Doing it in stages does mean you can run the PC normally in between if you need to get other things done on it.