irql_not_less_or_equal when wireless is turned on

Hi -

Any chance that your friend has a problem with the electricity?  Have any electronic devices been fried over there?

Just to make sure - you do use the same power cord for the ;laptop at your friend's as you do at home..?  Anything different whatsoever - a disk you use, a setting that has to be made, etc... ??

Please copy the mini kernel dumps from c:\windows\minidump out to your Documents folder.  Then bring up an elevated administrative cmd/DOS prompt -

START | type cmd.exe | RIGHT-click on cmd.exe, select 'Run as administrator' -- then type or paste the following commands in 1 line at a time -

driverquery /v > "%userprofile%\documents\dq.txt" & start notepad "%userprofile%\documents\dq.txt"

msinfo32 - the system info viewer will appear, save the file in the default NFO format  (file ext = NFO by default)

dxdiag - the DirectX Kernel diag rept - save it as a text file - bottom-center of the GUI says "save all as text".. select it and save the file

For now, only the driverquery is a full line command (all gets copied to the cmd/DOS screen), whereas  for  msinfo32 & dxdiag  -- those are the commands.  I may need add'l info at a later time while running the dump files.

Please rename the dumps & NFO file -- all files must end in TXT for uploading here.  Just add TXT to each, then zip them all up.   If you wish, go to my user profile and you'll see an email address.  You can send them there as attachments and I'll take care of attaching them to a post here.

Regards. . .

jcgriff2

He has no problems with power. And the wireless is onbord, and I don t need to config nothing there becouse the ip set is the same as my home. I also put a alternative ip settings. Is there any way to have another comp interfering on his wireless card. Becouse, I turn his comp with wireless card off, it was good, but when I turn it on, blue screen at same instant.

Just upgrade your WiFi driver to the newest one...

Are you using symantec's norton internet security?

No, we are using pc-cillin, but I tryed without the anti-virus on. Same error. The anti-virus is not the difference between my house And my friends house. The only thing possible is a wireless conflict on the neighborhood?? What u think about this possibility?

I think I'd get my windows CD out and run
SFC /SCANNOW
though that might not find anything out of spec anyway.

If I recall correctly, the last time I had a machine that kept BSOD'ing with that error I ended up doing a repair install. It had no wireless card in it at all, and no new hardware or programs had been added to it in the prior 6 months.

well, still it is happening the problem, i can take this anymore man, this computer is crazy, is there anyway that a wireless card can work in one place, and in the other crash the comp. it's crazy. what do i do with that?

What did SFC /SCANNOW do?

Did you upgrade your WiFi drivers?

[ QUOTE =  jcgriff2  ]

Hi -

Any chance that your friend has a problem with the electricity?  Have any electronic devices been fried over there?
Just to make sure - you do use the same power cord for the ;laptop at your friend's as you do at home..?  Anything different whatsoever - a disk you use, a setting that has to be made, etc... ??
Please copy the mini kernel dumps from c:\windows\minidump out to your Documents folder.  Then bring up an elevated administrative cmd/DOS prompt -
START | type cmd.exe | RIGHT-click on cmd.exe, select 'Run as administrator' -- then type or paste the following commands in 1 line at a time -

driverquery /v > "%userprofile%\documents\dq.txt" & start notepad "%userprofile%\documents\dq.txt"

msinfo32 - the system info viewer will appear, save the file in the default NFO format  (file ext = NFO by default)
dxdiag - the DirectX Kernel diag rept - save it as a text file - bottom-center of the GUI says "save all as text".. select it and save the file
For now, only the driverquery is a full line command (all gets copied to the cmd/DOS screen), whereas  for  msinfo32 & dxdiag  -- those are the commands.  I may need add'l info at a later time while running the dump files.
Please rename the dumps & NFO file -- all files must end in TXT for uploading here.  Just add TXT to each, then zip them all up.   If you wish, go to my user profile and you'll see an email address.  You can send them there as attachments and I'll take care of attaching them to a post here.

Regards. . .
jcgriff2  

[ END QUOTE ]

no, no problems with eletricity, or fried eletronic.

i am using same power cord.

not difference in the setup between my home and his house. i just turn the computer on on my house and work, and i just turn the comp with the wireless card on, than crashes, but if the wireless card is off, the comp works great at his house. this happen only when wireless card is on. but on my house the wireless can be on, does not matter, it work all ways on my house.

the dq.txt file is from the drivequery result, and the others from the folder minidump.

take a look and lets see what we can do with this comp.

thanks so much for your pacience.

That was my intuition it's WiFi driver. After analyzing your dumps I am sure.
So I'm writing 3rd time: UPDATE YOUR WiFi DRIVERS.

BSOD is caused by w22n51.sys and timestamp for such file in your system is Nov 2003

Here's the download page for the Intel BG2200
http://downloadcenter.intel.com/Filter_Results.aspx?strOSs=All&strTypes=All&ProductID=1637&OSFullName=All%20Operating%20Systems&lang=eng

Drivers only for XP (June 2009) - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17751

Drivers only for Vista (April 2008) - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=15798

I would download the exe file rather than the zip file, btw.

You should check at the laptop manufacturer's website first, though. They may have an updated driver for it.
I would still be prepared to do a repair install of windows over the top of the current install. i.e. prepared means ''backup whatever you can, first.''

Hi rafaelrgl -

My apologies for the instructions - they were for Vista, but I see you did just fine.  Thank you very much for all of those mini kernel dumps and the driverquery.  

Those that actually ran all 21 dumps should know that an updated Intel wifi driver will only buy you a very short term solution to the BSOD insurgance.

While at Intel, also update the driver for your Pro 100 Ethernet as well as it was loaded into RAM at the time of the crash and is from 2002 -

E100B        Intel(R) PRO Adapter     9/25/2002     7:09:09 AM       e100b325.sys        

I will have results for you within a few hours.

Regards. . .

jcgriff2

.

jcgriff2: e100b325.sys is loaded but not involved in BSOD. Just upgrade WiFi drivers... Nothing more complicated.

Hi -
 
Yes, w22n51.sys is clearly listed on the stack text and e100b325.sys is not --- not yet, anyway.  Why would a 2003 Intel wifi driver suddenly go nuts and cause 21 BSODs in a 90 minute timespan?   I don't think it is a reach to then think the system's 2002 Intel Ethernet driver may cause tomorrow's crashes (Ethernet used at home, I believe).  Nothing complicated about that at all.  
 
All 21 dumps were identical - bugcheck = 0xa, with the probable cause = w22n51.sys
 
No surprise there, but the catalyst(s) without a doubt are Trend Micro and the lack of Windows Updates.  Trend Micro's drivers are the newest in the loaded driver listing - April/ May 2009.  The NT Kernel, DirectX Kernel, win32k and others are the original drivers from XP SP2s release;  timestamp = Tue Aug 03 23:19:48 2004.  So if you just update the wifi drivers and not allow Windows Updates in to update your XP SP2 system, you will be back here within the week with additional BSODs.  I have seen follow-up BSODs in situations like this way too many times.
 
The link for Windows Updates - see what is there - http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-US
 
I have reason to believe that your Trend Micro IS installation is corrupted based on the timestamp of one of the drivers tmtdi.sys -- it has a timestamp = Dec 2007, but all other TMicro drivers are dated 2009.  I found this odd, so I searched through other system dumps and found that tmtdi.sys should have the same 2009 timestamp as the others.  Your system is listed 1st, another's below it (please see the code box).
 
That is all that I have for you as of now.  Windows Updates and driver updates are needed.  XP SP3 has been out for a while now and you will need to install it at some point in the near future.

Regards. . .
 
jcgriff2

 
@ gtworek -- I apologize for the tone that I have taken at times in this thread, but I have always looked at all drivers in a dump.  Please accept my apology so we can move forward.  The important aspect here of course is that rafaelrgl received help.
 
Thank you, JC
 
.

Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:59:20.066 2009 (GMT-7)
System Uptime: 0 days 0:02:37.626
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:56:30.450 2009 (GMT-7)
System Uptime: 0 days 0:00:35.010
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  svchost.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:35:27.068 2009 (GMT-7)
System Uptime: 0 days 0:03:27.628
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:31:46.784 2009 (GMT-7)
System Uptime: 0 days 0:04:06.344
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:11:03.202 2009 (GMT-7)
System Uptime: 0 days 0:00:36.762
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  svchost.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:08:46.962 2009 (GMT-7)
System Uptime: 0 days 0:00:36.522
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  svchost.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:07:58.810 2009 (GMT-7)
System Uptime: 0 days 0:00:35.370
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  services.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:07:11.876 2009 (GMT-7)
System Uptime: 0 days 0:05:17.436
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 12:01:43.245 2009 (GMT-7)
System Uptime: 0 days 0:04:34.805
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:56:58.357 2009 (GMT-7)
System Uptime: 0 days 0:03:12.917
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:53:22.994 2009 (GMT-7)
System Uptime: 0 days 0:02:15.554
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  SfCtlCom.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:50:55.570 2009 (GMT-7)
System Uptime: 0 days 0:03:08.140
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  Idle
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:47:33.340 2009 (GMT-7)
System Uptime: 0 days 0:00:34.900
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  svchost.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:46:43.992 2009 (GMT-7)
System Uptime: 0 days 0:00:36.552
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  services.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Mon Jul 20 11:38:36.723 2009 (GMT-7)
System Uptime: 0 days 0:00:37.283
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  svchost.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:46:14.818 2009 (GMT-7)
System Uptime: 0 days 0:00:47.378
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  System
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:44:54.399 2009 (GMT-7)
System Uptime: 0 days 0:02:39.968
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  SfCtlCom.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:42:01.923 2009 (GMT-7)
System Uptime: 0 days 0:00:44.493
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  services.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:40:55.723 2009 (GMT-7)
System Uptime: 0 days 0:00:44.283
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  csrss.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:39:58.536 2009 (GMT-7)
System Uptime: 0 days 0:00:46.096
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  explorer.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_rtm.040803-2158
Debug session time: Thu Jul 16 21:38:58.418 2009 (GMT-7)
System Uptime: 0 days 0:00:40.978
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
BugCheck 1000000A, {ff1711f2, 2, 0, 804d9f68}
Probably caused by : w22n51.sys ( w22n51+680e2 )
PROCESS_NAME:  services.exe
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
by jcgriff2
http://www.experts-exchange.com/M_5001532.html
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:

ok, i understand everthing u guys are saying about this. but one quote is necessary, why the same drive that is load crash at my friends house, and here at my house does not crash?

Probably something slightly different data are transmitted...
Maybe different speed, different broadcast frequency, different channel, different length of SSID... there are many parameters and one of them makes your driver crashing.

Rare crashes are the main cause of publishing such defective driver. Programmers can easily find their mistake if it crashes frequently...

Hi -

I agree there could  be some difference in your friend's router/modem than yours, but even if there was - it should not matter.  I am not convinced at all that that Intel wifi driver caused these crashes alone; at best it was a minor contributing factor.  It came in contact with another driver that either IT (Intel wifi driver) did not like or the other driver did not like IT.  This is the reason why I said that the updating of the wifi driver may buy you a little time, maybe none at all.

To help prove my theory - if the wifi driver was the sole cause, the system should have crashed at the same point every time because drivers are loaded into boot in the same order each time.  This would be the same for logon assuming the same user account is used.  Look at the system up-time and the name of the process running at the time of the BSOD's -

The longest time was 5 min 17 sec

Here is a summary - SYSTEM UPTIME on left; PROCESS running on right

0 days 0:05:17.436   :  Idle
0 days 0:04:34.805   :  Idle
0 days 0:04:06.344   :  Idle
0 days 0:03:27.628   :  Idle
0 days 0:03:12.917   :  Idle
0 days 0:03:08.140   :  Idle
0 days 0:02:39.968   :  SfCtlCom.exe
0 days 0:02:37.626   :  Idle
0 days 0:02:15.554   :  SfCtlCom.exe
0 days 0:00:47.378   :  System
0 days 0:00:46.096   :  explorer.exe
0 days 0:00:44.493   :  services.exe
0 days 0:00:44.283   :  csrss.exe
0 days 0:00:40.978   :  services.exe
0 days 0:00:37.283   :  svchost.exe
0 days 0:00:36.762   :  svchost.exe
0 days 0:00:36.552   :  services.exe
0 days 0:00:36.522   :  svchost.exe
0 days 0:00:35.370   :  services.exe
0 days 0:00:35.010   :  svchost.exe
0 days 0:00:34.900   :  svchost.exe

There is no rhyme or reason to the differences in the system crashes.  My guess is that the system crashed whenever an Internet-required service was invoked.  I think it is none other than Trend Micro.  A product like Trend Micro or similar with a firewall would certainly explain the absence of Windows Updates.

To test - take your laptop to an area hot-spot - McDonald's, Dunkin Donuts - anywhere with free wifi and see what happens.

Regards. . .

jcgriff2

Hi rafaelrgl -

Any news for us?

Thanks. . .  jcgriff2

it funny, the wireless card came back to life, it's up and running, but the windows update was not automatic, and also no update was made after i tryed to update the drivers and failed to work. But thanks a lots for your help experts. U guys open my mind about those problems.