BSOD

cbys · May 30, 2015

Hello kind gentlepeople

I've been experiencing BSODs today, usually when watching stuff on VLC. THe first BSOD occurred within 5 mins of launching a video whereas the second one lasted within 45 mins. Haven't installed anything new apart from Windows updates, some Steam games and Tales of the Borderlands. Here is the file from DM Log Collector. I'm running an AlienwareM17X R3 with an AMD6990m with 8gb RAM.

blueelvis · May 31, 2015

Hi cbys & Welcome to the forums ^_^,

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

IRQL_UNEXPECTED_VALUE (c8)
The processor's IRQL (Interrupt ReQuest Level) is not what it should be at this time. This is usually caused by a lower level routine changing IRQL for some period
and not restoring IRQL at the end of that period (eg acquires spinlock but doesn't release it).

The error is pretty self explanatory even though this is the first time, I have seen this. As usual, we check the stack for some clues -

Code:

0: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd001`a69d4488 fffff800`7c3f4376 nt!KeBugCheckEx
01 ffffd001`a69d4490 fffff800`61ed3936 nt!KeExpandKernelStackAndCalloutInternal+0x1d1b6
02 ffffd001`a69d4580 fffff800`61cd3a53 tcpip+0x6f936
03 ffffd001`a69d4600 fffff800`61cd3e7f ndis!ndisMIndicateNetBufferListsToOpen+0x123
04 ffffd001`a69d46c0 fffff800`61cd46b2 ndis!ndisMTopReceiveNetBufferLists+0x22f
05 ffffd001`a69d4750 fffff800`64470e27 ndis!NdisMIndicateReceiveNetBufferLists+0x732
06 ffffd001`a69d4940 ffffe001`94939e70 [COLOR=#FF0000][B][U]Ak27x64[/U][/B][/COLOR]+0x1fe27
07 ffffd001`a69d4948 00000000`00000001 0xffffe001`94939e70
08 ffffd001`a69d4950 00000000`00000000 0x1

The driver causing the problems is a part of the Killer Ethernet which is known to cause problems.

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

Code:

**************************Sun May 31 06:11:12.638 2015 (UTC + 5:30)**************************
[COLOR=#FF0000][U][B]lirsgt.sys                  Sun Mar  7 01:23:01 2004 (404A2C1D)
wdcsam64.sys                Wed Apr 16 14:09:08 2008 (4805BB2C)
WinRing0x64.sys             Sat Jul 26 18:59:37 2008 (488B26C1)
atksgt.sys                  Mon Oct 20 13:20:38 2008 (48FC384E)
[/B][/U][/COLOR]LGBusEnum.sys               Tue Nov 24 07:06:48 2009 (4B0B38B0)
LGVirHid.sys                Tue Nov 24 07:06:48 2009 (4B0B38B0)
HECIx64.sys                 Wed Oct 20 05:03:43 2010 (4CBE2AD7)
[COLOR=#0000FF][B][U]Ak27x64.sys                 Wed Dec  7 22:43:57 2011 (4EDF9ED5)
[/U][/B][/COLOR]RtsPStor.sys                Thu Mar 29 12:39:33 2012 (4F740AAD)
GEARAspiWDM.sys             Fri May  4 01:26:17 2012 (4FA2E2E1)
npf.sys                     Fri Mar  1 07:01:24 2013 (513004EC)
L1C63x64.sys                Mon Apr  1 08:45:17 2013 (5158FBC5)
ladfGSCamd64.sys            Tue Apr 16 00:09:12 2013 (516C4950)
ladfGSRamd64.sys            Tue Apr 16 00:09:15 2013 (516C4953)
LGSHidFilt.Sys              Thu May 30 20:46:33 2013 (51A76D51)
iaStorAV.sys                Thu Aug  1 05:30:49 2013 (51F9A531)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
bcbtums.sys                 Fri Oct 18 02:15:30 2013 (52604C6A)
mwac.sys                    Wed Jun 18 07:37:00 2014 (53A0F444)
AMDACPKSL.SYS               Sun Jun 22 08:01:43 2014 (53A6400F)
AtihdWB6.sys                Sun Jun 22 08:02:00 2014 (53A64020)
mbam.sys                    Wed Sep  3 23:20:25 2014 (540754E1)
aswRvrt.sys                 Thu Nov  6 18:23:22 2014 (545B6F42)
aswVmm.sys                  Thu Nov  6 18:23:31 2014 (545B6F4B)
aswRdr2.sys                 Thu Nov  6 18:24:02 2014 (545B6F6A)
aswHwid.sys                 Thu Nov  6 18:25:01 2014 (545B6FA5)
aswSP.sys                   Thu Nov  6 18:39:55 2014 (545B7323)
aswStm.sys                  Thu Nov  6 18:41:00 2014 (545B7364)
atikmpag.sys                Fri Nov 21 07:38:54 2014 (546E9EB6)
atikmdag.sys                Fri Nov 21 08:00:27 2014 (546EA3C3)
aswSnx.sys                  Fri Nov 21 16:47:12 2014 (546F1F38)
aswMonFlt.sys               Mon Jan  5 17:26:56 2015 (54AA7C08)
MBAMSwissArmy.sys           Fri Jan  9 08:15:43 2015 (54AF40D7)

Kindly rename all the drivers highlighted in RED since they are old and some of them (WDCSam64.sys & WinRing0x64.sys) are very well known to cause problems. Just do a system wide manual search for these drivers and then rename them. Once you have renamed these drivers, reboot the system and make sure that additional copies of these drivers are not created. If they are created, kindly let me know.
Kindly follow the below guide (Thanks usasma! ) and see if it solves the crashes or not. Please follow Note 2 first and if the problem is still not resolved then follow Note 1. -

At times the Killer Network Manager may cause BSOD problems:

NOTE1:Link thanks to blueelvis (15Oct2014): https://forum-en.msi.com/index.php?topic=178064.0 This is a method for removing all the network software and only installing the driver. Perfect for those issues that can't be resolved any other way!

NOTE2: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:

First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
Right click on it again and this time select "Properties"
In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

Next, open Task Manager (right click on TaskBar and select "Task Manager")
Click on the "More details" dropdown (if present)
Click on the "Startup" tab
Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
Finally, restart the system in order for the changes to take affect.

At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:

It may be that the instructions aren't stopping everything.
In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
"c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

Here's some things to try
1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

Just FYI - here are the MSI workaround instructions: MSI USA - Online Technical Support FAQ

Click to expand...

Let me know how it goes ^_^

-Pranav

BSOD

cbys

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One