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

System Service Exception ntoskrtnl.exe


  • Please log in to reply
14 replies to this topic

#1 apelle93

apelle93

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 30 December 2016 - 11:46 PM

Hello all,

 

I've been attempting to diagnose these blue screen issues on a friends build without much luck. I have been able to correct some of the issues at hand (or so I believe), but I can't seem to put the final nail in the coffin with these issues. I have run memtest already and was given a clean bill of health after letting it go over night. there is no O.C. on the computer (unless it somehow magically OCed itself) and memory timings are set by xmp. I have run the collection tool as required by the form so please see attached.

 

I understand we have an upcoming holiday and the last thing anyone wants to do is solve a BSoD issue on their spare time, So any help is greatly appreciated.

 

 

 

Thanks in advance,

 

apelle93

 

 

Edit: system specs

 

core i7 6700 (non K version)

16gb corsair vengeance ram 2133

Asus gtx1060 6gb strix

MSI z170m Mortar motherboard

250gb Samsung 850 EVO SSD

2tb Western Digital Black HDD

corsair rmx550w PSU

Windows 10 Home 64bit

Attached Files


Edited by apelle93, 30 December 2016 - 11:56 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:35 AM

Posted 01 January 2017 - 09:43 AM

FYI - Intel can "magicall"y overclock it's processors (I think it's for i5 and i7, but there may be more).  It's a program known as TurboBoost - caused quite a few questions/problems until we figured out what it was :9)

If it's overclocked, it'll show up in the dump files and we'll let you know.

 

Your UEFI/BIOS (version A.70) dates from 2016.  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).

Only 5 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
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.

Out of 46 memory dumps there were 10 different BSOD  (aka STOP or BugCheck) error codes (1 of which directly blames hardware).  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results

 

If all of the diagnostics pass and the BSOD's continue after doing the stuff listed above, then 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:
**************************Fri Dec 30 22:22:11.283 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\123016-3953-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 3:41:53.265
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 1000007E, {ffffffffc0000005, fffff80124e88bfc, ffffa8004c1ae0a8, ffffa8004c1ad8d0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80124e88bfc, The address that the exception occurred at
Arg3: ffffa8004c1ae0a8, Exception Record Address
Arg4: ffffa8004c1ad8d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.70
  BIOS Release Date             09/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 29 23:30:46.380 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122916-4031-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:1 days 4:13:32.062
Probably caused by :memory_corruption ( nt!MiFindEmptyAddressRangeDownTree+b6 )
BugCheck 3B, {c0000005, fffff80107ebcf22, ffff96007d555b80, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80107ebcf22, Address of the instruction which caused the bugcheck
Arg3: ffff96007d555b80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: 0x3B_nt!MiFindEmptyAddressRangeDownTree
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.70
  BIOS Release Date             09/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 28 18:19:53.978 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122816-4000-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 0:16:40.656
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  ZEROED_STACK_0x133
PROCESS_NAME:  VSSVC.exe
FAILURE_BUCKET_ID: ZEROED_STACK_0x133
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.70
  BIOS Release Date             09/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



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:

**************************Fri Dec 30 22:22:11.283 2016 (UTC - 5:00)**************************
rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
rt640x64.sys                Fri Apr 22 02:46:44 2016 (5719C8D4)
TeeDriverW8x64.sys          Wed Jul 13 12:52:17 2016 (578671C1)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
iaStorA.sys                 Tue Sep 13 10:45:46 2016 (57D8111A)
MBAMChameleon.sys           Sat Nov 19 14:13:08 2016 (5830A444)
RTKVHD64.sys                Tue Nov 29 08:12:39 2016 (583D7EC7)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 29 23:30:46.380 2016 (UTC - 5:00)**************************
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 27 23:38:14.342 2016 (UTC - 5:00)**************************
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 27 00:25:27.257 2016 (UTC - 5:00)**************************
cpuz137_x64.sys             Mon Feb 17 09:22:16 2014 (53021B18)
aswKbd.sys                  Thu Aug 18 10:12:06 2016 (57B5C236)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 25 18:57:37.530 2016 (UTC - 5:00)**************************
NTIOLib_X64.sys             Mon Nov 26 05:11:53 2012 (50B34069)
IOMap64.sys                 Wed Oct 22 20:52:12 2014 (5448513C)
iaLPSS2_I2C.sys             Mon May  4 08:41:19 2015 (554768EF)
iaLPSS2_UART2.sys           Mon May  4 08:41:32 2015 (554768FC)
iaLPSS2_GPIO2.sys           Mon May  4 08:41:36 2015 (55476900)
rzudd.sys                   Tue Aug 11 07:13:50 2015 (55C9D8EE)
NTIOLib_X64.sys             Tue Apr 12 03:04:16 2016 (570C9DF0)
NTIOLib_X64.sys             Wed Sep  7 22:55:34 2016 (57D0D326)
mbam.sys                    Wed Sep 28 11:45:44 2016 (57EBE5A8)
farflt.sys                  Wed Nov  2 10:29:12 2016 (5819F838)
MBAMSwissArmy.sys           Wed Nov  9 09:21:05 2016 (582330D1)
mwac.sys                    Thu Nov 17 20:02:05 2016 (582E530D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 17 13:11:47.954 2016 (UTC - 5:00)**************************
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Thu Dec  1 11:37:27 2016 (584051C7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 17 09:54:45.704 2016 (UTC - 5:00)**************************
aswHwid.sys                 Thu Aug 18 10:12:04 2016 (57B5C234)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  3 23:30:47.119 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Thu Nov 24 14:04:44 2016 (583739CC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov 26 19:43:28.358 2016 (UTC - 5:00)**************************
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvlddmkm.sys                Wed Nov 16 19:26:04 2016 (582CF91C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov 19 18:20:44.530 2016 (UTC - 5:00)**************************
hiber_storport.sys          Fri Jul 15 22:21:57 2016 (57899A45)
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  5 09:36:44.538 2016 (UTC - 5:00)**************************
RTKVHD64.sys                Tue Aug 16 08:14:34 2016 (57B303AA)


http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.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=cpuz137_x64.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
iaLPSS2_I2C.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.
iaLPSS2_UART2.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=iaLPSS2_GPIO2.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
farflt.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=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.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 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 01 January 2017 - 12:44 PM

You know what, I've never really thought of turbo boost as overclocking but that does make sense. As for diagnostic testing, I've already run memtest86 overnight and was given a clean bill of health. GPU wise ran fur mark for 4 hours or so without issue (1920 x 1080, full screen, 8x msaa) before I decided to loop unigine heaven benchmark. heaven did yield a BSoD at first, however once i updated Intel rapid storage technology I was able to loop for several hours without issue before i stopped it (1920 x 1080, ultra preset, tessellation enabled and 8x msaa).

 

I'll run prime95 and WD data lifeguard next. Also, happy new year :) .



#4 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 01 January 2017 - 04:02 PM

Blue screen while coming on to the 3rd hour of prime95 stress testing. was unable to catch the error message and no dump was generated. it did look like 2 of the threads fell behind and locked up though. while im leaning towards cpu issues, could this also indicate something wrong with the motherboard? temps never went above 65C.

Edit:

Just noticed the 2tb HDD is no longer being picked up by Windows or in BIOS.

 

Edit... again:

 

2tb hard drive being detected again


Edited by apelle93, 01 January 2017 - 08:42 PM.


#5 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 02 January 2017 - 10:50 AM

Attempted to run prime95 overnight Bsod occurred again, however this time it left a dump. windb points to SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) most likely cause by nvlddmkm.sys ( nvlddmkm+9cc67f ). If i recall correctly this is related to nvidia's driver which as of today i still have the latest stable driver. I can always try the beta driver though im not sure if that would make much of a difference being that its mostly fixes for games.

 
 
I've attached the latest dump just in case I've missed something, plus im still a novice at deciphering minidumps.

Attached Files



#6 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 03 January 2017 - 12:28 PM

Just an update on my end, I decided to try out driver verifier and it pointed to razer drivers. I removed any razer software i had as well as drivers and left prime95 to run over night, and it was successful. Prime95 ran from ~12:30am to now when I woke up to check on it and shut it off (approximately 12 hours total). I think my issue is solved, but i'll report back if anything changes.

 

Thanks for the help Usasma :)



#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:35 AM

Posted 03 January 2017 - 03:16 PM

Interesting to note that you had Prime95 errors and it seems to be fixed by updating the Razer drivers - I'll have to rethink my approach to this testing (and my assumptions about hardware type errors  from my previous post)..

Did you happen to check the results.txt file for Prime95? it'll record errors that it finds there.

 

In general, Prime 95 tests 3 things:

- RAM

- CPU cache

- memory controller (on the CPU for i3, i5, and i7 CPU's)

Also, note that Prime95 can catch memory errors that MemTest misses.  This is most often the case when the system spits errors/crashes on the Blend test.

It appears that a BSOD when running Prime95 may not always be the fault of Prime95 - the results.txt file should help with this attempt at a diagnosis.

Again, the waters of BSOD analysis just keep getting muddier and muddier! (IOW - analysis just keeps getting more difficult).

 

Good luck!


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.

#8 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 03 January 2017 - 03:26 PM

Interesting to note that you had Prime95 errors and it seems to be fixed by updating the Razer drivers - I'll have to rethink my approach to this testing (and my assumptions about hardware type errors  from my previous post)..

Did you happen to check the results.txt file for Prime95? it'll record errors that it finds there.

 

In general, Prime 95 tests 3 things:

- RAM

- CPU cache

- memory controller (on the CPU for i3, i5, and i7 CPU's)

Also, note that Prime95 can catch memory errors that MemTest misses.  This is most often the case when the system spits errors/crashes on the Blend test.

It appears that a BSOD when running Prime95 may not always be the fault of Prime95 - the results.txt file should help with this attempt at a diagnosis.

Again, the waters of BSOD analysis just keep getting muddier and muddier! (IOW - analysis just keeps getting more difficult).

 

Good luck!

 

Well actually I completely removed them. I'm currently in the process of retesting with the software reinstalled. the results.txt show's nothing but passes from beforehand so I'm not sure what to think. If I break past the 3 hour mark which I could not do before I'll assume the issue is resolved, but if anything else happens I'll keep everyone posted.



#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:35 AM

Posted 03 January 2017 - 04:00 PM

Most often (AFAIK) the only thing that'll show up error-wise in the results.txt file will be some entries that say "Fatal error" - that's a sign that Prime95 found errors.

Good luck!


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.

#10 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 19 April 2017 - 07:32 PM

Hello All,

 

Don't mean to bring a post back from the dead, but same computer again having issues with blue screens. This time however, i did a fresh install of windows. I'm honestly lost again as I ran 8+ hours of prime95 (blend test) the day before with out issue as well as 8 hours of memtest with zero errors. also ran unigine superpostion benchmark several times yesterday to stress the videocard (even ran the 8k resolution run to see if it would crash). Today i ran unigine valley for aproximately 10 minutes and it crashed.

 

Im debating on RMAing the motherboard and possibly the cpu. not sure what else could be the problem if its hardware related.

 

system specs:

 

Msi z170m mortar with A9 bios

Intel core i7 6700 (non k)

16gb corsair vengeance low profile ddr4 2133

Asus stirix gtx1060 6gb

Samsung 850 evo 250gb sata ssd

Western Digital 2tb black HDD

corsair rmx 550w 80 plus gold psu

silverstone  120mm aio liquid cooler

Windows 10 home x64

 

 

slight update:

 

as per usama's website the stop code for the most recent bsod was STOP 0x00000139: KERNEL_SECURITY_CHECK_FAILURE.

 

ran AV as well as TDSSKiller and the system appears to be clean.

-----------------

 

Also ran WD Data lifeguard extended test on the ssd (passed). Same test is in progress on the HDD.

Attached Files


Edited by apelle93, 19 April 2017 - 09:59 PM.


#11 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 20 April 2017 - 06:00 AM

Mini Update:

 

WD Data Lifeguard extended test passed on all drives. not sure where else to go from there.



#12 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:35 AM

Posted 20 April 2017 - 07:51 AM

Your UEFI/BIOS (version A.90) dates from 2016.  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).

Only 3 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this (7 or 8 are the most common number recently).  Please visit Windows Update and get ALL available Windows Updates.
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.

Have you reinstalled the OS?  There are fewer updates than there were previously.

 

Beyond this, I don't see any further problems with the reports.
As such, the most likely explanation is a hardware problem (although compatibility issues and low-level driver problems remain a possibility)

Start with ALL of these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Feel free to skip the HDD test, but be sure to run ALL of the other diagnostics.
Let us know the results of ALL of the tests and we can move on from there.

 

FYI - my tentaive thought here is that there's a memory problem - which all of the tests will check for.

I most suspect the video card memory - but it can also be a problem with other memory - so ALL of the other tests are necessary.

 

The results of the 3 memory dumps analyzed below tend to support this theory of mine (that it's a hardware problem)......

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Wed Apr 19 20:09:11.705 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\041917-5187-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.1066.amd64fre.rs1_release_sec.170327-1835
System Uptime:1 days 20:37:13.389
Probably caused by :memory_corruption
BugCheck 139, {3, ffffbf0115e8b6c0, ffffbf0115e8b618, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffbf0115e8b6c0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffbf0115e8b618, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.90
  BIOS Release Date             12/14/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Apr 17 23:07:34.183 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\041717-3656-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.1066.amd64fre.rs1_release_sec.170327-1835
System Uptime:0 days 0:04:14.865
Probably caused by :dxgmms2.sys ( dxgmms2!VidSchIsGpuAccessBlocked+16 )
BugCheck 3B, {c0000005, fffff80ab4e34966, ffff8801c136cf80, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80ab4e34966, Address of the instruction which caused the bugcheck
Arg3: ffff8801c136cf80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  HWMonitor.exe
FAILURE_BUCKET_ID: 0x3B_dxgmms2!VidSchIsGpuAccessBlocked
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.90
  BIOS Release Date             12/14/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Apr 17 14:59:14.395 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\041717-4015-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.1066.amd64fre.rs1_release_sec.170327-1835
System Uptime:0 days 0:11:50.078
Probably caused by :memory_corruption
BugCheck 1A, {61941, 706205ae, 1d, ffffc980c5936a80}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 00000000706205ae
Arg3: 000000000000001d
Arg4: ffffc980c5936a80
BUGCHECK_STR:  0x1a_61941
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
CPUID:        "Intel® Core™ i7-6700 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3408
  BIOS Version                  A.70
  BIOS Release Date             09/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             Z170M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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:

**************************Wed Apr 19 20:09:11.705 2017 (UTC - 4:00)**************************
ndisrfl.sys                 Thu Jul  9 13:06:23 2015 (559EAA0F)
rt640x64.sys                Thu Jul 14 05:04:28 2016 (5787559C)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
iaStorA.sys                 Tue Sep 13 10:45:46 2016 (57D8111A)
TeeDriverW8x64.sys          Thu Sep 15 13:08:03 2016 (57DAD573)
nvhda64v.sys                Wed Mar 15 08:48:41 2017 (58C93829)
cpuz143_x64.sys             Thu Mar 23 07:26:40 2017 (58D3B0F0)
RTKVHD64.sys                Tue Mar 28 09:33:44 2017 (58DA6638)
nvlddmkm.sys                Fri Mar 31 21:26:23 2017 (58DF01BF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Apr 17 14:59:14.395 2017 (UTC - 4:00)**************************
rt640x64.sys                Thu Jan 21 03:17:40 2016 (56A09424)
intelide.sys                Fri Jul 15 22:29:13 2016 (57899BF9)
MegaSas2i.sys               Fri Jul 22 17:36:46 2016 (579291EE)

http://www.carrona.org/drivers/driver.php?id=ndisrfl.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
cpuz143_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
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
MegaSas2i.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.
 


Edited by usasma, 20 April 2017 - 07:52 AM.

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 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 20 April 2017 - 08:25 PM

Hi usasma,

 

as per my previous posts:

 

  • Did a fresh install of windows (hence the lower update count)
  • ran memtest for 8 hours with no errors
  • ran prime 95 for 8 hours with no errors
  • ran furmark for a half hour (for got to mention this one) and then switched to the unigine superposition benchmark (which can max out vram on the gtx 1060) with no issue
  • shut down and came back the next day and ran unignie valley and crashed after approx. 10 minutes.
  • ran data life guard long test on both had and sdd 

 

I just swapped out the ram with a new kit that I bought for another build so will report back with results soon.



#14 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:35 AM

Posted 21 April 2017 - 04:44 AM

Sorry for missing that stuff, but I have some serious eye problems and it hurts for me to use my eyes a lot - so I scan a lot of things rather than reading in depth.

 

Have you run the Video2 tests listed here:  http://www.carrona.org/hwdiag.html#morevideo

and the CPU test(s) immediately below it?  If so, what were the results?

The Video2 tests are much more in-depth than the FurMark test.

 

Still, I'm fairly sure that this is a hardware issue.  Do you have another good video card that you can test with?

But, as other things are possible, please run Driver Verifier according to these instructions after you've finished up the diagnostics:  http://www.carrona.org/verifier.html


Edited by usasma, 21 April 2017 - 04:45 AM.

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 apelle93

apelle93
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:08:35 AM

Posted 23 April 2017 - 12:47 PM

Mini update:

 

after swapping ram, the computer has been stable. I've ran it for the past coupe of days without issues.

 

  • 8 hour run prime 95,  no errors
  • 2 hour run on unigine valley benchmark,  no issues
  • 7 hours of  continuous game play on civilizations VI,   no issues

 

Guess it's time to go through the rma process...






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users