BSOD while playing on msi gt70 dragon edition 2

[m4d]

hello everyone ,,, 2 days ago i bought a new MSI GT70 DRAGON EDITION 2
system specs :~
i7-4700mq processor
nividia geforce gtx780m
750gb +128g ssd(super raid)
ram 32gb
os: windows 8
...

and i got BSOD like 5 times until now while playing league of legends and each time with different error msg (like IRQL_NOT_LESS_OR_EQUAL or UNEXPECTED_KERNEL_MODE_TRAP)

and i want to upload the Dump File but i dont know what type of write debugging information i should use (is it the Kernel memory dump or the small memory dump) anyway i upload the default one which is automatic memory dump

 

[ectech]

Hello m4d,

Let's start with a little bit of maintenance. Please remove Android Bluestacks from the system.

Next, run Windows Update & install any updates available.

 

[kaelaan]

Hi m4d,

I bought the same laptop myself about 3 weeks ago. Mine was the same processor and came with a 1TB data drive and a 384MB RAID 0 across three 128MB micro SSD drives. Nice computer, but it's been nothing but problems since day 1 - all driver related BSODs.

The two major device driver issues I had revolved around the Killer Network e2200/Killer-N 1202 drivers as well as the Intel 4600 graphics chip drivers. The Killer network drivers tended to be all of the place with the BSOD codes, but happened most often when putting a lot of load on the NIC or WLAN. Installing various games over an internet connection (especially through Steam) would result in repeated BSODs. The BSODs caused by the Intel 4600 were often pointing to the GDI or Aero functions in the stack trace.

This is what I did to resolve my issues (hopefully, I'm still anticipating an anoying BSOD).

Installing the latest Intel driver from Intel's website (or Microsoft's site) seemed to correct BSODs related to the Intel graphics chip. The MSI drivers pre-installed on the laptop and the ones currently on their website are not the latest and will cause problems at random times. The good thing was these were infrequent.

I have tried various driver packages from Qualcomm to correct the Killer Network driver issues. Not a single one works. The issues seem to revolve around the filters that tie into the Network Manager. The Network Manager is the custom service and application that throttles the available network throughput by tying into the TCP driver (tcpip.sys). It causes too many headaches and becomes rather unstable under high loads. So, some of the people over at the MSI forums have creates a custom driver package (slightly old by a few months) that does not include any of the custom Killer Network Manager software.

You can find it at https://forum-en.msi.com/index.php?topic=174228.0

You need to uninstall the Killer Network software first. Basically, uninstall the two Qualcomm installations in the add/remove programs. Restart the laptop. Locate the devices (now no longer working) in Device Manager. Manually update the drivers using the package found at the MSI forums. Restart again and connect to your wireless network at this point (unless you use LAN). The bluetooth driver is also bundled into the Killer Network software. When you uninstall the Qualcomm software, your bluetooth will be replaced with the Microsoft generic adapter which seems to work.

The windows update site does give you an optional update to update the Microsoft generic bluetooth adapter with the latest Qualcomm driver without the network manager. However, I don't want to jinx anything just yet and I want to leave the laptop like this for now until I know that these drivers are stable.


Another note - DO NOT upgrade the laptop to Windows 8.1. The system will repeatedly BSOD randomly even with the latest BIOS and EC firmware updates. Several of us have tried and pretty much the consensuses is that we had to restore the laptop and stick to Windows 8 until the Intel and Qualcomm drivers become more stable.

 

[m4d]

thank you guys so much for replying ... this issue is driving me crazy
anyway i'll update you later with the details

 

[m4d]

HELLO kaelaan

,, i did download the driver you gave me and it worked for a while but i just got bsod again 10 minutes ago

and this is the dump file ​

 

[m4d]

and this is one i just did after downloading windows updates

 

[m4d]

guys please tell me if it's something related to the hardware so i could replace the laptop itself within the given days because i bought it couple days ago

 

[ectech]

The most recent crash points to your wireless card. Open Device Manager and disable the wireless. Use a wired connection to test if this stops the system from crashing.

View attachment 34639

As you can see from the picture, the driver is attempting to use IRQ 4294967289. Most computers only use IRQs up to 15. There is clearly something wrong with the driver.

Test the system with only a wired connection and post any details you find.

 

[kaelaan]

Hi m4d,

It sounds like one of the filters from the network manager is still active. Download the 64-bit version of the killer cleaner found at Driver Downloads | Qualcomm Atheros, Inc. and the latest drivers for e2200/wireless-N 1102 (64-bit).

Manually uninstall the drivers I had you install. Reboot.

Run the killer cleaner. Reboot.

Install the latest drivers. Reboot.

Uninstall the latest drivers from the Uninstall Programs in your control panel. Reboot.

Run the kill cleaner again. Reboot.

Install the drivers I had you manually install.​

I realize that it's a pain, but wireless-N driver is causing the crash. This is usually because one of the filters installed by Killer Network Manager is still left behind.

I still haven't had any crashes for a while now. However, I will never say never.

ectech - FFFFFFF9 is the standard IRQ to be used for the Qualcomm Atheros Wireless-N 1102. I'm pretty sure it's a virtual device that is sharing the same hardware along with the Qualcomm Atheros e2200. Which is why, both wired or wireless will cause the same issues when put under high load.

My personal opinion is that it is a design flaw either in the driver or the device itself. To make it worse, Bigfoot (the original design manufacturer) was acquired by Qualcomm and has since shut down the website as of the 1/1/2014. This is why killergaming.com has been down for the past week. Hopefully, Qualcomm provides a fix.

What I have noticed is that the driver wants to manage the Windows TCP/IP stack for all applications. So programs that have their own process management for network activity seem to be at higher risk in causing a problem with the drivers. A perfect example of this is either chrome.exe or steam.exe. Both of which use an internal task management and memory system that split the multiple downloads into separate tasks (in the case of chrome) or threads (in the case of steam). Which would explain a lot of the wacky BSODs I used to get (KERNEL_SECURITY_CHECK_FAILURE, DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL) all of which would point to either the killer drivers themselves or the tcpip.sys.

It's actually a common theme with various MSI laptops once you start putting them through their paces. You can try RMA'ing the laptop, but since it's intermittent and usually happens only when the NIC or WLAN is put under heavy load - I think you will get the laptop or replacement in the same condition.

Because this laptop cost me $2600 - if it happens again to myself, I will be removing (or disabling) the onboard LAN/WLAN and installing my own. I really don't want to be reduced down to a USB wireless network adapter.

 

[m4d]

thank you guys so much ,,, <3
i'll see and give you an updates

 

[m4d]

Hi m4d,

It sounds like one of the filters from the network manager is still active. Download the 64-bit version of the killer cleaner found at Driver Downloads | Qualcomm Atheros, Inc. and the latest drivers for e2200/wireless-N 1102 (64-bit).

Manually uninstall the drivers I had you install. Reboot.

Run the killer cleaner. Reboot.

Install the latest drivers. Reboot.

Uninstall the latest drivers from the Uninstall Programs in your control panel. Reboot.

Run the kill cleaner again. Reboot.

Install the drivers I had you manually install.​

I realize that it's a pain, but wireless-N driver is causing the crash. This is usually because one of the filters installed by Killer Network Manager is still left behind.

I still haven't had any crashes for a while now. However, I will never say never.

ectech - FFFFFFF9 is the standard IRQ to be used for the Qualcomm Atheros Wireless-N 1102. I'm pretty sure it's a virtual device that is sharing the same hardware along with the Qualcomm Atheros e2200. Which is why, both wired or wireless will cause the same issues when put under high load.

My personal opinion is that it is a design flaw either in the driver or the device itself. To make it worse, Bigfoot (the original design manufacturer) was acquired by Qualcomm and has since shut down the website as of the 1/1/2014. This is why killergaming.com has been down for the past week. Hopefully, Qualcomm provides a fix.

What I have noticed is that the driver wants to manage the Windows TCP/IP stack for all applications. So programs that have their own process management for network activity seem to be at higher risk in causing a problem with the drivers. A perfect example of this is either chrome.exe or steam.exe. Both of which use an internal task management and memory system that split the multiple downloads into separate tasks (in the case of chrome) or threads (in the case of steam). Which would explain a lot of the wacky BSODs I used to get (KERNEL_SECURITY_CHECK_FAILURE, DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL) all of which would point to either the killer drivers themselves or the tcpip.sys.

It's actually a common theme with various MSI laptops once you start putting them through their paces. You can try RMA'ing the laptop, but since it's intermittent and usually happens only when the NIC or WLAN is put under heavy load - I think you will get the laptop or replacement in the same condition.

Because this laptop cost me $2600 - if it happens again to myself, I will be removing (or disabling) the onboard LAN/WLAN and installing my own. I really don't want to be reduced down to a USB wireless network adapter.

the weird thing is. my friend bought the same laptop and he had no crashes at all .. thats why im thinking of changing it with another dragon edition 2 .. although if i'm going to change it i have to do it by tommorow because it's the last day for me
so what do you think .. should i get a new one or stick with this one and try to solve it

 

[kaelaan]

I hear that as well (mixed results), but I really think it also has to do with what they are using it for.

For example, even after upgrading to Windows 8.1 (which was a very buggy driver experience), I was able to play a heavily modded version of Minecraft (4GB memory in use) for hours at a time. I was also able to play Battlefield 4 with no issues at all. I only had issues with VMWare Workstation once before I updated to the latest Intel graphics driver (BSOD was pointing to GDI, which uses the Intel 4600).

As soon as I switch to steam games or do heavy browsing with Chrome (YouTube), the BSODs start flying.

It could very well be a bunch of faulty laptops, you can try your luck with swapping it out with another one. Myself, if I run into issues again, I may contact the local MSI repair center before I rip the back off myself.

 

[m4d]

The most recent crash points to your wireless card. Open Device Manager and disable the wireless. Use a wired connection to test if this stops the system from crashing.

View attachment 34639

As you can see from the picture, the driver is attempting to use IRQ 4294967289. Most computers only use IRQs up to 15. There is clearly something wrong with the driver.

Test the system with only a wired connection and post any details you find.

that's the problem i can't use wired connection at this time


.....


kaelaan ,, i tried that but i just got bsod 30 minutes ago i attached the dump file ..
,,
although in the custom driver(the one without killer network software) i got 2 folders 1-killer e220x 2-killer wireless N ,, i installed it manually in device manager the killer e220x in the Ethernet device and the killer wireless-N in the network device am i doing it right ?

 

[kaelaan]

Yeah ... that's correct. There are two folders, one for the wireless and one for the wired driver. I have a feeling that you may want to swap out the laptop tomorrow.

Btw, are you consistently able to reproduce the BSOD (over time) by performing specific tasks? If so, you should try the same exact things on the swapped out laptop.

 

[m4d]

oh ok thanks .. hopefully they agree on swapping the laptop because i threw the box :$

 

[kaelaan]

Well.. so much for my setup. I received a BSOD a few minutes ago (KMODE_EXCEPTION_NOT_HANDLED).

Since no release driver (from MSI or Qualcomm) and unofficial release driver seems to be correcting the issue, I have to assume that there are a lot (I know about a dozen of us with the same problem) of faulty LAN/WAN Bigfoot chipsets (pretty sure its on the same module).

 

[kaelaan]

And then another one (IRQL_NOT_LESS_OR_EQUAL) while vacuuming and letting it idle. Very strange.

 

[m4d]

i just hate msi at this point ,, i tried to swap it but they said they couldn't swap it even though it's clearly new (bought it 7 days ago and had the problem from day 1) and totally their fault ... so frustrating

 

[kaelaan]

I wouldn't hate on MSI too much. I would expect this from any laptop manufacturer. Unless you can reproduce the issue easily, a lot of times it is hard to prove your case. Which is why we come here.

So, I went out and bought a linksys wireless adapter, uninstalled the NIC and wireless drivers and then disabled both devices. Installed the Linksys USB wireless adapter and will be using that to see if the problem goes away.


I also went ahead and uninstalled the Qualcomm Atheros bluetooth adapter. Scanned for new hardware and it was immediately replaced by the Microsoft Generic Bluetooth device. Within a couple of minutes - BSOD... So, I opened up the dump with WinDbg. Apparently, Windows updated automatically replaced the Microsoft Generic Bluetooth with the Qualcomm Atheros version that I downloaded from the Microsoft Windows Update site a couple of weeks ago. When it did, it immediately though a driver fault KMODE_EXCEPTION_NOT_HANDLED. It also pointed out that Address regions for 'bthpan' and 'bthport.sys' overlap. I'm not sure if that's because the device manager didn't finish remove the MS Generic Bluetooth adapter before it automatically installed the Qualcomm version of the adapter for me - or if there is actually a problem with the Qualcomm Atheros Bluetooth adapter. So, just to be sure, I disabled the bluetooth adapter as well.

Anyway, if this fixes my problem - then I will eventually open up the bottom (void the warranty), pull out the Bigfoot Double Shot card (which includes the e2200 and Wireless N-1102 on the same mini card) and replace it with something different. I really do like the laptop... when it works.

 

[MasterChief]

I noticed you have Afterburner installed or a similar overclocking tool. I would completely uninstall that until you are certain the machine is well. Just a thought, as I see hardware referenced in crashes, in unusual ways too. Perhaps a set overclock is the cause.

Check CPU-Z SPD tab and compare it to its Memory tab. See if Memory tab reflects proper settings that SPD tab shows. If all memory installed is not of same exact brand, type and size, we should definitely look into that too.