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

Windows 10: Random BSODs on Boot; All ntoskrnl.exe related


  • Please log in to reply
5 replies to this topic

#1 happeleh

happeleh

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:31 AM

Posted 20 January 2017 - 07:32 PM

Windows 10 64bit
Original OS - Windows 8.1
Windows was installed from an ISO downloaded from Microsoft
Laptop was purchased in July 2015
OS was reinstalled < 2 weeks ago (because of BSODs, problem persists). Was installed onto a formatted drive.
 
CPU - i7 4870HQ (no overclocking)
GPU - 970M (no overclocking)
OS installed on the SSD, HDD used for storage.
Motherboard/PSU - N/A it's a laptop
 
System Manufacturer - Cyberpower PC
Model Number - Model: C Series Fangbook Edge 536508-A8PWLX
 
Some context:
 
I have been experiencing BSODs for long enough now that I don't remember when it started exactly.
~90% of the BSODs occur during boot, occasionally I can get to the desktop where it will crash when opening a program usually.
The stop codes being displayed change, but all seem to be linked to ntoskrnl.exe (found that out using BlueScreenView)
 
If I keep restarting eventually I can get into Windows and everything works great.
It stays stable when it finally does boot into Windows, I've gamed/used it for hours on end with no problems.
The number of restarts it takes to get the laptop to boot varies, I haven't noticed a pattern.
Also, just plain restarting the system usually results in no BSOD.
I've found that the most consistent method of facilitating a BSOD is to boot it up after its been off/in sleep mode for a while.
 
 
This laptop is essentially an MSI GS60:
While the specs listed on that page are not identical to mine, the chassis is the same
Cyberpower PC obtains barebones laptops from MSI, and does the rest of the assembly.
 
Things I've Tried:
 
BIOS Update - I heard directly from Cyberpower PC support that they do not have BIOS support. I asked about using the MSI BIOS files from the Ghost Pro page, they said they cannot say if it will work or not. 
General Driver Updates - Video Drivers, Network Drivers
Troubleshooting tricks within Windows: sfc /scannow (found no problems), ran WindowsMemoryDiagnostic (no errors)
 
 
I followed the posting guide, so everything should be here. I'll be more than happy to provide more information if needed.
 

Attached Files



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:09:31 AM

Posted 22 January 2017 - 08:31 AM

The perfmon report shows issues that I usuall associate with BIOS updates.

Pretty poor support for the amount of money they want you to spend.

I would suggest trying the MSI BIOS update - but be aware that it's possible that this will physically damage the system (so only use it as a last resort)

Try comparing the current BIOS number with the BIOS numbers on the MSI site.

 

But first, let's try this stuff............

 

Your UEFI/BIOS (version E16H5ICP.106) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
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.  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.

 

Please update your Intel wifi driver as it dates from well before W10 was released.

 

There are only 3 memory dumps in the uploaded reports, but there are 3 different BSOD error codes.

Sometimes this is a symptom of a hardware problem - so I would start with these free hardware diagnostics:   http://www.carrona.org/hwdiag.html

Please finish ALL of the tests and let us know the results.

If ALL of the tests pass, 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 Jan 20 11:48:15.499 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012017-5515-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 16:06:34.189
Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+659 )
BugCheck 19, {25, 46, 5, ffffa105b1d09920}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000025,
Arg2: 0000000000000046
Arg3: 0000000000000005
Arg4: ffffa105b1d09920
BUGCHECK_STR:  0x19_25
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x19_25_nt!ExDeferredFreePool
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 19 19:41:15.621 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011917-5734-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 1:47:55.394
*** 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, fffff805cbf5e3e9, ffffd50028f1c6e8, ffffd50028f1bf10}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff805cbf5e3e9, The address that the exception occurred at
Arg3: ffffd50028f1c6e8, Exception Record Address
Arg4: ffffd50028f1bf10, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 19 17:53:01.139 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011917-4250-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 2:07:30.914
*** 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 C2, {7, 0, 0, ffffa58fecc13650}
BugCheck Info: BAD_POOL_CALLER (c2)
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000000000, Pool tag value from the pool header
Arg3: 0000000000000000, Contents of the first 4 bytes of the pool header
Arg4: ffffa58fecc13650, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_Ntfx
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Jan 20 11:48:15.499 2017 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
Netwbw02.sys                Sun Feb 22 06:00:57 2015 (54E9B6E9)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
ETD.sys                     Mon Jul 27 22:01:31 2015 (55B6E27B)
RTKVHD64.sys                Tue Nov 24 07:41:57 2015 (56545B15)
mbae64.sys                  Fri Apr 29 06:10:09 2016 (57233301)
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
mbam.sys                    Wed Sep 28 11:45:44 2016 (57EBE5A8)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
farflt.sys                  Wed Nov  2 10:29:12 2016 (5819F838)
MBAMSwissArmy.sys           Wed Nov  9 09:21:05 2016 (582330D1)
ibtusb.sys                  Mon Nov 14 19:31:48 2016 (582A5774)
mwac.sys                    Thu Nov 17 20:02:05 2016 (582E530D)
MBAMChameleon.sys           Sat Nov 19 14:13:08 2016 (5830A444)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
nvvhci.sys                  Thu Dec 15 04:29:03 2016 (5852625F)
nvvad64v.sys                Mon Dec 19 00:50:05 2016 (5857750D)

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=ETD.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
e2xw10x64.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=mbam.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.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=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
nvvhci.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=nvvad64v.sys

 


Edited by usasma, 22 January 2017 - 08:32 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.

#3 happeleh

happeleh
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:31 AM

Posted 23 January 2017 - 12:24 PM

Thanks so much for your reply! I am a college student, so the amount of time I have to commit to troubleshooting is limited. I have tried a few of your suggestions:

 

  • I updated my Intel Wifi drivers - Intel had a really nice automatic driver detection and installation suite.
  • Checked windows update (it says "Your System is up to date). I ran "Find and fix Windows Update Problems" to be sure all was good, it fixed a few things. The update history page shows a number a failed updates. I checked Microsoft's website and the most recent update they pushed out successfully installed on my machine, so I'm assuming it's all good.

r7HadXQ.png

  • Ran Memtest for 4 passes, came up with no errors. I could try and test each RAM chip individually; do you think that is an appropriate step to take? How many passes would you recommend for each chip?

The BIOS version listed on MSI's website for the Ghost laptop is E16H5IMS.111 2016-03-25; System information displays my BIOS version as E16H5ICP.106 9/25/2014

The numbers appear similar, but for me that's not enough information to take a $1,300 leap of faith, and from what I've seen of Cyberpower support so far if I brick it sending it back to them for repair will be a nightmare.

 

I've attached more dump files, there were only a few initially as I just reinstalled windows. Different stop code each BSOD, this still has me so confused.

Unfortunately none of these things worked, but they certainly didn't hurt my machine. I'll work through the rest of the tests you suggested and get back to you. Thanks again!

Attached Files


Edited by happeleh, 23 January 2017 - 12:31 PM.


#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:09:31 AM

Posted 24 January 2017 - 07:24 AM

No problem, take your time replying.  I get an email whenever you reply to this topic.

 

I'm not a Windows Update expert - but failed updates don't seem to be a good thing to me.
BUT, when you check for updates now, does it say that all is good?  If so, then I wouldn't worry about it for now.
If you are concerned, I'd suggest posting a topic in the Windows 10 forum with "Windows Update" or something similar in the title (to attract the Windows Update experts).

 

I fully understand about the BIOS update - I wouldn't want to do it either.  Similar isn't good enough - you'd need an exact match.
Were you able to find a BIOS update on the MSI site that had the E16H5ICP.106 version?

If not, this makes it very unlikely that the later MSI BIOS will work - and the chances of borking your system are great (IMO).

 

Random errors are generally a sign of a low-level error - be it hardware, compatibility, or even low-level drivers.

That's why we suggest hardware diagnsotics.

In this case, it's 8 different BSOD codes out of a total of 13 memory dumps - still suggestive of hardware., compatibility, or low-level drivers.

 

As you've reinstalled Windows and the piablem remains, you've eliminated a lot of the software stuff.

Most likely the Windows installation media was good - as you didn't relate any issues with reinstalling Windows.

And, as you had to reinstall any third party software - that suggests that it wasn't a problem either

 

The most certain test here would be to reinstall W8.1 and see if the problem remains (you can always update to W10 later on)

That would remove any problems with compatibility - as that's what the system was designed for.

I'm still fairly certain that this is a hardware problem - as I haven't seen these sort of problems with systems designed for W8.1

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan 23 10:33:02.448 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012317-6437-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:00:07.182
Probably caused by :memory_corruption
BugCheck 1A, {41793, fffff30000026480, 2, 1}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff30000026480
Arg3: 0000000000000002
Arg4: 0000000000000001
BUGCHECK_STR:  0x1a_41793
PROCESS_NAME:  OriginWebHelperService.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 23 10:30:37.064 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012317-5875-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:00:11.883
Probably caused by :memory_corruption
BugCheck EF, {ffff9d096d022780, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffff9d096d022780, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 23 10:29:59.987 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012317-6906-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:37:35.718
Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+b9d )
BugCheck 19, {e, fffff51a407f9390, 299be369adfbf357, d66461ed168cd4d7}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 000000000000000e,
Arg2: fffff51a407f9390
Arg3: 299be369adfbf357
Arg4: d66461ed168cd4d7
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  LogonUI.exe
FAILURE_BUCKET_ID: 0x19_e_VRF_nt!ExDeferredFreePool
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Mon Jan 23 10:33:02.448 2017 (UTC - 5:00)**************************
MBfilt64.sys                        Thu Jul 30 23:40:32 2009 (4A7267B0)
TeeDriverW8x64.sys                  Tue Jul  7 13:43:32 2015 (559C0FC4)
ETD.sys                             Mon Jul 27 22:01:31 2015 (55B6E27B)
RTKVHD64.sys                        Tue Nov 24 07:41:57 2015 (56545B15)
IntcDAud.sys                        Tue May 10 04:08:56 2016 (57319718)
intelppm.sys                        Fri Jul 15 22:10:43 2016 (578997A3)
e2xw10x64.sys                       Wed Sep 14 16:52:26 2016 (57D9B88A)
igdkmd64.sys                        Thu Sep 29 10:43:27 2016 (57ED288F)
Netwbw02.sys                        Sun Oct  9 12:00:54 2016 (57FA69B6)
ibtusb.sys                          Mon Nov 14 19:31:48 2016 (582A5774)
nvlddmkm.sys                        Sun Dec 11 13:13:24 2016 (584D9744)
nvvhci.sys                          Thu Dec 15 04:29:03 2016 (5852625F)
nvvad64v.sys                        Mon Dec 19 00:50:05 2016 (5857750D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 23 10:29:59.987 2017 (UTC - 5:00)**************************
Syst?m32?dri?ers?gpu?nergydrv.sys   Fri Jul 15 22:28:09 2016 (57899BB9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 19:19:37.693 2017 (UTC - 5:00)**************************
xusb22.sys                          Fri Jul 15 22:28:13 2016 (57899BBD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 17:04:33.941 2017 (UTC - 5:00)**************************
Netwbw02.sys                        Sun Feb 22 06:00:57 2015 (54E9B6E9)

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=ETD.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
e2xw10x64.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
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
nvvhci.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=nvvad64v.sys
Syst?m32?dri?ers?gpu?nergydrv.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=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
 


Edited by usasma, 24 January 2017 - 07:25 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.

#5 happeleh

happeleh
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:31 AM

Posted 03 February 2017 - 05:23 PM

When booting my laptop up today I noticed the stop codes where different than usual. A couple crashes occurred after making it to the desktop.

 

What threw a red flag for me was one of the stop codes displayed was: DRIVER_VERIFIER_DETECTED_VIOLATION

 

I have run driver verifier before, but never had it capture anything cause it's difficult for me to make the computer crash. I'm certain I disabled driver verifier, so seeing that code has me a little confused. Either I unknowingly never disabled driver verifier, or that stopcode doesn't mean what I think it does.

 

Anyway, would you be able to take a look at the dump files and provide some more suggestions on things to try? The dumps I'm talking about are from 2/3/17.

 

Attached File  SysnativeFileCollectionApp.zip   5.39MB   1 downloads



#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:09:31 AM

Posted 06 February 2017 - 05:40 AM

It is possible to throw a Driver Verifier enabled crash without enabling Driver Verifier.

I'm uncertain of the exact circumstances, but I have seen it several times before (I seem to recall that those were related to video drivers/components also)

Still, it doesn't hurt to run verifier.exe and select "Delete existing settings", then click on "Finish" and reboot for the changes to take effect.

 

Various different STOP errors are usually a sign of a hardware/compatibility/low-level driver issue.

 

You still have to fix the Windows Update problems.
I suggest posting in the Windows 10 forums with something about Windows Update in the topic title (to attract the Windows Update experts)

If that doesn't work, then I'd suggest trying these different repairs until you get Windows Update to work:

NOTE:  Try a clean boot to see if the problem clears up that way:  http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows
If it does, then different troubleshooting steps are called for.

Here's some repair/recovery/restore options (in this order).   Be sure to backup your stuff if you don't want to take the chance of losing it.:

 

1 - Startup Repair.  Run it 3 times, rebooting in between tries.

2 - System Restore to a point before this started happening.

3 - DISM/SFC repair (DISM doesn't work with W7, although SFC does)  - doesn't work if you're not able to boot to Windows (let me know and I'll post a way to do it from Startup Repair)
    

 

Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt).  Press Enter after typing it:
   
Dism /Online /Cleanup-Image /RestoreHealth
    FYI - I have repaired systems using the last command even though problems weren't found with the first 2 - so I suggest running them all.

    From this article: http://technet.microsoft.com/en-us/library/hh824869.aspx

    You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption. Include the CBS log (located at C:\Windows\Logs\CBS\CBS.log) if you'd like to have a Windows Update expert check it (I don't check them because I can't read them)


4 - RESET using the "Keep My Files" option (W8 calls this a REFRESH; W7 and earlier doesn't have this function)

5 - Repair install of the OS (Thanks to FreeBooter!):
   

 

"How To Perform a Repair Installation For Windows 8, 8.1 and 10"
    https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html

    "How to Do a Repair Install to Fix Windows 7"
    http://www.sevenforums.com/tutorials/3413-repair-install.html

    "How To Perform a Repair Installation For Vista"
    http://www.vistax64.com/tutorials/88236-repair-install-vista.html

    "Non-destructive reinstall of Windows XP"
    https://www.winhelp.us/non-destructive-reinstall-of-windows-xp.html


6 - RESET using the "Remove Everything" option (W8 calls this a RESET; W7 and earlier doesn't have this function)

If using W7 or earlier, this can be accomplished by resetting the system by use of the recovery partition/recovery disks/recovery drive.
If you don't have them, you can usually order them from the OEM manufacturer of your system ( US points of contact here:  http://www.carrona.org/recdisc.html )

7 - Wipe and reinstall from the Recovery Partition (if so equipped)

8 - Wipe and reinstall from Recovery Media - to include deleting all partitions.
If you don't have them, you can usually order them from the OEM manufacturer of your system ( US points of contact here:  http://www.carrona.org/recdisc.html )

 

Out of 24 memory dumps there were 9 different BSOD  (aka STOP or BugCheck) error codes.  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 you have finished ALL of the diagnostics and nothing has been found, then start with this procedure to help identify the problem device(s):  http://www.carrona.org/strpdown.html

 

FWIW - I suspect a memory problem of some sort.  And (just guessing) as the Driver Verifier enabled memory dumps pointed to video - I have to wonder about video memory problems.  Have you run the video memory test suggested in the hardware diagnostics?

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Fri Feb  3 16:39:53.576 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-6734-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:01:08.305
Probably caused by :memory_corruption
BugCheck 139, {e, ffffe2001f3591d0, ffffe2001f359128, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 000000000000000e, Type of memory safety violation
Arg2: ffffe2001f3591d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffe2001f359128, 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_ONE_BYTE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 16:38:26.792 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-6281-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 2:15:01.609
*** 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 12B, {ffffffffc00002c4, 95c, 4d00990, ffffa500f74aa000}
BugCheck Info: FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 000000000000095c, physical page number
Arg3: 0000000004d00990, zero
Arg4: ffffa500f74aa000, zero
BUGCHECK_STR:  0x12B_c00002c4_StCtDecompressFailed
PROCESS_NAME:  MemCompression
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 14:23:02.739 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020317-6609-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:02:38.571
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
Probably caused by :pci.sys
BugCheck 9F, {3, ffffe6894ede3060, fffff801e77b1cb0, ffffe6895092a6b0}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe6894ede3060, Physical Device Object of the stack
Arg3: fffff801e77b1cb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe6895092a6b0, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_VRF_3_nvlddmkm_IMAGE_pci.sys
CPUID:        "Intel® Core™ i7-4870HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  E16H5ICP.106
  BIOS Release Date             09/25/2014
  Manufacturer                  CYBERPOWER Coporation
  Baseboard Manufacturer         
  Product Name                   
  Baseboard Product             MS-16H5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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 Feb  3 16:39:53.576 2017 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
ETD.sys                     Mon Jul 27 22:01:31 2015 (55B6E27B)
RTKVHD64.sys                Tue Nov 24 07:41:57 2015 (56545B15)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
Netwbw02.sys                Sun Oct  9 12:00:54 2016 (57FA69B6)
ibtusb.sys                  Mon Nov 14 19:31:48 2016 (582A5774)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
nvvhci.sys                  Thu Dec 15 04:29:03 2016 (5852625F)
nvvad64v.sys                Mon Dec 19 00:50:05 2016 (5857750D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  3 00:17:18.139 2017 (UTC - 5:00)**************************
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 31 14:47:08.667 2017 (UTC - 5:00)**************************
magdrvamd64.sys             Wed Aug 26 07:30:12 2015 (55DDA344)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 29 14:46:01.330 2017 (UTC - 5:00)**************************
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=ETD.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
e2xw10x64.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
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
nvvhci.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=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=magdrvamd64.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys


 


Edited by usasma, 06 February 2017 - 05:41 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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users