Windows 8.1 BSODS

Madoperator · Oct 15, 2014

I'm having some issues with BSODs randomly happening on my pc. According to WhoCrashed ntoskrnl.exe and ntkrnlmp.exe are the culprits, but they're system files.

Code:

[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 14-10-2014 23:19:33 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\101514-7062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x153CA0) 
Bugcheck code: 0xA (0xFFFFFDC3BF144C30, 0x2, 0x0, 0xFFFFF802E0EF7BFC)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 14-10-2014 23:19:33 GMT your computer crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xA (0xFFFFFDC3BF144C30, 0x2, 0x0, 0xFFFFF802E0EF7BFC)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/COLOR][/SIZE][/FONT]

I've ran a overnight test with memtest86, no errors. Reinstalled drivers for my motherboard and gpu but that also has not helped. I've attached logs, if anyone can help me out I would really appreciate it!

Edit: I see that all of my minidump logs are attached. The last 2 are the ones that I'm talking about. Some of the rest are crashes due to me trying out some overclocks. I have already tried disabling my overclock but the crashes persisted, so I keep it on for now.

Edit2: I got another crash this time while playing fifa 15, and it's a new error message. PFN LIST CORRUPT. Haven't seen this one before, but i'm uploading the logs for this crash also.

blueelvis · Oct 16, 2014

Hi Madoperator & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

**************************Thu Oct 16 03:06:20.235 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101514-12906-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 22:16:13.910
 
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
 
Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
 
BugCheck 4E, {99, 1d1e5e, 2, 40000100001a15d}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
 
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001d1e5e, page frame number
Arg3: 0000000000000002, current page state
Arg4: 040000100001a15d, 0
BUGCHECK_STR:  0x4E_99
 
PROCESS_NAME:  MsMpEng.exe
 
FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount
 
CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
 
MaxSpeed:     3400
 
CurrentSpeed: 3400
 
  BIOS Version                  V1.8
 
  BIOS Release Date             12/03/2013
 
  Manufacturer                  MSI
 
  Product Name                  MS-7845
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 15 04:49:33.484 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101514-7062-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 3:02:24.158
 
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+3fc )
 
BugCheck A, {fffffdc3bf144c30, 2, 0, fffff802e0ef7bfc}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
 
Arguments: 
Arg1: fffffdc3bf144c30, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802e0ef7bfc, address which referenced memory
BUGCHECK_STR:  AV
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  AV_nt!MiInsertPageInFreeOrZeroedList
 
CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
 
MaxSpeed:     3400
 
CurrentSpeed: 3400
 
  BIOS Version                  V1.8
 
  BIOS Release Date             12/03/2013
 
  Manufacturer                  MSI
 
  Product Name                  MS-7845
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Below is a list of 3rd party drivers present on your system :-

Code:

**************************Thu Oct 16 03:06:20.235 2014 (UTC + 5:30)**************************
LUMDriver.sys               Fri Feb 16 18:44:48 2007 (45D5AE48)
MBfilt64.sys                Fri Jul 31 09:10:32 2009 (4A7267B0)
LGBusEnum.sys               Tue Nov 24 07:06:48 2009 (4B0B38B0)
LGVirHid.sys                Tue Nov 24 07:06:48 2009 (4B0B38B0)
tapoas.sys                  Mon Jul 12 06:01:59 2010 (4C3A627F)
[COLOR=#FF0000][U][B]NTIOLib_X64.sys             Wed Oct 20 12:15:49 2010 (4CBE901D)
[/B][/U][/COLOR]vfilter.sys                 Fri Dec 17 11:12:25 2010 (4D0AF841)
ISCTD64.sys                 Wed Nov 28 01:22:34 2012 (50B51A02)
RTCore64.sys                Mon Mar 11 11:02:06 2013 (513D6C56)
INETMON.sys                 Thu Mar 14 02:41:58 2013 (5140EB9E)
LGSHidFilt.Sys              Thu May 30 20:46:33 2013 (51A76D51)
imsevent.sys                Wed Jul  3 05:29:37 2013 (51D36969)
ikbevent.sys                Wed Jul  3 05:30:06 2013 (51D36986)
iaStorA.sys                 Fri Aug  2 07:09:52 2013 (51FB0DE8)
dump_iaStorA.sys            Fri Aug  2 07:09:52 2013 (51FB0DE8)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
BthHfAud.sys                Thu Aug 22 17:08:26 2013 (5215F832)
tap0901.sys                 Thu Aug 22 18:10:01 2013 (521606A1)
btfilter.sys                Wed Sep 18 14:12:54 2013 (5239678E)
asstor64.sys                Mon Jan 27 15:00:34 2014 (52E6273A)
xusb22.sys                  Tue Mar 18 13:48:41 2014 (53280161)
e22w8x64.sys                Wed Mar 26 21:28:37 2014 (5332F92D)
bwcW8x64.sys                Thu Apr 10 21:10:24 2014 (5346BB68)
TeeDriverx64.sys            Sat May 10 02:37:35 2014 (536D4397)
iwdbus.sys                  Wed Jun 18 03:24:22 2014 (53A0B90E)
RTKVHD64.sys                Tue Jul 15 16:23:15 2014 (53C5081B)
igdkmd64.sys                Tue Aug  5 21:17:18 2014 (53E0FC86)
nvvad64v.sys                Thu Sep  4 22:40:48 2014 (54089D18)
nvlddmkm.sys                Fri Sep 19 09:19:22 2014 (541BA7C2)
NvStreamKms.sys             Fri Oct  3 07:09:09 2014 (542DFE3D)

Madoperator · Oct 16, 2014

Ok, how would I delete NTIOLib_X64.sys? And deleting all MSI software from my pc? Even MSI Command Center?

Edit: You were right about my RAM timings being wrong, they were completely messed up. I've activated the XMP profile through my BIOS. If the BSODs persist I'm going to try each RAM stick seperately.

blueelvis · Oct 17, 2014

Madoperator said:
Ok, how would I delete NTIOLib_X64.sys? And deleting all MSI software from my pc? Even MSI Command Center?

Edit: You were right about my RAM timings being wrong, they were completely messed up. I've activated the XMP profile through my BIOS. If the BSODs persist I'm going to try each RAM stick seperately.

The driver file is generally accompanies the MSI Live Update 5 or MSI Afterburner. I would suggest you to uninstall these software and then do a manual file search for the driver throughout your system to make sure that it has been deleted.

I don't think that you would be required to test the RAM individually if it has not been damaged. Just reset back to stock settings and let me know how it goes ^_^

Windows 8.1 BSODS

Madoperator

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Madoperator

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One