BSOD on ntoskrnl.exe and some other addresses

[DwzLT]

Hi,

So I'm having the BSOD issue when freshly starting the PC. It happens usually 2-10 minutes after booting the system when it has been turned off for the night.

Here are the last four logs:

==================================================
Dump File : 102716-14601-01.dmp
Crash Time : 2016.10.27 11:51:18
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff9d0`0ac93e00
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030939fd
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23564 (win7sp1_ldr.160930-0600)
Processor : x64
Crash Address : ntoskrnl.exe+6f440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102716-14601-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7585
Dump File Size : 275.920
Dump File Time : 2016.10.27 11:52:19
==================================================


==================================================
Dump File : 102216-15147-01.dmp
Crash Time : 2016.10.22 12:07:34
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000001
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23564 (win7sp1_ldr.160930-0600)
Processor : x64
Crash Address : ntoskrnl.exe+6f440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102216-15147-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266.320
Dump File Time : 2016.10.22 12:08:47
==================================================



==================================================
Dump File : 102116-14804-01.dmp
Crash Time : 2016.10.21 15:09:19
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`0c438288
Parameter 3 : fffff880`0c437ae0
Parameter 4 : fffffa80`0b7f0210
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+4211
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+6f440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102116-14804-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275.920
Dump File Time : 2016.10.21 15:11:11
==================================================



==================================================
Dump File : 101016-15085-01.dmp
Crash Time : 2016.10.10 10:09:13
Bug Check String : ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code : 0x000000fc
Parameter 1 : fffff880`0c7311c0
Parameter 2 : 80000002`8c263963
Parameter 3 : fffff880`0c730fe0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70180
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23564 (win7sp1_ldr.160930-0600)
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101016-15085-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275.920
Dump File Time : 2016.10.10 10:10:11
==================================================



I have run memtest (several instances of it on 2047 value and then less) and came back with 0 erros

Any ideas?

 

[HeuristicToaster]

IRQL_NOT_LESS_OR_EQUAL tends to shout memory, especial in conjunction with ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY. Both those errors are caused by drivers or system errors just as easily though, so since you're ruled out memory I'd suggest running sfc to rule out the OS. Driver wise, the built in Driver Verifier can be used to analyse them for problems whilst it's running, and it's always worth a quick check in eventvwr in case there's something obvious showing up there.

I take it from the timestamps that these BSODs are rather infrequent? 10th, 21st, 22nd, 27th - are these times that you (re)boot the computer? If so, how is the computer left inbetween (running, suspended, hibernated etc)? It strikes me as being quite an infrequent / elusive problem, in which case if it is bad memory it might be worth letting memtest run for 3-4 passes. I've had BSODs from dodgy RAM (maybe once or twice a fortnight) that didn't fail memtest until it reached 6 passes after running over the weekend, which isn't to say that it's necessary to run it for that long but if you've got the time it can't hurt

 

[DwzLT]

The BSODs happen infrequemtly, yes, but all of them happen when turning on the pc while it was shut down (electricity shut off) for long periods of time (12-15 hours etc.) For the most part pc is only on for the day and shut down for the night. I can rule out power surges as I got the safety for that equipped.

sfc returned with no noticeable errors. I'll try doing more passes on memtest.

The thing that baffles me is that the bsod started all of a sudden about a month ago, I know for a fact I have not installed any new software in the past month (I would have thought that to be part of the problem). That big gap from 10th to 21st was after I updated the windows updates (they probably didn't do anything but a mate suggested doing that) and it didn't bsod for that period at all but it started happening again more frequently since the 21st.

Either way, Any other suggestions on possible troubleshooting would be welcome.

And thank you for your suggestions HeuristicToaster