Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random crashes, usually page_fault_in_nonpaged_area


  • Please log in to reply
19 replies to this topic

#1 smr24

smr24

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 10 December 2017 - 05:16 PM

http://speccy.piriform.com/results/LisH0dAiYMMFT4ybZ1kR3lk

 

Hello,

 

I built a new gaming rig a few months ago, and about 2 months in I started getting random BSODs, almost always when the system was idle or not being stressed. This is happening pretty much daily. I've only had it BSOD once while playing a game, and even then it was not a system-intensive one. I've gotten a few different error codes, but by far the most common is "page_fault_in_nonpaged_area". I've tried running WinDbg and all it points to is ntoskrnl.exe. I tried running driver verifier, and initially it pointed to some drivers for utilities that came with my motherboard, but after uninstalling those, it ended up pointing to ntoskrnl.exe again.

 

Windows Memory Diagnostic and memtest both came up clean after running each several times, as did system file checker and chkdsk. 

 

I had my friend at a computer shop reinstall Windows and only a few of the mobo utilities. The system was good for about a week, and is now back to crashing daily. I'm pretty much to the point of having to RMA hardware components now, but maybe there's something we're still missing. 

 

Thanks in advance for the help!

Attached Files


Edited by smr24, 10 December 2017 - 05:17 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 11 December 2017 - 07:02 AM

ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

If the culprit (the offending 3rd party driver) hasn't exited yet, then a BSOD analyst may be able to find traces of it in the reports/dumps.  If the culprit has exited, then the chase is on and further tests/reports will be needed to help identify what actually caused it.

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe


There is only one memory dump in the attached reports.

If using a disk cleaner (such as CCleaner), please stop while we're troubleshooting.

 

Your UEFI/BIOS (version 1.40) dates fromMarch of 2017.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

This device needs to have drivers installed:

 

PCI Simple Communications Controller    PCI\VEN_8086&DEV_A2BA&SUBSYS_7A631462&REV_00\3&11583659&0&B0    The drivers for this device are not installed.

This is most likely the Intel Management Engine (MEI) and the latest, W10 compatible version should be available from the support website of the manufacturer of your motherboard.

 

I would suggest uninstalling Corsair Link.  While there's no direct evidence of it's involvement, there are signs that it could be involved.
If you need the program, you can uninstall it temporarily - and then download and install fresh, W10 compatible version from the Corsair website to see if that helps.

 

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:

SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
USBXpress Development Kit http://www.silabs.com/SUPPORT/Pages/default.aspx
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
 
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
Silicone Labs USBXpress Development Kit http://www.silabs.com/SUPPORT/Pages/default.aspx
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys

LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
Logitech Gaming KMDF HID driver[br]KB or mouse  http://www.logitech.com/en-us/support-downloads/downloads
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
 
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
Logitech Gaming Software driver http://support.logitech.com/en_gb/software/lgs
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
 
 If this does not stop the problem, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html


Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sun Dec 10 16:21:00.626 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-3515-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 4:39:55.923
Probably caused by :memory_corruption
BugCheck 50, {fffff80200000000, 10, fffff8020f36211f, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffff80200000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff8020f36211f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  CorsairLink4.Service.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.40
  BIOS Release Date             03/31/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sun Dec 10 16:21:00.626 2017 (UTC - 5:00)**************************
MpKsl8de32445.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
cpuz144_x64.sys             Fri Oct 13 05:27:26 2017 (59E086FE)
nvlddmkm.sys                Tue Dec  5 14:28:19 2017 (5A26F353)


MpKsl8de32445.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
cpuz144_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 11 December 2017 - 04:46 PM

Thanks for the reply. 

 

There was indeed a newer BIOS version (1.60). I installed that, and I believe I found the drivers you said were missing. I uninstalled and reinstalled Corsair Link as well. As I was researching the other drivers you listed as out of date, the computer crashed again. The dump files are attached. 

 

I noticed that there is still only one minidump folder, and I have not run any kind of disk cleaner. Is there a setting somewhere that I need to change for Windows to not get rid of the old dump files? 

 

Thanks again for your help!

Attached Files



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 12 December 2017 - 08:30 AM

You'll only have one folder for Minidumps - and each will have a different name.
You may also have a MEMORY.dmp in the C:\Windows folder - and this will only be the latest memory dump that was captured (and it's much larger than the Minidumps).

 

Dump file info (I haven't updated this recently, so it may refer to older versions of Windows):

Set your system for Minidumps (much smaller than the MEMORY.DMP file):  http://www.carrona.org/setmini.html
More info on dump file options here: http://support.microsoft.com/kb/254649
 

The attached memory dump is from Mon Dec 11 16:38:36.992 2017 (UTC - 5:00)
Was this before or after you had updated Corsair Link?  From your description I presume it was after.

 

The Silicone Express older drivers are still present.  Any idea what they are for?

I suspect that it's for one of the MSI utilities - such as XFast USB.  If you have that installed, please uninstall it and see if that helps

I'd have to next suggest Driver Verifier to try to figure this out.
Please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 11 16:38:36.992 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121117-3531-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:16:17.766
Probably caused by :memory_corruption
BugCheck 1000007E, {ffffffffc000001d, fffff80128ddf8f0, fffffc0b34109b28, fffffc0b34109370}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80128ddf8f0, The address that the exception occurred at
Arg3: fffffc0b34109b28, Exception Record Address
Arg4: fffffc0b34109370, Context Record Address
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  CorsairLink4.Service.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Dec 11 16:38:36.992 2017 (UTC - 5:00)**************************
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
asmtxhci.sys                Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                Mon Aug 29 04:40:08 2016 (57C3F4E8)
TeeDriverW8x64.sys          Tue Jul 18 10:15:12 2017 (596E17F0)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
cpuz144_x64.sys             Fri Oct 13 05:27:26 2017 (59E086FE)
nvlddmkm.sys                Tue Dec  5 14:28:19 2017 (5A26F353)


http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
cpuz144_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 12 December 2017 - 03:05 PM

Yes, that crash happened after I reinstalled Corsair Link. 

 

I believe SiLib and SiUSBxp are both used by my liquid cooler, so they likely came with Corsair Link. 

 

I ran driver verifier with the instructions you linked to. It crashed immediately, did not boot. Also, before I could compile the dumps and make this post, it crashed again. That dump should be included here. When it restarted, it began installing some Windows updates.

Attached Files


Edited by smr24, 12 December 2017 - 03:07 PM.


#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 13 December 2017 - 01:33 PM

The memory dumps seem to show what is likely to be a hardware problem.

There is a slim possibility that the OS is to blame - but I think we can rule out 3rd party problems at this point.

 

2 options from here:

1)  Run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Then, if they ALL pass, try this procedure to locate the problem device:  http://www.carrona.org/strpdown.html

2)  or, perform a clean install:

 

A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
- The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
- Windows is fully updated after it's installed.  That's ALL updates - none excepted.
- NO 3rd party software is installed.
- There are no errors in Device Manager (if you find any, post back for suggestions).

This will wipe everything off of the computer, so it's advisable to backup your stuff first.
Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them :(
Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

The point of doing this (the clean install) is to:
- rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
- rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
- so, if the problem continues, it must be a hardware problem.

OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Tue Dec 12 14:53:58.846 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121217-3718-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 0:31:39.618
Probably caused by :win32kfull.sys ( win32kfull!DestroyThreadsHotKeys+b0 )
BugCheck 50, {ffffc6e600000000, 10, ffffc6e6f10ce0a0, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffc6e600000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: ffffc6e6f10ce0a0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  RuntimeBroker.
FAILURE_BUCKET_ID: OLD_IMAGE_win32kfull.sys
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 12 14:19:18.164 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121217-3328-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 0:00:03.848
Probably caused by :ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+df )
BugCheck C4, {2004, ffffa48aafda3d98, fffff801a87a01f0, ffff830c2443efc8}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002004, Code Integrity Issue: The image contains a section that is not page aligned.
Arg2: ffffa48aafda3d98, The image file name (Unicode string).
Arg3: fffff801a87a01f0, The address of the section header.
Arg4: ffff830c2443efc8, The section name (UTF-8 encoded string).
BUGCHECK_STR:  0xc4_2004
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2004_nt!VerifierBugCheckIfAppropriate
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 16:38:36.992 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121117-3531-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:16:17.766
Probably caused by :memory_corruption
BugCheck 1000007E, {ffffffffc000001d, fffff80128ddf8f0, fffffc0b34109b28, fffffc0b34109370}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80128ddf8f0, The address that the exception occurred at
Arg3: fffffc0b34109b28, Exception Record Address
Arg4: fffffc0b34109370, Context Record Address
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  CorsairLink4.Service.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Dec 12 14:53:58.846 2017 (UTC - 5:00)**************************
MpKslf7963c3d.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
MpKsld87d6eff.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
asmtxhci.sys                Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                Mon Aug 29 04:40:08 2016 (57C3F4E8)
TeeDriverW8x64.sys          Tue Jul 18 10:15:12 2017 (596E17F0)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
cpuz144_x64.sys             Fri Oct 13 05:27:26 2017 (59E086FE)
nvlddmkm.sys                Tue Dec  5 14:28:19 2017 (5A26F353)


MpKslf7963c3d.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKsld87d6eff.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
cpuz144_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 16 December 2017 - 12:47 PM

I'm inclined to believe it's not a Windows problem since I did a clean reinstall recently, but who knows. I ran a bunch of those diagnostics, nothing showed up. Prime95 ran for almost 14 hours, memtest for about 4 this time (but over 12 in the past), and the HDD ones all passed. Is there anything we can go by in terms of which component might be causing problems? I'm a little worried that it's not the RAM since I've tried running the computer with 1 stick at a time and it still crashed. 

 

Also, had a BSOD that I haven't seen before this morning, that should be attached. 

 

Windows has once again deleted the rest of my minidumps. Maybe it's running a built-in cleaning program automatically?

Attached Files



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 16 December 2017 - 03:04 PM

Windows doesn't automatically delete minidumps.  Something has to be set to delete them.

The MEMORY.dmp file in C:\WIndows is overwritten each time a dump is generated - but that's a full dump, not a minidump

 

If you did a clean install of WIndows - then it's most likely a hardware problem

See the quote below for a more detailed description:

 

A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
- The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
- Windows is fully updated after it's installed.  That's ALL updates - none excepted.
- NO 3rd party software is installed.
- There are no errors in Device Manager (if you find any, post back for suggestions).

This will wipe everything off of the computer, so it's advisable to backup your stuff first.
Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them :(
Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

The point of doing this (the clean install) is to:
- rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
- rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
- so, if the problem continues, it must be a hardware problem.

OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

 

If ALL of the diagnostics have passed (you didn't mention the video tests or the CPU test), then try this procedure to help isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

BUT, there's still this stuff to try, as hardware type problems can also be caused by compatibility issues or low-level driver problems..................

 

Your UEFI/BIOS (version 1.60) dates from late November of 2017.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

NTIOLib_X64.sys often causes BSOD's - but this is the first time I recall seeing a version dated from 2017

Unfortunately, the dump file doesn't show which programs use it (a lot of the MSI Control Center applications use it.
I'd suggest searching your system for NTIOLib_X64.sys and seeing where it's installed.

DO NOT DELETE the driver - it may cause problems booting.  If you wish, you can uninstall those programs associated with the location that you find the driver in.

 

If the steps above don't fix things, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sat Dec 16 12:35:49.974 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121617-3578-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 8:16:11.746
Probably caused by :ntkrnlmp.exe ( nt!NtSetSystemPowerState+b90 )
BugCheck C000021A, {ffffae09a9a87570, ffffffffc0000005, 7ffd6368e120, fafe87da40}
BugCheck Info: WINLOGON_FATAL_ERROR (c000021a)
Arguments:
Arg1: ffffae09a9a87570, String that identifies the problem.
Arg2: ffffffffc0000005, Error Code.
Arg3: 00007ffd6368e120
Arg4: 000000fafe87da40
Arg2: ffffffffc0000005, Error Code.
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xc000021a_c0000005_csrss.exe_Terminated
FAILURE_BUCKET_ID: 0xc000021a_c0000005_csrss.exe_Terminated_nt!NtSetSystemPowerState
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sat Dec 16 12:35:49.974 2017 (UTC - 5:00)**************************
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
asmtxhci.sys                Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                Mon Aug 29 04:40:08 2016 (57C3F4E8)
NTIOLib_X64.sys             Sun Jul  9 21:53:21 2017 (5962DE11)
TeeDriverW8x64.sys          Tue Jul 18 10:15:12 2017 (596E17F0)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
nvlddmkm.sys                Tue Dec  5 14:28:19 2017 (5A26F353)


http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 19 December 2017 - 11:46 PM

My mistake, I did also try Furmark and the Intel CPU diagnostic, both ran with no problems. I was a little surprised that it ran all of these tests without crashing at all, given how long they take. Recently it seems like it will only last a few hours turned on before it crashes, much less the 12+ it took to run some of these tests in Windows. Is it possible that whatever is causing these BSODs is more likely to occur while the system is under low stress? 

 

As far as hardware, it doesn't seem (to me) like the RAM would be the problem since it passes many hours of memtest, and I also tried running the system in the past with one stick at a time and still had these BSODs. I could try running the system without the graphics card, using the integrated Intel graphics. These tests are frustrating when you don't have a direct, known way to trigger the error! 

 

When I reinstalled Windows a few weeks ago, the system ran fine with no BSODs for about two weeks before they started happening again. I had not, to that point, reinstalled any of the MSI utilities beyond the basic motherboard controllers, and I'm pretty sure I did not install any other driver-related software around that time. I'm just curious if you have any insight into why the errors would clear up like that, then return seemingly on their own. 



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 20 December 2017 - 08:48 AM

Have you done the Other Video/Video 2 tests that I also suggested?

I've found (over the last year or so), that video card errors don't always show up with Furmark.

As to why they would clear up and suddenly return - lot's of guesses but no firm causes.

First, we must presume that this is most likely a hardware problem - simply because you did a clean install (without any problems that you mentioned) and didn't install any 3rd party software.

If that's the case, then either:

- some 3rd party software was stressing the faulty hardware component in ways that Windows didn't.

- that the system wasn't doing anything to stress the faulty hardware component for the first 2 weeks.

 

I would try running just the integrated graphics for a long while - as you know the system can go for weeks without a problem.
Unfortunately, there's just no way to speed this process up on the forums.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 28 December 2017 - 08:42 PM

Ok, the system had gone for a couple days without crashing until today. I got the same page_fault BSOD as before. I decided to try running the system without the graphics card since that's pretty much the only hardware change I can make without sending parts off to be replaced. Running on integrated graphics, it crashed after about 45 minutes. That dump is attached. I'm still inclined to believe the RAM is not the problem since I tried the two sticks separately, one at a time, and got BSODs both times. Hopefully this dump tells us something. Otherwise, any ideas of what other components could be causing problems? 

 

The dump from the first crash today is attached as SysnativeFileCollectionApp2.zip. I believe this dump was erased at some point between the two crashes, still haven't figured out what's deleting them. 

Attached Files



#12 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 31 December 2017 - 10:30 AM

Did you try the RAM sticks in both slots individually?
stick 1 in slot 1

stick 1 in slot 2

etc?

 

Dunno about the missing dumps.  I was involved in the early development of the Sysnative app, but haven't contributed/tested it for several years.

Maybe ask member jcgriff2?  He's the owner/primary developer.

 

I suggest removing the Intel Extreme Tuning program as I have seen problems with it in other systems on occasion.  It's driver is iocbios2.sys

I also suggest uninstalling the MSI FastBoot program - as the NTIOLib_x64.sys driver has been known to cause BSOD's on other systems.

 

 

2 very different memory dumps, but still possible that it's caused by software.

The point here is if you can't identify a driver from a Driver Verifier crash (either by seeing it named on the BSOD or by capturing a dump file) then we're left with trying the procedure to rule out hardware:My suggested way to diagnose a hardware problem (3 steps):

1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.
    FYI - These are the tests and what we usually see for the reports:

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


2)  If all the tests pass, then try to perform a clean install of Windows:

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [:(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Thu Dec 28 20:31:40.145 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122817-2687-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 0:42:12.907
Probably caused by :memory_corruption
BugCheck A, {ffffffffffffff88, 2, 0, fffff8020852a15f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffffffffffff88, 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: fffff8020852a15f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  WinStore.App.e
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 28 17:15:27.105 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122817-4265-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 10:08:48.866
Probably caused by :ntkrnlmp.exe ( nt!fputwc_nolock+2b )
BugCheck 50, {fffff80000000000, 10, fffff800cbfca09f, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffff80000000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff800cbfca09f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  CorsairLink4.S
FAILURE_BUCKET_ID: AV_INVALID_nt!fputwc_nolock
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Thu Dec 28 20:31:40.145 2017 (UTC - 5:00)**************************
MpKsl2070e1e5.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
asmtxhci.sys                Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                Mon Aug 29 04:40:08 2016 (57C3F4E8)
NTIOLib_X64.sys             Wed Mar 29 03:26:33 2017 (58DB61A9)
TeeDriverW8x64.sys          Tue Jul 18 10:15:12 2017 (596E17F0)
IntcDAud.sys                Mon Sep 11 08:11:17 2017 (59B67D65)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
cpuz144_x64.sys             Fri Oct 13 05:27:26 2017 (59E086FE)
igdkmd64.sys                Tue Oct 17 21:39:02 2017 (59E6B0B6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 28 17:15:27.105 2017 (UTC - 5:00)**************************
MpKslabe5cc05.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvlddmkm.sys                Fri Dec 15 17:17:15 2017 (5A3449EB)


MpKsl2070e1e5.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
cpuz144_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
MpKslabe5cc05.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#13 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 08 January 2018 - 10:06 PM

Sorry about the delay, I've been out of town a lot and haven't had time for troubleshooting.

 

I have tried the RAM sticks as a pair in slots A1/B1 and A2/B2, switched the sticks to the opposite slot each time, as well as run one at a time in slot A2. This mobo says to use slots A2/B2 if using two sticks, which is why I went with just A2 for the individual sticks. 

 

As I said, I haven't had time to try anything new, but I did get a BSOD I've never seen before (attached). This popped up shortly after I was in the other room and heard the computer restart from idle, followed by Windows informing me of updates that required a restart. After restarting for the updates, I got these two crashes within 5 minutes. Strangely, I am now unable to open Firefox. I can see the program in the Task Manager using some % of the CPU, but it never actually opens. I also tried doing a system restore to about a week ago, but it was unsuccessful. 

Attached Files



#14 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:05 PM

Posted 10 January 2018 - 01:03 PM

Sometimes Firefox will hang like that.  Kill (end) the processes in Task Manager, then try to launch Firefox again.

Worst case, uninstall it - then download and install a fresh copy.

 

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:
 
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
USBXpress Development Kit http://www.silabs.com/SUPPORT/Pages/default.aspx
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
 
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
Silicone Labs USBXpress Development Kit http://www.silabs.com/SUPPORT/Pages/default.aspx
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
 

One of the two memory dumps here states that there is a hardware problem.

Have you finished the hardware diagnostics that I suggested?  If so, what were the results.

The next 2 steps are needed to verify that there is a hardware problem, and then to isolate the defective component(s).

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan  8 21:05:19.036 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010818-4015-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 0:03:36.803
Probably caused by :memory_corruption
BugCheck A, {fffff80300000000, 2, 8, fffff803582be0dc}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: fffff80300000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, 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: fffff803582be0dc, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  8 21:00:33.804 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010818-4203-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
System Uptime:0 days 0:53:56.570
Probably caused by :hardware ( nt!wcschr+8 )
BugCheck 1000007E, {ffffffff80000003, fffff8009416e088, ffffa70297f16f68, ffffa70297f167b0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8009416e088, The address that the exception occurred at
Arg3: ffffa70297f16f68, Exception Record Address
Arg4: ffffa70297f167b0, Context Record Address
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: IP_MISALIGNED
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  1.60
  BIOS Release Date             11/20/2017
  Manufacturer                  MSI
  Product Name                  MS-7A63
  Baseboard Product             Z270 GAMING PRO CARBON (MS-7A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Jan  8 21:05:19.036 2018 (UTC - 5:00)**************************
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
ICCWDT.sys                  Sun Mar 13 07:44:25 2016 (56E55299)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
iocbios2.sys                Fri Jul 15 00:39:19 2016 (578868F7)
asmtxhci.sys                Mon Aug 29 04:40:00 2016 (57C3F4E0)
asmthub3.sys                Mon Aug 29 04:40:08 2016 (57C3F4E8)
NTIOLib_X64.sys             Wed Mar 29 03:26:33 2017 (58DB61A9)
TeeDriverW8x64.sys          Tue Jul 18 10:15:12 2017 (596E17F0)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
cpuz144_x64.sys             Fri Oct 13 05:27:26 2017 (59E086FE)
RTKVHD64.sys                Tue Nov 14 06:05:07 2017 (5A0ACDE3)
nvlddmkm.sys                Fri Dec 15 17:17:15 2017 (5A3449EB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  8 21:00:33.804 2018 (UTC - 5:00)**************************
hvsocket.sys                Thu Oct 27 00:00:01 1994 (2EAF25C1)
hiber_storport.sys          Tue Jun 28 22:27:39 2011 (4E0A8D9B)


http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
cpuz144_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
hvsocket.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#15 smr24

smr24
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 25 January 2018 - 07:31 AM

Ok, as one last attempt before really getting into hardware stuff, I did one more clean install of Windows. The only 3rd party drivers installed are Corsair Link and nVidia graphics, maybe some basic Logitech ones for my keyboard and mouse that install automatically. I wanted to try this one last time because the computer was fine for about two week the first time I did this. 

 

Naturally, it made it about 3 days this time. The system did not actually display the blue screen, but it did freeze up for a few seconds before restarting. I checked the dump files, and sure enough, something was there, so that file is attached. 

 

At this point, my friend has suggested replacing the RAM and possibly the motherboard. We think the graphics card is OK since the crashes still happened with it removed, and he said CPUs are almost never the problem. Hopefully this dump file gives some hints, otherwise that's probably what we're going forward with. Thanks again for all your help! 

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users