My M11xR1 has been having random crashes and freezes since I've installed my Intel 6250 card.
The laptop would sometime freeze (can't move or open anything at all) when I leave it idling for long periods of time and the only thing I can do is a hard reset.
Sometimes, instead of a complete freeze like the above, explorer.exe would stop responding. I can keep running whatever programs I'm currently running. I was even in the middle of playing a game once and only found out that explorer.exe has stopped responding after I quit the game. When this happens I would also need to do a hard reset since if I try to restart it will be stuck during the log off process.
I have unchecked the option of allowing Windows to turn off the card to conserve power.
-
Try the older drivers or the latest. I'm using 13.5.0.6 that so far (one day) has been better, no freeze. Survived a few hours of use on the net and nearly 5hrs of idle time.
There are also potential vid driver crash. Usually this recovers on its own but something to think about as not all "freeze" moments may be intel related. -
Strange. My M11X has been running strong for 6 days without a crash with the Intel 6200. I always find that the majority of issues are caused by left over files and registry entries. Nothing beats a clean install of windows and keeping that OEM bloat off your computer.
-
I'm using 13.5.0 which is the latest for the 6250. Going to see if going to the 13.4.0.0 resolves the problem.
-
if going older.... go much older. 13.0 or even earlier.
There isnt really any bloat on M11x! Certainly nothing impacting NIC. Might be an application getting added later but I doubt it. To me this is about the same as some being able to overclock and others not. -
Not sure if this has been discussed here as I did not read the entire thread but I had this issue with the stock Wifi card that my M11xR2 shipped with, and I found a solution.
It stems from the fact that Wireless N is still a draft and not certified just yet. Different manufacturers are using slightly different configurations for their implementations of Wireless N and because of this, some of them are not compatible with everything.
Take the Intel 6200-6300 series of cards. A known issue (don't have link handy at work) is that the lower end Linksys N router (E1000) is not quite within spec and it causes random lockups/freezes when communicating with your wireless N card.
The solution? Sadly, is to disable mixed mode on the wireless router and allow it to only connect via wireless G. This is also the solution if you find yourself out at a coffee shop and experiencing the locks ups. Force your card into wireless G mode only.
There are ways to configure the wireless N to work, but without knowing the make/model of the router, you are stuck. If you know it, then you might get lucky and find a config that works, but due to the number of options the Intel cards have, I gave up immediately after I realized there would be more than 300k separate configs for me to try.
IT is also highly probable that other manufacturers will also have issues when using wireless N as a protocol, so linksys is not the only one affected, it is just the only one I needed to know about for my issue. -
I just installed the 6200 card and can't connect to anything. Here is what happens:
I sleep it - It wakes and I have 10-40 seconds to search for networks. If I catch it in time I see the network and it will try to connect. I have never had it connect yet and it drops out and will not see anything. I have tried messing with the power settings to make sure its "on"...
If I try and search again, it can't recognize the card. I have tried uninstalling the driver and reinstalling... no luck. Any clue what it could be? -
In my advanced settings the Ad Hoc Channel 802.11b/g was set to 11. I changed the value to 10 and that fixed it. Had to set others connection settings to medium.
I got ballzy and put them on high, and nope... dropped.
Set them back to med and no connections again... Ugh... -
Tore the back apart again and checked the card. I took it out and checked the antenna connections. I made sure it was correctly inserted, pulled it out and re did everything extra careful. Put everything back and low and behold, it worked... for about 2 minutes. I am really confused... Could the card be bad? I bought it from a trusted computer parts seller on ebay (not foreign and really high feedback). It seems like the computer is getting hot quicker as well too, could that be possible?
-
Could test in other system to confirm
-
Very true. I will do that tonight and see what happens. If thats the case, I will hopefully get a refund.
-
I went back to the stock card in my M11x and its working great (as good as before). At least I now know that its not my computer. Now to try the card in something else.
-
After few days of observation it seems I only get freezes when I disable the power saving options on the Intel 6250.
-
enabled/disabled power settings, even transmit settings. Driver versions of all sorts, Disable N etc. Still have freeze! Seems worse with Firefox for some reason. Odd.
-
I still have the same issue also, tried power settings, drivers... very frustrating.
-
anyone installing the full pkg from intel? Im just using the driver downloads.... but is intel bundling any card management into their software?
-
I will fix this today... I have let this annoy me for far too long... I am just glad to see i am not the only one.... I am going to blowout driver and install full intel suite, and disable power management.. I am on a fresh install and seems to happen during heavy duty use IE installing a program from a network drive which is becoming very problematic and messing up my registry....
-
Does everyone having this issue have a SSD btw?
-
no ssd here
-
I actually have a freezing issue with my m11x, intel 6200, has a vertex 2 ssd, at the moment i'm swapping ram to test if that's the problem, even though memtest found no errors.
-
its the card. Just cant find what combo sets it off or what temp threshold it has. I would exchange/return it but it would cost too much.
-
ok so, Ive tried everything, downgrade drivers, upgrade drivers, tweak settings, switch to g only, you intel proset utility.. nothing still freezes. Tonight i am going to blow out and upgrade every driver in my notebook.. and if that doesn't work I am going to put back the stock wifi card, and if it doesn't freeze for a week. I will be posting a video of taking the intel 6200 and shooting it with a potato gun into a brick wall, all the while i'm running full speed into the same brick wall holding my m11x in the other hand.... Will keep you posted
-
I made it nearly two days without lock... then pow pow pow lots of em. Curious if the potato gun vid is posted yet.
-
Sorry to butt in but I've got a bit of an issue that MIGHT be related. I have the stock Dell card and I've been experiencing lower than normal performance. I've actually had a few times when my m11x R1 locked up randomly when I was streaming anime or starting up an online game. Is it possible it might be the Dell card? I was scouring around trying to find info on m11x locking up issues and this seemed to make sense but you guys all seem to be speaking about the Intel card only. Sadly, I was thinking of switching it out to a 6200 or 6300.. Anyways, could my freezing up randomly issue be related to my Dell wireless card?
-
Most don't have that problem but you can try the same "fixes" they tried. It might be video, flash, or other issues but come back when you have teh 6xxx series
-
I'm having exactly the same problems with my 6300, although, my system configuration is a little bit different:
- Dell XPS M1330
- 4GB
- Intel SSD (Postville)
- Windows 7 x64
- Router: AVM Fritz!Box 7390 (simultaneous dual-band, but mostly connecting at 2.4GHz/40MHz)
The system freezes during heavy network, e.g. when copying large amounts of data on the local network or watching YouTube. At this time, the WiFi-card is quite hot (surely above 60°C). It is totally irrelevant which application or even operating system I use.
Because there are many "faked" cards or so called "engineering samples" flying around, I guess it might be that all of us are using such a faulty one. The main reason for me choosing this card was that I were unable to get a "non-faked" 5300. I tried 4 different sellers (even Amazon) and every card was "manipulated" slightly differnt: Most of them had a different MAC-address than the one printed on the card and some were recognized as an Intel 4965 (although the sticker says it's a 5300).
So my hope was that the situation would be much better when using the latest Wifi-Link series... But I doubt I was wrong :-( -
Faulty - probably. All using fake, altered, or samples - probably not.
-
Yes, I can only hope you're right, but after my personal "5300 desaster", not being to able find any (!) working/genuine card I'm just guessing the situation might be identically.
On the other hand: Why do so many 6300 cards, all sold by individuals and not from the OEM, around the world suffer the same failure if we are not talking about pre-production samples or faked versions? -
bad production run, something odd in common with effected systems, ??
I don't know one way or the other what mine is. Got it via Amazon
Fixed it by plugging in a DWA-125 -
I changed routers... to a dual band wireless .... will report back in 3-4 weeks if no lockups.. obviously sooner if i get a lockup in the meantime.
-
Side note how fail this PC only has a 10/100 nic... -
Has anyone found a solution or are we blaming it on faulty batches of cards? I was actually using my 6300 perfectly with an SLG motherboard, now that I have an ICS I get lockups within 5-30 mins of streaming Netflix. This started happening when I moved into a new house, and I'm situated a bit farther from the router.
-
and since it is a hard hang requiring a hard reset there is not memory dump like a bsod. So there is nothing to go off of, really.. i suspect its a voltage issue, or the way the card interacts with system memory... but the only resolution so far is just put the old one back in or deal with your laptop freezing.
I have tried everything btw to fix spent countless hours... days even its just not worth the time or effort. I have consulted numerous co workers with degrees and certifications to no avail.....
without a memory dump file i just cant figure out whats going on.... and a hard hang like that usually indicates a memory issue but my memory modules tested fine for hours of intense stress testing..
long story short put the old card back and use the other in another laptop... sorry -
just sold my 6300n. had at least 2 lock ups a day sometimes more and the only constant was the wifi card. the card wasnt faulty as such as it worked perfectly with no issues in my 101z. for some reason or another (most probably a driver issue) this card and my m11x didnt get on. back to the old 1520 and all works fine again. have to say it is weird as the wifi driver/ card was not my number one suspect for the lock ups but there you have it.
-
I changed a few advanced settings and was freeze-free for 5 hours of Netflix streaming and as I was typing up this post to report my results... IT FROZE. Beforehand it'd pretty reliably crash within 30 or so minutes of Netflix, so I thought I was onto something. Intel even has a new driver released June and it doesn't solve any of these problems.
The weirdest thing is that I had an SLG PLL with the intel wifi card working for months upon months rock solid. As soon as Dell replaced my motherboard to the ICS one it started acting up. I wonder if all of you guys have the ICS PLL. -
Whats the quick and dirty on checking that? Was it part of the OC thread?
-
trust me dude just get a new wifi card lol its not fake card its not faulty its something that is different about our mllx r1's (possibly what you said) that causes a hardware incompatibility with this card. The 6200 i pulled out of my mllx is up and running in a dell latitude e6410 with NO freeze after 48 hours of streaming media.... trust me just get a new wifi card 1501 or 1520 don't install the dell wireless utility just the driver.. use windows to manage wireless and boom you have your wireless gaming machine with slightly less range... oh well -
I have had two lockups just like when the 6200 was causing it... but card is disabled and I'm using LAN. Got one or two slight movements of mouse before system frozen.
It was night and day disabling the card but now having had the issue repeat I'm going to agree with others that it isnt a defecting card (in a traditional sense at least) but rather some conflict or ?? -
-
I have 2 mllx r1's that will do a random lockup even without the 6200.. BUT it is much more frequent like every 30 min with the 6200 installed.. I can check what PLL i have in both and maybe we can trend it.. but is dell going to do anything?.. It took a act of god to get the hinge issue under control...
I can deal with a random hard hang every 6-12 hours of gaming what I couldn't deal with was every 30 minutes and that was with the 6200 installed... -
agreed. frequency very high with 6200. Other instances I can kinda explain away (nvidia etc) but 2-6 times per day was too much. Oddly I had no obvious trigger or schedule - very random.
-
Hello boys and girls.
(Unfortunately I can not English, I'm German) This text is translated by Google. And revised by me on translation errors .....
For two months I have been working on a solution. And?
I think I know the cause.
For me it is specifically about the "Intel WiFi 6300", but the problem is identical.
Please be patient for another two days!
I now know why so few users are affected.
But more on that later.
Incidentally, the real problem with me was very difficult to detect.
I had cloned the same time with the WiFi built a system to other hardware.
My troubleshooting was 1 1 / 2 months in the same direction "SystemSID for two systems on the same network.
However, even after SID change, and even on fresh install Windows 7, the problem continues.
A defect in my new SSD was also not excluded.
But everything is ok except WiFi.
I discovered this thread only a week ago.
Just as the Intel thread, see here.
None of all proposals to be effective. I also think Intel is not aware of the problem. It is simple but very difficult to find.
I hope to be able to really help. Or this thread is so old that nobody has a problem?
I just wrote about this a lot of work to spare others. (New installation, or return of the Wi-Fi)
Final test run. Chance of success is 80%. The solution is definitely a compromise.
Publication about Thursday or Friday.
I'm happy now. -
That translation was bloody good. I'm very interested in your findings!
-
@GNandGS
Thank you for your feedback! So it is fun.(You are so far the only one interested.)
If I let my German text translated 1 to 1 of Google, is coming out just bull. I always have to "words" exchanged or replaced.
Often even help parentheses or quotation marks. So do not wonder about it! This text took me 30 minutes of my life.
There are still two long-time tests under different preconditions necessary.
Chance of success is now at 90%. Moreover, the benefits remain more "WiFi 6300" received than I thought.
Incidentally, I also think the 5300 is WiFi affected by the problem. Unfortunately I have no 5300 for testing.
For the 5100 I can probably make a statement later. (next week)
My test cards are:
3x "WiFi Ultimate 6300", " 1x WiFi 5100", 3x "WiFi 4965 AGN with three antennas," 1x "Wifi 3945" and 1x"Fritz USB Stick N '
Is tested on laptops of this type:
3x "HP Pavilion HDX Win7x64 and Vistax32"(Dual boot), 1x "Toshiba Portege A600 Win7x32 and Vistax32"(Dual boot)
2x "Gericom MEx32" 1x "Medion Win7x32"
Is tested on Router of this type: 1x "FRITZ!Box Fon WLAN 7270 v2 (UI)"
I publish only when I'm 100% sure. It remains for Thursday and Friday this week. Sorry!! -
Looking forward to it. Let me know if I can test something
-
Wow! Looking forward to the sort of detailed and intense testing you are doing. Good job on the translation!
-
Mal sehen, wie die Rückübersetzung funktioniert ... Bitte teilen Sie uns Ihre Erkenntnisse. Während einige ohne Zweifel aufgegeben, sicherlich einige Leser davon profitieren - auch lurkers.
-
Glad us lurkers can benefit -- I appreciate your assumptions, but as they say about assumptions. I've long since sold off my intel card and in fact the computer that it was used in.
I was simply coming over here to pay a compliment to a fellow human being who saw it fit to spend some of their time trying to resolve these issues. Again it was purely to encourage his excellent work since I have no gain.
I left this thread subscribed for all this time because I was curious there would ever be consensus that A) it was problem with the card, and B) ever would be addressed. -
Don't be an . I was offering encouragement and to not be concerned if all those who still have the card(S) choose not to post. Apparently there might be issues with or improvement to be had with cards other than 6200
-
I'm sorry. The extent of my tests is really huge and still not completed.
Unfortunately it was in the last two days results, again spoke to my theory.
Thus, it is not possible for me to offer a 100% solution. On the contrary, I doubt any connection now. And if not 100%, then there is no solution.
But one thing is clear to 100%, an emerging "Freeze" is solely in connection with the "WiFi 6300" and occurs only where it is installed.
A system installed with "3945" or "4965" or "5100" I never did crash.
(Under no circumstances, always stable)
Preliminary information:
In all my tests I am only using the 2.4 GHz band. (I never used 5.2 GHz)
But even here I see no connection.
1."WiFi 6300" test only to "HP Pavilion HDX9350" and "9480". (Operating System 100% identical, since "9480" is a clone of "9350")
2.I have every available "Wifi driver" to test for a connection error - same behavior.
("Oldest 13.4.0.0" to the "latest 14.1.1.0" is displayed as "14.1.1.3")
3.Each Driver removal was by deleting the old driver. Each driver installation was done only after system reboot.
(There were no drivers to install Vista and Win7 independently, because all I had deleted)
Better it gets.
4.All driver settings I've tried, but could never establish a connection to the problem. That is why I describe it not in detail.
5.All OS system error can be excluded since no problems with "WiFi 4965" in both HDX. (Never)
Even then, when "4965 WiFi" was built "HDX" in one, and the other "HDX" with "WiFi 6300" worked.
6."Virtual WiFi" Initially I had also suspected, but could also create a stable system without being inactivated.
7.Before each test, I deleted the previously existing network connection and set the router back.
Thus, here error causes are excluded.
8.For all tests, the systems were switched on permanently. (Energy saving mode turned off)
The same applies to the router's Internet connection and "wireless router connection" to the notebook.
First observation:
A freeze of "WiFi 6300" takes place only while connected to the router.
An active "WiFi 6300" ("WiFi Laptop" turned on) without a router connection never produces a crash.
This statement is good for debugging, but meaningless for daily operations. (Without "router connection" no wireless card required)
Second observation:
The freeze occurs regardless of the stress.
I needed no large downloads. Freeze all performed in idle mode.
Mean, 90% believed safe, theory. (Now disproved)
But perhaps it does help someone.
I assumed that each of the freeze problem has more than one wireless device to a router operates.
At the same time, I assumed that each of them uses channel bonding.
(Yes, this is just one of the advantages over an older wireless card.)
To this end, the channel bandwidth of the WiFi drivers are provided by the 2.4 GHz "20Mhz" on "automatic".
At the same time have the radio channel of the router to "n + g" (2.4 GHz) and "For 300 Mbit / s optimized use of radio channels" are set.
This creates a stable 300Mbit / s connection between "WiFi 6300" and the relevant routers.
Now is an additional router connected to a "wireless device" made in the channel bonding "2.4 GHz band" is not supported,
it comes at the "6300 WiFi system" to freeze within minutes.
Additional example of my connection to the same router without any "channel bonding in the 2.4 GHz band", "3945 WiFi" or "Wi-Fi 4965)
For other users this can be any other wireless device. (Eg phone, media player, next-door neighbor who has access to the same router)
To exclude all factors, it must have done a test.
This was the system with "WiFi 6300" (or 6200) alone have access to the router. No other router connections!
After 24 hours of continuous testing without a freeze, a statement can be made.
My first recommendation for an alternative way of multiple connections to the router was switched off the router function "for 300 Mbit / s optimized use of radio channels."
(I do not mean the WiFi driver setting)
This was my first success in any case without any freeze error. This unfortunately only with a maximum connection speed 130Mbit / s.
Under utilization of this knowledge, I banished all wireless devices that do not support the 2.4 GHz channel bonding.
So I tested without 3945 and 4965th
Further tests were performed only with a double connection to the router between "6300" and "5100".
I switched the router to function "for 300 Mbit / s radio channels optimized use" back to active.
Both notebooks ("HDX 6300" and "Toshiba with 5100") had stable 300Mbit / s connection.
Test run 24 hours in idle. Do not freeze.
My previous assumption was confirmed by yet.
Assuming this alleged knowledge (one-sided channel bundling problem), I expected to get the Toshiba to freeze.
To this end, I switched the driver of the "HDX 6300 in WiFi" (during connection of the two notebooks),
the channel bandwidth to 20MHz. (was "automatically")
result:
Toshiba does not freeze, but the "HDX with the 6300" crash after 20 minutes. (Freeze)
It is impossible to understand.
Of course I made the same test again, this time however, I switched to the Toshiba 20MHz channel bandwidth.
result:
Again it came to the freeze on the HDX.
The Toshiba with the "Wifi 5100" was always stable and never crashed during testing.
The results make me mad. I find no meaningful Freeze condition.
Now the test for Wednesday, Thursday and today. This is due to the Crown.
Hardware and Info:
1. "HDX9350 with 6300"
Always stable with 300Mbit / s. Even with simultaneous use of the "Toshiba with 5100". The only requirement:
No change in channel bonding on the fly.
2."HDX9480 with 6300"
Despite having the same hardware, same drivers, and exactly the same OS (only difference processor and SSD) behave differently compared to the "HDX9350".
Behavior: "WiFi 6300" Freeze at irregular intervals.
(Sometimes after 20 minutes, sometimes after 4 hours)
Freeze at only active router connection. With WiFi on, without a router connection, no freeze.
By using the original "4965 WiFi" never freeze.
I wanted to explain this different behavior now.
My guess: "Wifi 6300 in HDX9480" has a hardware defect.
Test: I swapped the "WiFi cards" between "HDX9350" and "HDX9480".
The "WiFi driver (14.1.1.3)" I have not uninstalled.
Now I started the "HDX9480" 6300th, which presumably intact
Result:
Do not freeze. The system is running without interruption even now.
Well I started the additional "HDX9350" with the suspect "WiFi 6300". The "WiFi driver (14.1.1.3)" I have not uninstalled here.
Result:
Do not freeze. The system is running without interruption even now.
It is not to understand!:
"Intel WiFi 6300" 100% original!
MAC address on the label and the network indicator in each match.
I'm building a card always conscientious. Installation errors are excluded.
Is there a connection problem with the "6300"? (Contacts?)
After the "WiFi card swap" HDX both immediately went online. (The driver I had not even uninstall)
Both "HDX" did not notice the hardware change. (No "new devices detection" at startup)
Here is an explanation?
After another 24 hours I started also the "Medion notebook with 4965."
I expected to be 100% a freeze on the HDX.
(Remember: The "4965 WiFi" does not support the 2.4 GHz channel bonding, and brought before the HDX9350 to freeze)
Result:
Do not freeze. All three systems operate continuously, even now.
This morning I started the addition "with Toshiba 5100"
Result:
Do not freeze. All four systems work continuously, even now. (For 8 hours)
I am a little confused.
Until now I have no "HDX system reboot".
This, however, I will make soon. (After another 24 hours without a freeze)
Conclusion:
All my theories run into the sand. Is it the order of registration on the router?
Has it something to do with different heat?
If the distance between the notebook is a factor? (HDX are currently right next to each other)
I've really invested more than enough time.
I have all the possible test minimizes interferences.
I've changed for each test performed only one parameter.
There were no changes in the system test phase.
I'm sorry, because this is not a solution!
Sorry!
With new insights, I'll write here.
Perhaps a user detects a connection that has not struck me.
This paper describes only the "Freeze changing behavior" test.
The full extent of all of my tests can not be described.
The only thing that is certain to 100%, using only the 6300 (I have no guess 6200, but this has the same problem), there is Freeze.
No other system has ever had a crash.
Finally, my main question:
Are there users who run only a notebook (of course with "WiFi 6200 or 6300") to get a router (no other wireless devices) and a freeze?
The answer is only interesting if Freeze is 100% of the "WiFi Connection" is due!
Stock Wi-fi card to Intel wifi 6200 system freezes
Discussion in 'Alienware M11x' started by bittercold, Dec 27, 2010.