Solved BOSD on my GT72Pro Notebook - Please help!

phila delphia · Dec 30, 2014

Update: I will not be able to uninstall Dragon Gamong Center which is the reason for the winio64 as this center is the only chance to switch between the internal and dedicated GPU...

Best regards

Phil

P.S.: Also - without using Verifier I had no bluescreen in nearly one week now.

usasma · Dec 30, 2014

In general, there's 2 ways to try to fix BSOD's.
The first is to fix one thing at a time and see if that helps.
The second is to fix all the things that might be wrong with the system.
The second way is faster than the first way - and that's why I use it.

As for reinstalling the stuff, don't worry about it.
I asked about it because I wasn't certain that you had removed it or not.
The location of the drivers isn't all that important, although the drivers not being in the drivers directory does suggest that it's the MSI Command utilities stuff that's causing it.

I'm glad you got a laugh out of my system specs. I have system problems just like most people, and putting them in the specs helps to show that problems can exist everywhere!

I had no other clue about the Audials software (other than it's age). I'm glad that you recognized that they all belonged to the same software - that makes their presence a lot more significant. Also, it's freezing your computer is a significant find in our analysis. FYI - often when fixing BSOD's we'll get black screen errors or freezes after we stop the BSOD's. This is usually indicative of a problem that's not just caused by one thing alone (for example, it could be that the Audials software is especially unstable with the Afterburner type drivers - thereby causing multiple problems).

FWIW - I prefer to remove (uninstall) the software rather than update it.
That way you can see if it stops the problems immediately.
Then, later on, if you want the software back, you can install a fresh copy and see if it causes any problems then.

The Audials memory dumps are different from the other memory dumps. In short, the others are from BSOD errors that occur in the kernel memory space, while the Audials dump is from application crashes in the user memory space. As such, these are interpreted differently (and use different commands than the kernel space dumps).

I analyze kernel space dumps. I'm not very adept at analyzing user space dumps - but I sometimes can gain a few clues from them (if available). In general the 2 are separate, but there are limited ways for user mode process' to communicate with kernel mode device drivers (you'll see people saying that user mode stuff can't cause a BSOD - and this is why).

The clue that I saw in this one was:

06390000 063f9000 DownloadManager DownloadManager.dll Mon Oct 07 08:55:19 2013 (52525AD7)

What this meant to me is that 1) it was very close to the crash itself (in the stack text), and 2) that it involves the network (download manager). And in post #17 I saw that there was network involvement in the verifier enabled crashes. While this isn't a definite conclusion, it does give us reason to remove the Audials software (temporarily) in order to see if it stops the freezes/BSOD's.

Now, verifier isn't a tool to be used at all times. It's specifically designed to stress problem drivers. It is conceivable that a properly working driver can react badly to the stress that Driver Verifier places on them. As such, I don't suggest using it until you have a problem that calls for it's use. It won't cause any harm, it just may lead you onto a path that's not related to the problem that you're experiencing (the BSOD's that happen when verifier isn't running).

I'll work first with your WinDbg analysis of the last memory dump.

First, please note that this isn't a Driver Verifier Enabled memory dump. Since verifier was running when it happened, there's a couple of possibilities here. Basically it's either a driver problem or a hardware problem - but we're not sure about either.

The memory dump shows that it can't get symbols for bwcW8x64.sys
This is a 3rd party (non-Microsoft) driver, so that's not unusual
But what is unusual is that it's a driver involved in networking - and it's mentioned in the memory dump.
The first time it's mentioned is that the debugger can't find symbols for it. This isn't a definite blame, but it's being shown in the dump so there must be some sort of involvement.
The second time it's mentioned is in the very next line where it's being blamed as the probably cause.

The ntstatus error code (0xc0000409) is for a buffer overrun - and the BSOD error itself is:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.

I can't recall if you've done the suggested anti-malware checks - but if not, please try several of these free scanners: Free Online AntiMalware Resources (the list is older so some of them may not work w/Win8).

Then, please replace the bwcW8x64.sys driver. To do this:
- download (but do not install) a fresh copy of the latest, Win8.1 compatible version of the Killer Bandwidth Control Filter Driver.
It's in the lan_bigfoot_8.1.0.23_1.1.44.1048 package_0x54907e58_w81700.zip package (under LAN driver at the download site)
- uninstall the current Killer drivers (and then verify that the bwcW8x64.sys driver has been removed - it's dated 13 August of 2014)
- then install the freshly downloaded drivers (and verify that the bwcW8x64.sys driver has been installed - it'll be dated from June 27 of 2014) Please note that this driver is older than the one currently on your system - so the newer one may have been removed, or it there may be a newer version in one of the other MSI downloads.
- monitor for further BSOD's

Here's the analysis that I did. It's essentially the same thing as yours is:

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Mon Dec 29 09:43:20.686 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122914-58562-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 0:08:05.512[/B]
*** WARNING: Unable to verify timestamp for bwcW8x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW8x64.sys
Probably caused by :[B]bwcW8x64.sys ( bwcW8x64+3968 )[/B]
BugCheck [B]139, {3, ffffd000259e4e90, ffffd000259e4de8, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000259e4e90, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000259e4de8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  360sd.exe
FAILURE_BUCKET_ID: [B]0x139_3_bwcW8x64+3968[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Mon Dec 29 09:43:20.686 2014 (UTC - 5:00)**************************
[COLOR=RED][B]MBfilt64.sys               Thu Jul 30 23:40:32 2009 (4A7267B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys              Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]winio64.sys                Fri Jun  4 00:08:03 2010 (4C087C23)[/B][/COLOR]
GEARAspiWDM.sys            Thu May  3 15:56:17 2012 (4FA2E2E1)
tbhsd.sys                  Tue Oct  9 18:01:42 2012 (50749EC6)
rsvcdwdr.sys               Tue Oct  9 18:36:49 2012 (5074A701)
[COLOR=RED][B]RTCore64.sys               Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
intelppm.sys               Thu Aug 22 04:46:35 2013 (5215CFEB)
RrNetCapFilterDriver.sys   Fri Nov  1 11:51:24 2013 (5273CDFC)
TeeDriverx64.sys           Wed Nov 27 12:56:32 2013 (52963250)
360Box64.sys               Fri Nov 29 01:51:33 2013 (52983975)
RtsPer.sys                 Fri Feb 21 02:35:56 2014 (530701DC)
SAlphaPS264.sys            Wed Mar  5 10:00:39 2014 (53173C17)
[COLOR=RED][B]e22w8x64.sys               Wed Mar 26 11:58:37 2014 (5332F92D)[/B][/COLOR]
360AntiHacker64.sys        Sun Apr 20 23:48:04 2014 (535494F4)
360AvFlt.sys               Tue Apr 22 23:54:35 2014 (5357397B)
360Camera64.sys            Mon Apr 28 07:39:27 2014 (535E3DEF)
360FsFlt.sys               Wed May  7 05:34:14 2014 (5369FE16)
SteelBus64.sys             Tue May 27 12:42:05 2014 (5384C05D)
iwdbus.sys                 Tue Jun 17 17:54:22 2014 (53A0B90E)
nvhda64v.sys               Mon Jul 21 10:17:53 2014 (53CD2111)
Qcamainx64.sys             Fri Aug  8 02:04:41 2014 (53E46879)
btfilter.sys               Fri Aug  8 02:17:53 2014 (53E46B91)
bwcW8x64.sys               Wed Aug 13 12:58:49 2014 (53EB9949)
iaStorA.sys                Fri Aug 22 17:26:36 2014 (53F7B58C)
dump_iaStorA.sys           Fri Aug 22 17:26:36 2014 (53F7B58C)
RTKVHD64.sys               Tue Sep 16 06:44:17 2014 (54181481)
SynTP.sys                  Thu Oct  9 01:07:46 2014 (54361822)
Smb_driver_Intel.sys       Thu Oct  9 01:12:24 2014 (54361938)
nvvad64v.sys               Thu Nov 20 10:33:54 2014 (546E09E2)
nvlddmkm.sys               Thu Nov 20 18:01:23 2014 (546E72C3)
nvvadarm.sys               Thu Nov 20 18:16:18 2014 (546E7642)
[COLOR=RED][B]NvStreamKms.sys            Sat Nov 22 02:46:45 2014 (54703F65)[/B][/COLOR]
[/font]

usasma · Dec 30, 2014

PS - don't forget to turn Driver Verifier off. To do this, open up verifier.exe and select "Delete existing settings", then click on "Finish" and reboot for the settings to take effect.

phila delphia · Dec 30, 2014

Wow! Thank you! I am on it!

Best regards

Phil

P.S.:

usasma said:
I'm glad you got a laugh out of my system specs. I have system problems just like most people, and putting them in the specs helps to show that problems can exist everywhere!

You definitely achived that. But I liked those specs especially because the show that you don`t take yourself to serious and can have a laugh at yourself - that`s what impresses me with people.

phila delphia · Dec 30, 2014

Hi John!

I did as you said: I uninstalled all drivers Killer and checked that no one was present on the system anymore. Then I reinstalled the Killer Suite again. Now I got the Drivers with the Date you mentioned in these three locations:

Best regards

Phil

phila delphia · Dec 30, 2014

Hi John!

This afternoon after updating the networkdrivers I was full of hope, that this migth have been it (and perhaps it was part of?)

But now I cought another DUMP (see below) - this time without using verifier. Instead I was using "Audials" (the one whose three drivers I updated yesterday...).

Best regards

Phil

Update: And one more DMP this time while ideling - my analysis according to your method blames Qcamainx64.sys both times. The Driver seems to be part of the Killer Networ Suite/Drivers (see Picture)

Update: Third one - as well Qcamainx64 seems to be the bad guy.

Update: Oh, and have a Look what I did find:
MSI USA - Online Technical Support FAQ
BSOD ntoskrnl.exe PAGE_FAULT_IN_NONPAGED_AREA - Blue Screen - Windows 8
and again here in the forums
http://www.eightforums.com/bsod-cra...e_fault_in_freed_special_pool.html#post462007

I reverted to the most recent driver but disabled the Killer suite according to the MSI workaroud...

usasma · Dec 31, 2014

Interesting. There may be another issue with the Killer suite (the last one was with the Killer Network Manager several months ago).
Your research is very helpful!

The first link doesn't have a date associated with it, so I'm unsure if it was another response for the same problem from several months ago. It is a different procedure, so I suspect that it's another issue.

The second link may/may not be related, but it blamed the bluetooth drivers.
The last link is probably a video issue, but that's not 100% certain due to the limited amount of info that was presented.

As you've already updated the Qcamainx64.sys, I'd suggest that you wait and see if further BSOD's occur.
If not, then I'd guess that the Killer network service workaround that you described was the "fix".

Here's my analysis just FYI:

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Tue Dec 30 15:46:50.442 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\123014-5484-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 0:29:44.214[/B]
*** WARNING: Unable to verify timestamp for Qcamainx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamainx64.sys
Probably caused by :[B]Qcamainx64.sys ( Qcamainx64+103f1f )[/B]
BugCheck [B]1D2, {5010000, a76eb, 400a76eb, 41a680}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]Unknown bugcheck code (1d2)[/url]
Arguments: 
Arg1: 0000000005010000
Arg2: 00000000000a76eb
Arg3: 00000000400a76eb
Arg4: 000000000041a680
BUGCHECK_STR:  0x1D2
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1D2_Qcamainx64+103f1f[/B]
CPUID:        "Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2494[/B]
  BIOS Version                  E1781IMS.10D
  BIOS Release Date             09/15/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT72
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 30 14:36:57.363 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\123014-5796-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 0:26:16.134[/B]
*** WARNING: Unable to verify timestamp for Qcamainx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamainx64.sys
Probably caused by :[B]Qcamainx64.sys ( Qcamainx64+103f1f )[/B]
BugCheck [B]1D2, {5010000, a76eb, 400a76eb, 41a680}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]Unknown bugcheck code (1d2)[/url]
Arguments: 
Arg1: 0000000005010000
Arg2: 00000000000a76eb
Arg3: 00000000400a76eb
Arg4: 000000000041a680
BUGCHECK_STR:  0x1D2
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1D2_Qcamainx64+103f1f[/B]
CPUID:        "Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2494[/B]
  BIOS Version                  E1781IMS.10D
  BIOS Release Date             09/15/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT72
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 30 13:35:47.625 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\123014-5781-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 3:49:39.396[/B]
*** WARNING: Unable to verify timestamp for Qcamainx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamainx64.sys
Probably caused by :[B]Qcamainx64.sys ( Qcamainx64+103f1f )[/B]
BugCheck [B]1D2, {5010000, a76eb, 400a76eb, 41a680}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]Unknown bugcheck code (1d2)[/url]
Arguments: 
Arg1: 0000000005010000
Arg2: 00000000000a76eb
Arg3: 00000000400a76eb
Arg4: 000000000041a680
BUGCHECK_STR:  0x1D2
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1D2_Qcamainx64+103f1f[/B]
CPUID:        "Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2494[/B]
  BIOS Version                  E1781IMS.10D
  BIOS Release Date             09/15/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT72 2QE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Tue Dec 30 15:46:50.442 2014 (UTC - 5:00)**************************
[COLOR=RED][B]MBfilt64.sys               Thu Jul 30 23:40:32 2009 (4A7267B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys              Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]winio64.sys                Fri Jun  4 00:08:03 2010 (4C087C23)[/B][/COLOR]
GEARAspiWDM.sys            Thu May  3 15:56:17 2012 (4FA2E2E1)
tbhsd.sys                  Tue Oct  9 18:01:42 2012 (50749EC6)
rsvcdwdr.sys               Tue Oct  9 18:36:49 2012 (5074A701)
[COLOR=RED][B]RTCore64.sys               Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
ladfGSCamd64.sys           Mon Apr 15 14:39:12 2013 (516C4950)
ladfGSRamd64.sys           Mon Apr 15 14:39:15 2013 (516C4953)
intelppm.sys               Thu Aug 22 04:46:35 2013 (5215CFEB)
RrNetCapFilterDriver.sys   Fri Nov  1 11:51:24 2013 (5273CDFC)
TeeDriverx64.sys           Wed Nov 27 12:56:32 2013 (52963250)
360Box64.sys               Fri Nov 29 01:51:33 2013 (52983975)
RtsPer.sys                 Fri Feb 21 02:35:56 2014 (530701DC)
SAlphaPS264.sys            Wed Mar  5 10:00:39 2014 (53173C17)
[COLOR=RED][B]e22w8x64.sys               Wed Mar 26 11:58:37 2014 (5332F92D)[/B][/COLOR]
360AntiHacker64.sys        Sun Apr 20 23:48:04 2014 (535494F4)
360AvFlt.sys               Tue Apr 22 23:54:35 2014 (5357397B)
360Camera64.sys            Mon Apr 28 07:39:27 2014 (535E3DEF)
360FsFlt.sys               Wed May  7 05:34:14 2014 (5369FE16)
SteelBus64.sys             Tue May 27 12:42:05 2014 (5384C05D)
iwdbus.sys                 Tue Jun 17 17:54:22 2014 (53A0B90E)
Qcamainx64.sys             Tue Jun 24 15:51:51 2014 (53A9D6D7)
bwcW8x64.sys               Tue Jun 24 17:49:38 2014 (53A9F272)
btfilter.sys               Fri Aug  8 02:17:53 2014 (53E46B91)
iaStorA.sys                Fri Aug 22 17:26:36 2014 (53F7B58C)
dump_iaStorA.sys           Fri Aug 22 17:26:36 2014 (53F7B58C)
RTKVHD64.sys               Tue Sep 16 06:44:17 2014 (54181481)
igdkmd64.sys               Mon Sep 29 13:51:21 2014 (54299C19)
SynTP.sys                  Thu Oct  9 01:07:46 2014 (54361822)
Smb_driver_Intel.sys       Thu Oct  9 01:12:24 2014 (54361938)
nvvad64v.sys               Thu Nov 20 10:33:54 2014 (546E09E2)
[COLOR=RED][B]NvStreamKms.sys            Sat Nov 22 02:46:45 2014 (54703F65)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 30 13:35:47.625 2014 (UTC - 5:00)**************************
nvhda64v.sys               Mon Jul 21 10:17:53 2014 (53CD2111)
nvlddmkm.sys               Thu Nov 20 18:01:23 2014 (546E72C3)
nvvadarm.sys               Thu Nov 20 18:16:18 2014 (546E7642)
[/font]

phila delphia · Dec 31, 2014

usasma said:
The first link doesn't have a date associated with it, so I'm unsure if it was another response for the same problem from several months ago.

Yes, you are right. I searched for a date on the FAQ as well but I did not find it. The problem seems to be a older one indeed (especially as the newer Notebook models are not listed on that page) anyhow... I very first line states that all NB with Killer Lan/Wifi might expreience trouble.

But I guess we will see sooner or later ;-) And I`ll of course report any dumps.

Best regards and a happy new year 2015 for you and your familiy

Phil

P.S.: Is there a way I can "buy you a beer"?

usasma · Dec 31, 2014

Best regards to you and your family. I hope that you also have a happy new year!
Thanks for the thought about buying me a beer. I don't accept favors or donations though - as I do this for the love of helping others.
Good luck!

phila delphia · Jan 6, 2015

Hi John!

I was amlost about to close this thread. One week without any problem after I disabeled the Killer Suite.

Now today the following crash dump (without verifier and again while th PC was ideling):

View attachment 56241

Best regards

Phila

P.S.: Please have a look what I found after googeling the error source that windbg points to [Qcamainx64.sys ( Qcamainx64+100563 )]: There is a user in this forums that seems to suffer the same problem on a very similar machine: http://www.eightforums.com/bsod-crashes-debugging/56749-random-bsod-page-fault-nonpaged-area.html

P.P.S.: There meanwhile seem to be some more people with a similar problem: This post and the subsequent date from Dec 14.
MSI GS70 Stealth Pro Theard - Page 118

P.P.P.: I found and downloaded even mor recent driver for te Atheros Qualcomm - dating fomr Oct 9th 2014 fpr the wireless adapter. So let`s see

usasma · Jan 6, 2015

You're going to have to get rid of winio64.sys and RTCore64.sys - even if it's only temporarily. This is to see if they are involved with the crashes. Quite frankly, with the number of issues I've seen on MSI systems over the last several months, I just don't trust anything that MSI makes (without testing it first).

The most likely cause here is the Qcamainx64.sys driver.
But what is actually causing it?
Is it something that the driver is doing?
Is it a bug in the driver, or is it a corruption of the installed driver?
Is it something that another driver is doing in the Qcamainx64.sys driver's memory space?
Is the other driver showing up in the memory dump, or is it absent from the memory dump?
Is it something caused by the hardware?
Is it an incompatibility w/Win8.1?

The easiest way to test all of this would be to:
- remove the wireless drivers
- disable the wireless card in the UEFI/BIOS
- use a wired connection for the next week or two in order to test the system.

Another way to test this would be to:
- remove the wireless drivers
- disable the wireless card in the UEFI/BIOS
- use a wireless USB device (be sure that it's Win8.1 compatible) for the next week or two in order to test the system.
(if you don't have one of these, maybe you can purchase one from a shop that will allow you to return it if it's not needed).

usasma · Jan 6, 2015

Oops! I forgot to post the analysis:

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Tue Jan  6 06:27:38.181 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010615-15828-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]4 days 22:43:29.053[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for Qcamainx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamainx64.sys
Probably caused by :[B]Qcamainx64.sys ( Qcamainx64+100563 )[/B]
BugCheck [B]50, {ffffe00128dbc000, 0, fffff800883cf325, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arguments: 
Arg1: ffffe00128dbc000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800883cf325, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]AV_Qcamainx64+100563[/B]
CPUID:        "Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2494[/B]
  BIOS Version                  E1781IMS.10D
  BIOS Release Date             09/15/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT72 2QE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Tue Jan  6 06:27:38.181 2015 (UTC - 5:00)**************************
[COLOR=RED][B]MBfilt64.sys               Thu Jul 30 23:40:32 2009 (4A7267B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys              Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]winio64.sys                Fri Jun  4 00:08:03 2010 (4C087C23)[/B][/COLOR]
GEARAspiWDM.sys            Thu May  3 15:56:17 2012 (4FA2E2E1)
tbhsd.sys                  Tue Oct  9 18:01:42 2012 (50749EC6)
rsvcdwdr.sys               Tue Oct  9 18:36:49 2012 (5074A701)
[COLOR=RED][B]RTCore64.sys               Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
ladfGSCamd64.sys           Mon Apr 15 14:39:12 2013 (516C4950)
ladfGSRamd64.sys           Mon Apr 15 14:39:15 2013 (516C4953)
intelppm.sys               Thu Aug 22 04:46:35 2013 (5215CFEB)
RrNetCapFilterDriver.sys   Fri Nov  1 11:51:24 2013 (5273CDFC)
TeeDriverx64.sys           Wed Nov 27 12:56:32 2013 (52963250)
360Box64.sys               Fri Nov 29 01:51:33 2013 (52983975)
RtsPer.sys                 Fri Feb 21 02:35:56 2014 (530701DC)
SAlphaPS264.sys            Wed Mar  5 10:00:39 2014 (53173C17)
[COLOR=RED][B]e22w8x64.sys               Wed Mar 26 11:58:37 2014 (5332F92D)[/B][/COLOR]
360AntiHacker64.sys        Sun Apr 20 23:48:04 2014 (535494F4)
360AvFlt.sys               Tue Apr 22 23:54:35 2014 (5357397B)
360Camera64.sys            Mon Apr 28 07:39:27 2014 (535E3DEF)
360FsFlt.sys               Wed May  7 05:34:14 2014 (5369FE16)
SteelBus64.sys             Tue May 27 12:42:05 2014 (5384C05D)
iwdbus.sys                 Tue Jun 17 17:54:22 2014 (53A0B90E)
nvhda64v.sys               Mon Jul 21 10:17:53 2014 (53CD2111)
Qcamainx64.sys             Fri Aug  8 02:04:41 2014 (53E46879)
btfilter.sys               Fri Aug  8 02:17:53 2014 (53E46B91)
bwcW8x64.sys               Wed Aug 13 12:58:49 2014 (53EB9949)
iaStorA.sys                Fri Aug 22 17:26:36 2014 (53F7B58C)
dump_iaStorA.sys           Fri Aug 22 17:26:36 2014 (53F7B58C)
RTKVHD64.sys               Tue Sep 16 06:44:17 2014 (54181481)
SynTP.sys                  Thu Oct  9 01:07:46 2014 (54361822)
Smb_driver_Intel.sys       Thu Oct  9 01:12:24 2014 (54361938)
nvvad64v.sys               Thu Nov 20 10:33:54 2014 (546E09E2)
nvlddmkm.sys               Thu Nov 20 18:01:23 2014 (546E72C3)
nvvadarm.sys               Thu Nov 20 18:16:18 2014 (546E7642)
[COLOR=RED][B]NvStreamKms.sys            Sat Nov 22 02:46:45 2014 (54703F65)[/B][/COLOR]
[/font]

phila delphia · Jan 7, 2015

Hi John!

The MSI Support has answered in the meantime they admit:

Dear Philipp, Thank you for reporting in detail. We are aware of such issue on few models, a
cause of BSOD is the incompatibility of driver. Will you try to update the
driver and killer suit to the lastest? Thank you for contacting us

.[/QUOTE]

Here is my answer to them:

Hi! Thank you for the response. Unfortunately the driver you offer at your site ist NOT the latest and it caused the same issues the one that came installed. I donwloaded the very latest package form Atheros Qualcomm yesterday and recieved an update via windows this morning. My friends also suspect the MSI Afterburner drivers and the Windows Gaming Center drivers to cause Probelms... What can you tell me about this? Best regards Phil

Click to expand...

As I mentioned above I installed a driver dating to Oct 10th 2014 directly form Qualcomm yesterday. Today I even got an uptade via Microsoft Updater for the Qualcomm... I`ll be checking this package first. If the probelm persist I will do as you say - just to verify.

Best regards

Phil

usasma · Jan 7, 2015

I'm happy to hear that you got confirmation from MSI about this.
I'll look forward to hearing your results.

EDIT: BTW, I've updated the DRT (Driver Reference Table) with the information that you provided: Driver Reference Table - Qcamainx64.sys

Yoggin · Jan 11, 2015

phila delphia said:
Hi John!

The MSI Support has answered in the meantime they admit:

Dear Philipp, Thank you for reporting in detail. We are aware of such issue on few models, a
cause of BSOD is the incompatibility of driver. Will you try to update the
driver and killer suit to the lastest? Thank you for contacting us

Click to expand...

.[/QUOTE]

Here is my answer to them:

Hi! Thank you for the response. Unfortunately the driver you offer at your site ist NOT the latest and it caused the same issues the one that came installed. I donwloaded the very latest package form Atheros Qualcomm yesterday and recieved an update via windows this morning. My friends also suspect the MSI Afterburner drivers and the Windows Gaming Center drivers to cause Probelms... What can you tell me about this? Best regards Phil

Click to expand...

As I mentioned above I installed a driver dating to Oct 10th 2014 directly form Qualcomm yesterday. Today I even got an uptade via Microsoft Updater for the Qualcomm... I`ll be checking this package first. If the probelm persist I will do as you say - just to verify.

Best regards

Phil

Click to expand...

I have the same problem on my MSI GS60, where did you find the new package from atheros qualcomm? Ive been trying to find it on their site but cant seem to find anything directly from them...

phila delphia · Jan 12, 2015

Yoggin said:
I have the same problem on my MSI GS60, where did you find the new package from atheros qualcomm? Ive been trying to find it on their site but cant seem to find anything directly from them...

Hi Yoggin! Did you open up an own BSOD thread according to the idea in the forums? Perhaps it is an other Kind of BSOD? The guys on thins froums will really help you along.

Anyhow: I tried to find the driver I mentioned on the Atheros Qualcomm Site - but had no luck. I deemed this curious. Lucky I did did not delete the suite after install. So here is the link. https://www.dropbox.com/s/34awdatdqewj8xy/KillerSuite_1.1.48.1376_Win7_Win81.exe?dl=0

I had no problems since the update. Yet I will not close the thread until some mor time has passed. As the last BSOD appeared just when I felt save... If there should be further problems MSI allready offered to do an hardwarecheck.

Best regards

Phil

Yoggin · Jan 15, 2015

phila delphia said:
Yoggin said:

I have the same problem on my MSI GS60, where did you find the new package from atheros qualcomm? Ive been trying to find it on their site but cant seem to find anything directly from them...

Click to expand...

Hi Yoggin! Did you open up an own BSOD thread according to the idea in the forums? Perhaps it is an other Kind of BSOD? The guys on thins froums will really help you along.

Anyhow: I tried to find the driver I mentioned on the Atheros Qualcomm Site - but had no luck. I deemed this curious. Lucky I did did not delete the suite after install. So here is the link. https://www.dropbox.com/s/34awdatdqewj8xy/KillerSuite_1.1.48.1376_Win7_Win81.exe?dl=0

I had no problems since the update. Yet I will not close the thread until some mor time has passed. As the last BSOD appeared just when I felt save... If there should be further problems MSI allready offered to do an hardwarecheck.

Best regards

Phil

Hi Phil,

Thanks alot for the link, have been searching alot for this update but it seemes like the Atheros site don't contain any Killer Suite files whatsoever anymore, wierd. I have been analyzing my BSOD files and tried to fix this problem for some days before I stumpled on your post. After reading it and looking at all info I concluded that we had the same problem, the BSOD files are almost identical so I thought I would give it a try with the update you found.

Since installing the update I haven't had a single BSOD so I'm hoping this has fixed it, as I got a BSOD as soon as I started any process that demanded some bandwith over the wifi before Im optimistic about the problem being fixed.

If the problems comes back I will open up my own thread to try and fix this problem.

phila delphia · Jan 15, 2015

Hi Yoggin!

I am glad, my problem an Johns analysis did offered you some help - or at least the consolation that you are not alone with your issue. There are three things I can report for now:

1.) I had no BSOD since I installed the updated. Even though I must admit, that I was to gutless to check with verifyer.
2.) It is really curious that I could download the driver from the Qualcomm Site - but later on I got an error when loading the bookmarked site?!?!
3.) After I told MSI that I tried to fix the BSOD with an factory reset they mentioned that it also could be an hardware issue (even thought this does not take into account that the factory reset installs the old - and crappy? - drivers ;-).
4.) I communicated with MSI to send the notebook in for a checkup if the BSOD will continue.

Best regards

Phil

P.S.: The MSI support is always very short. I wish they`d care about their customers issues as Jhon and the other guys on this forums do.

usasma · Jan 16, 2015

FYI - I have recently seen (over the last 4 or 5 days) that Windows Updates is offering a newer version of the Qualcomm wifi driver. I suspect that this is a move by Qualcomm to get the older driver out of circulation more rapidly.

Open up Windows Update (press the Win and R keys at the same time, then type in "wuapp" (without the quotes) and press Enter)
Check the optional updates to see if the Qualcomm driver is present.

phila delphia · Jan 16, 2015

usasma said:
FYI - I have recently seen (over the last 4 or 5 days) that Windows Updates is offering a newer version of the Qualcomm wifi driver. I suspect that this is a move by Qualcomm to get the older driver out of circulation more rapidly.

Open up Windows Update (press the Win and R keys at the same time, then type in "wuapp" (without the quotes) and press Enter)
Check the optional updates to see if the Qualcomm driver is present.

Hi John!

Thank you very much for the information! This sounds good (and perhaps correspondents with the fact that the "older" drivers are not found in the Qualcomm download section.)

The update is allready out I suspect? Or will it take some more time in Germany? As I did not get an seperate Qualcomm Update up to now.

Best regards

Phil

Solved BOSD on my GT72Pro Notebook - Please help!

New Member

My Computer

Mr. Cranky Pants

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer