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

PC BSOD while shutting down


  • Please log in to reply
13 replies to this topic

#1 Oklearz

Oklearz

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 18 October 2016 - 09:21 AM

Hey,

lately I've been getting BSODs, but not regular ones. I don't actually see it. I just noticed that the pc needed a lot more time to shut down that usual. It also needs more time to fully boot up again. I already checked the dumps with BlueScreenView, as well as WinDBG. With WINDBG I found out that the BSOD is probably caused by ndis.sys (which is, if I'm not wrong, the network driver). I had this problem before but resolved it by reinstalling the driver. My network driver is Qualcomm Atheros AR8161 PCI-E Gigabit Ethernet Controller (NDIS 6.30) and I am pretty sure I already got the latest version. My PC is running Windows 10 64 Bit. I attached the two latest minidumps to this thread, so you can check it out yourself. Thanks for your help in advance. 

Attached File  Dumps.zip   508.95KB   1 downloads



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:04:23 PM

Posted 19 October 2016 - 06:07 AM

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 

*******************************************************************************************

There are many different reasons that the ndis.sys driver may be blamed - and only some of them are due to the networking driver that you mentioned.

The number of possibilities increases when this is associated with a sleep/hibernate/shutdown transition.

 

While waiting for the other reports, let's have a look at the memory dumps.....

 

Your UEFI/BIOS (version F13) dates from 2012.  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).

I don't know how many Windows Update hotfixes are installed.  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.

As these are BSOD's during a power down transition, please ensure that you have the latest, W10 compatible chipset and Intel drivers (RST, MEI, DFTP, SCCT, etc) installed.

Update your video drivers also - as they also affect power transitions.  Your video drivers date from 01Oct2016 - so you may not be able to update them.  In that case, uninstall them and then download install a fresh copy.

 

Uninstall Gigabyte's Precision X.  It uses the WinRing0x64.sys driver - which is known to cause BSOD's on some WIndows systems.

Additionally, it dates from 2013, well before the release of W10 - so I wonder about it's compatibility w/W10

 

Your wired networking driver (L1C63x64.sys) also dates from 2013.

Please update it to the latest, W10 compatible version.

While the current one may be the latest, you must ensure that it is W10 compatible.

If it's not compatible, then you'll need to look at other networking solutions.

 

You also seem to have HotSpotShield installed.

Back in the W7 days this was a know BSOD cause

Your version has a driver dating from 2015 - and I haven't seen any BSOD's from this version - but one has to wonder if there are any issues with it.
I'd try uninstalling it to see if that helps stop the BSOD's

 

If these things don't stop it, then try running 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 Oct 17 17:24:52.626 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\101816-36406-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:0 days 9:06:34.092
Probably caused by :ndis.sys ( ndis!NdisMRegisterInterruptEx+1e94 )
BugCheck 9F, {3, ffffc20fea1ef400, fffff801dedbf960, ffffc20fef3a8010}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffc20fea1ef400, Physical Device Object of the stack
Arg3: fffff801dedbf960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc20fef3a8010, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!NdisMRegisterInterruptEx
CPUID:        "Intel® Core™ i5-3470 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3203
  BIOS Version                  F13
  BIOS Release Date             09/19/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77M-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 16 17:55:32.790 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\101716-44968-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:3 days 13:20:31.498
Probably caused by :ndis.sys ( ndis!NdisMRegisterInterruptEx+1e94 )
BugCheck 9F, {3, ffffe50e7f9d8060, fffff8039109b960, ffffe50e8403f010}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe50e7f9d8060, Physical Device Object of the stack
Arg3: fffff8039109b960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe50e8403f010, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!NdisMRegisterInterruptEx
CPUID:        "Intel® Core™ i5-3470 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3203
  BIOS Version                  F13
  BIOS Release Date             09/19/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77M-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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 Oct 17 17:24:52.626 2016 (UTC - 4:00)**************************
WinRing0x64.sys             Wed May  1 22:19:47 2013 (5181CD43)
L1C63x64.sys                Tue Jul 16 02:56:31 2013 (51E4EE9F)
iaStorA.sys                 Fri May  2 19:06:56 2014 (53642510)
VClone.sys                  Sat May  3 12:53:40 2014 (53651F14)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
viahduaa.sys                Tue Aug 18 03:38:56 2015 (55D2E110)
hssdrv6.sys                 Fri Sep 18 17:42:05 2015 (55FC852D)
ICCWDT.sys                  Sun Sep 20 03:59:19 2015 (55FE6757)
mbamchameleon.sys           Wed Jan 27 18:48:35 2016 (56A95753)
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvvad64v.sys                Fri Jul  1 09:12:29 2016 (57766C3D)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
nvlddmkm.sys                Sat Oct  1 15:08:52 2016 (57F009C4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 16 17:55:32.790 2016 (UTC - 4:00)**************************
MegaSas2i.sys               Fri Jul 22 17:36:46 2016 (579291EE)

http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys
http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=hssdrv6.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.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=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.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, 19 October 2016 - 06:09 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 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 19 October 2016 - 10:20 AM

Hey,

the newest BIOS/UEFI drivers available for my motherboard would be F15a, it says it's a Beta BIOS though, so I'm not sure about installing that. I have all Windows Updates installed and always try to keep it updated, just like I try to keep my video drivers updated.
I do have Hotspot Shield installed, but I rarely use it, so I deactivated it in the device manager. I'll try to uninstall that in case the BSOD returns.
Unfortunately, Qualcomm does not offer driver downloads on their official website, the website that looks the most trustworthy would be atheros-drivers.com and it states that the required driver is not available for Windows 10. But I have downloaded the Windows 8 64-Bit version from there before to fix the problem. It did fix it for a week, but the problem returned. The driver seems to work great though (apart from the BSOD this thread is about)
To be honest, it really could be EVGA Precision XOC, as I never had any problems like this when I hadn't installed it yet. But it'd be a shame uninstalling it, because it works great. I will uninstall it temporarily to see if it fixes the problem. I would like a tool like that though to increase performance. Might try MSI Afterburner, if Precision XOC is the culprit (I hope Afterburner can't cause these problems). You said PrecisionXOC was dates back to 2013, I am running the newest version though, which was released in September 26 2016.

Thanks for taking your time to help me! I appreciate it.


Attached File  SysnativeFileCollectionApp.zip   1.52MB   2 downloads



#4 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:04:23 PM

Posted 20 October 2016 - 05:08 AM

Don't try the beta BIOS yet.  What does the description say that the beta version does/fixes?

Do you have a link for it?

 

Disabling HotSpotShield in Device Manager may help, but please understand that the driver still loads into memory when the system boots.

I don't suspect that it's a major issue - but have always suggested uninstalling the program just in case the disabled driver affects things in some unknown way.

It's fairly easy to uninstall/reinstall the program - so it shouldn't take much effort on your part.

 

This is a clue that your Qualcomm driver may not be compatible w/W10:

 

states that the required driver is not available for Windows 10.

 

As for Precision XOC, it's possible that it's causing a problem - but there are also known issues with MSI Afterburner, Riva Tuner, and AMD Overdrive.

The point here is to do without them temporarily to see if the BSOD's stop.

Then, if they do stop, you can reinstall the programs(s), one by one and test to see if the BSOD's return. (this will let you know if a corruption caused the problem - or if the program itself is the problem).

 

A final bit of discussion before I start the analysis.

BSOD's are sometimes easy, and sometimes very complicated.

Network BSOD's have many possible causes - simply because most computers have an enormous number of programs that affect/interact with the internet.

Running Driver Verifier according to these instructions may help force the offending driver to the surface:  http://www.carrona.org/verifier.html

 

If you note in the systeminfo.txt report (down at the bottom), you'll see that the HotSpotShield network device is still being detected - despite having been disabled in Device Manager.

 

These devices are disabled in Device Manager:

 

Evolve Virtual Ethernet Adapter    ROOT\NET\0001    Das Gerät wurde deaktiviert.
Anchorfree HSS VPN Adapter    ROOT\NET\0002    Das Gerät wurde deaktiviert.

Please re-enable them, then uninstall the programs associated with them.

Feel free to reinstall a freshly downloaded copy once we've finished troubleshooting.

 

Precision X_x64 has crashed 9 times in Sep/Oct of 2016

Please uninstall it temporarily to test it.

 

What I suggest is elimnating all of the other possible networking problems (but uninstalling them) so you can focus on the network adapter itself.

If you've eliminated all the other possible causes, then you'd be able to figure out if the network adapter remains at fault (and that this may be due to an incompatibility).

 

Lastly, I suggest trying another networking card (and either physically removing the current one or disabling it in the BIOS)

Network cards are fairly cheap, and it's always a good idea to have one on hand (in case your system stops accessing the internet at a time when all the shops are closed).

This would be the fastest/easiest "fix" if the current card is truly incompatible.

 

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.

#5 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 20 October 2016 - 05:26 AM

Hey,

yesterday the computer took a lot of time to completely shut down again. So yeah, it happened again even after completely uninstalling Precision XOC, so it probably didn't have anything to do with that. I'll just install it again after the problem is resolved. The minidump is attached again. I think I will try reinstalling the Windows 8.1 driver that is causing these issues to see if it resolves it again. Just in case it could help, using the commands "sfc /scannow" and "dism.exe /online /cleanup-image /restorehealth" in the command prompt outputs that it does not find any integrity violations/ended successfully.


Attached File  Minidump.zip   232.23KB   1 downloads



#6 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 20 October 2016 - 06:02 AM

Hey again,

here's the link to the BIOS downloads: http://www.gigabyte.com/products/product-page.aspx?pid=4142#bios
I have activated the network entries in the device manager and uninstalled the programs associated with them. As I said earlier, I reinstalled the network driver (for Windows 8.1 64-Bit), so maybe it resolved the issue. If it did, I'll post that here. I will reinstall Hotspot Shied and Evolve when I need them again (only after I don't get the BSODs anymore, obviously)



#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:04:23 PM

Posted 22 October 2016 - 07:05 PM

There's no additional info for the BIOS - I'd leave it alone for now.

Otherwise your plan seems sound.  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 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 24 October 2016 - 06:54 AM

Hey,

so I haven't got any BSODs yet, but the last two times it shut down, it took a lot of time again. So it seems like when I try to shut down my computer, it enters standby-mode. Then five minutes later it gets reactivated (and then shut down like it's supposed to I guess). I don't even have sleep mode enabled. So I suspect the fast startup feature of Windows 10 is at fault. I turned off fast startup in Windows 10 and the hybrid shut down option in Classic Shell. I attached some events I saved from eventviewer (in case that could help indentify the problem).

 

Attached File  Shutdown.zip   2.37KB   1 downloads



#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:04:23 PM

Posted 26 October 2016 - 03:17 PM

The shutdown log shows it's entering sleep.

I'd suggest posting over in the Windows 10 forums for help with ensuring that sleep is fully disabled.

I don't usually bother with those things, so I'm not really qualified to help with that.


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 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 31 October 2016 - 08:07 AM

Hey,

 

I haven't got a BSOD so far! I hope it stays this way. Also to the other problem: I deactivated Hybrid mode in Classic Shell but activated fast startup in the Windows settings. 
Thanks a lot for your help, I appreciate it! Have a great day :)



#11 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 01 November 2016 - 04:10 PM

Well,

 

another crash. This time WinDbg says it was probably caused by raspppoe.sys. Also I believe it might've something to do with CCleaner (probably the version I was using (5.22)). In the time, where I haven't got any Blue Screens, I didn't use it. Now I used it and I got a crash. Have you heard something like this before? I'll update it and hope it was a temporary bug in that version. 

 

 

Attached File  110116-25375-01.zip   224.74KB   1 downloads



#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:04:23 PM

Posted 02 November 2016 - 04:25 AM

I just noticed that you had previously uploaded another minidump (and I apologize for missing it)

They both point to networking issues.

 

My first concern is HotSpotShield.  Although I haven't seen issues with it since the days of W7, back then it caused a lot of BSOD's.

It is present in all of the memory dumps - so it's a strong possibility here.  Please temporarily uninstall it to see if that helps.

 

Also, your Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller networking drivers date from 2013.

Please:

- download a fresh set of networking drivers from the Gigabyte support site for your motherboard.  ensure that the are the latest, W10 compatible drivers available

- uninstall the networking drivers from Control Panel...Programs and Features.  If not uninstallable from there, then uninstall them from Device Manager (remove the software if that choice is offered).

- install the freshly downloaded drivers

- monitor for further BSOD's

 

CCleaner is a remarkably stable tool.  If it's causing BSOD's, there's not evidence of it in the memory dumps.

I'd suggest trying to run Driver Verifier in order to verify the problem drivers on the system

Please follow the suggestions here:  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:
**************************Tue Nov  1 16:35:11.870 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110116-25375-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:0 days 6:07:31.579
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
Probably caused by :raspppoe.sys ( raspppoe+10fa )
BugCheck 9F, {4, 12c, ffffa4830a482040, fffff80223cfd980}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffa4830a482040, The thread currently holding on to the Pnp lock.
Arg4: fffff80223cfd980, nt!TRIAGE_9F_PNP on Win7 and higher
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_4_raspppoe!unknown_function
CPUID:        "Intel® Core™ i5-3470 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3203
  BIOS Version                  F13
  BIOS Release Date             09/19/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77M-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 19 17:21:57.841 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\102016-26875-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
System Uptime:0 days 5:45:26.548
Probably caused by :ndis.sys ( ndis!ndisPauseFilterInner+7078 )
BugCheck 9F, {3, ffffd1827a683770, fffff802d6c80960, ffffd18280b52e10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd1827a683770, Physical Device Object of the stack
Arg3: fffff802d6c80960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd18280b52e10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!ndisPauseFilterInner
CPUID:        "Intel® Core™ i5-3470 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3203
  BIOS Version                  F13
  BIOS Release Date             09/19/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77M-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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 Nov  1 16:35:11.870 2016 (UTC - 4:00)**************************
L1C63x64.sys                Tue Jul 16 02:56:31 2013 (51E4EE9F)
iaStorA.sys                 Fri May  2 19:06:56 2014 (53642510)
VClone.sys                  Sat May  3 12:53:40 2014 (53651F14)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
PROCMON23.SYS               Mon May 25 20:35:46 2015 (5563BFE2)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
viahduaa.sys                Tue Aug 18 03:38:56 2015 (55D2E110)
ICCWDT.sys                  Sun Sep 20 03:59:19 2015 (55FE6757)
mbamchameleon.sys           Wed Jan 27 18:48:35 2016 (56A95753)
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 19 17:21:57.841 2016 (UTC - 4:00)**************************
hssdrv6.sys                 Fri Sep 18 17:42:05 2015 (55FC852D)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys                Sat Oct  1 15:08:52 2016 (57F009C4)


http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
PROCMON23.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=mbam.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.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=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=hssdrv6.sys
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 Oklearz

Oklearz
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:23 PM

Posted 02 November 2016 - 10:19 AM

Hey, 

 

I already said in a previous post that I already uninstalled HotSpotShield, just like I said that I already have the newest network driver (which is unfortunately for Windows 8.1, but it worked flawlessly so far (of course except the blue screens it caused)). So I guess it might've been HotSpotShield or Evolve that caused those BSODs, since I haven't got a crash since I uninstalled them. 

The crash yesterday was caused by something different (raspppoe.sys) and I will investigate it and try to fix it in case I get the same crash caused by that driver again. At the moment I'm hoping that the latest crash was a blue screen that won't appear again. 

My next post will come when I repeatedly get bluescreens again (which will hopefully never happen)

Still thanks for the info and your help!



#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:04:23 PM

Posted 03 November 2016 - 04:57 AM

Yes you did say that you uninstalled HotSpotShield in a previous post.

Yet the driver was still present in the 19 Oct memory dump

 

It was not present in the 31 Oct memory dump - so I hope that it is gone for good.

 

As to the latest memory dump, that's where I suggest that you uninstall/reinstall your networking drivers and, if that doesn't fix it, that you try Driver Verifier to help identify the problem driver.


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