RPracic

Good afternoon! (Well, down here anyway),

It is still fairly cold up here. Got some snow overnight as well. Oh well, darker days mean brighter ones to follow. A good 6°C is the best I can hope for these days.

As for the manufacturer drivers - don't worry about that... I didn't even think of it. Consider it a mistake on my part rather than neglect on your part. I probably should have checked after getting drivers from Microsoft.

I used to use Dial-up... I think about 8 or 9 years ago . It was good enough for me at the time. I bet if I went back, I would die waiting for pages to load.

That's too bad about the SFC log. Well, good that there's no errors there, but unfortunately the scans still show some errors.

Even more unofortunate, though, is that I came home to a blue screen twice more during the weekend. Fortunately, it's not nearly as often as it used to be, not by a long shot. To be honest, I think I can live with a blue screen error every 40 hours or so. Obviously there's some underlying error that we just can't seem to find, and it will always be on the back of my mind. I won't be in such a hurry to find it. Anyway, I have included here the latest two BSOD minidumps. Hopefully they reveal something the others have not - but I think I can foresee the unfortunate result of that.

Fortunately, I can still transfer files as required. Between two of my home network laptops, I set up a torrent for BitComet to transfer a fair 35GB worth of files for a second test. During this second test, the transfer was nearly completed at 31.29GB before the blue screen error. A total of 35 hours transfer time (approximately). This is acceptable for me on a non-standard basis, considering most of my work with clients is capped at 15GB, and that's on a very rare occasion.

However, on the flip side, I am a perfectionist with a little bit of OCD in me, so in the back of my mind, I'm always going to want to fix what's broken. I'll know the issue is there so I'll continue searching.

I ran all the scans I could think of again - memtest, anti-virus (I did housecall and AVG, and I borrowed NOD32 from a friend and ran that as well), SFC scan again (same errors as before), checkdisk... I am just re-downloading and installing that hotfix that was posted here twice earlier.

So far, no dice with the scans, I have no idea what the problem is. I am beginning to think that the wireless card simply overheats and something with that causes the system to reboot. I will attempt to schedule time to run the laptop for a good 3 or 4 days without wireless next time and pray that it works. at this point, I don't care if I have to replace hardware, I just want to know WHAT to replace!

At any rate, I still owe you a lot. We are definitely gaining some ground here and I never would have thought of these things on my own. So thank you very much for the assistance!

Take your time reviewing the BSOD reports. If others on the forum have posted errors - give them priority if need be before coming back to this topic and looking over any of this. Enjoy whatever is left of the weekend!

Thanks a lot!

-Rob

P.S. Sorry I hadn't replied back in a few days!!
P.P.S. I hope you don't mind, but I have sent (/am sending) a complete SFC scan to you're e-mail address. (Update: I am rebooting to safe mode to run the SFC scan. I find that on Vista, even in elevated mode the cmd commands still get denied access to certain areas, I'll upload the entire report when complete).


(Edit - Apparently I missed a BSOD that I never uploaded from before...)

Attached Files

	MiniDump Files latest.zip (40.7 KB, 1 views)
	Minidump 040508.zip (19.4 KB, 0 views)

jcgriff2

Hi again Rob. . .

Sorry to hear that the BSOD epidemic continues for you. Personally, I would dread an annual BSOD - let alone one every 40 hours. No one should have to "live" with BSODs -PERIOD-! The old myth that I hear from time-to-time that a BSOD is a normal "Windows Event" is just not true - at least in my eyes. I agree that some are much harder than others to solve, but I like to believe that all have an ultimate solution. So, let's go forward and see what we can do. OK??

Now... the area that I immerse myself in is Windows and software in general. I am really not that savvy in the hardware area, but there are those within TSF who are hardcore hardware experts. I will ask that a hardware specialist review this thread. They may very well ask for additional information. Also, a second (or third) pair of eyes from the software side would not hurt either - as I find driving the roads at night getting a little blurry. We all have different methods of troubleshooting and solutions as well. I never mind being "second guessed" as the phrase goes. After all, no one person knows everything - although some have told me they do! Seriously, though, when I find a user as willing and as forthcoming as you have been, I will move both Heaven and Earth to help.

One area that I would like to check out further is your Event Log(s). Let's start with the Admin log. Click on START; type eventvwr.exe in the Start Search box; right-click on same when it appears above; select Run as Administrator; on the top-left side double-click on Custom Views; click on Administrative Events - this will take a few seconds to bring up; Look to the right-center - "Save events as..." - click on this and save the file as an EVTX file - this is a must so that I can review them in the Event Viewer on my Vista system. Zip the file up and ATTACH to your next post. Please do this soon as I want it to capture the most recent BSOD information.

As far as the memory dumps are concerned - send them all at any time. On some rare days, I find myself to be "memory dump-LESS" and have trouble sleeping! No day of mine is complete without processing one. In all honestly, just one single dump could solve all by revealing a driver name that has thus far eluded detection. You never know.

My only enemy these days is time. It is Spring and in New Jersey anyway, it is a time to clean up after a harsh winter (I know... yours are much harsher!). We get a lot of sand and a ton of salt that wreaks havoc on everything. Also, the days are longer with summer now approaching as well as Daylight Savings Time invoked. The kiddies regularly miss their 22:00 bedtime. I pay for it dearly! So please be patient as all of this will be ongoing and somewhat time consuming - on both ends.

Regards. . .

JC

RPracic

Thanks again for the reply, JC,

Along with another BSOD dump, I have included the information from the Event Viewer as you have requested.
I've decided I don't want to live with the BSODs. I thought I could, but it seems "they" have a life of their own and just keep coming back. I think we'll have to put a stop to this...

I'm pretty sure I can provide at least one dump report for you every day... if you're bored, you know who to call!

Anyway, I guess you want to take a look at these. I sure hope you find something of interest. When I reviewed it, all it says is "Cannot find address of even ID O", or something to that effect. Hopefully what I've zipped up is what you were looking for, I've never had to do that before so I'm not entirely sure I did it right.

I'm a pretty patient guy - I guess that sort of speaks for itself when I say I can try and live with one BSOD a day. I try to nod it off as "just another day in paradise", zip up all relevant info, and move on with my work. At least you can get some sleep after digging through it and seeing what it has to offer. Did you get the SFC files I sent via e-mail?

All the help is much appreciated!! Thanks!

-Rob

(Edit - Uploaded a second one. Seems I missed some sort of "Local Meta Data". Don't know if its relevant but for time's sake, which I know we both seem to have very little of, I am uploading it all here as well. Boy... only 24 hours in a day?)

Attached Files

	Event Viewer - Administrator Events.zip (347.8 KB, 1 views)
	Mini040608-01.zip (21.1 KB, 1 views)
	LocaleMetaData.zip (551.3 KB, 1 views)

RPracic

One more for the trophy box...

By the way, I appreciate you gathering more people to take a look at the issue. The more heads, the better - and I sincerely appreciate all the help I can get in this perplexing matter!

Thanks!!

-Rob

Attached Files

Mini040708-01.zip (21.1 KB, 2 views)

RPracic

Three more.

Windows update just gave me 12 more updates today. One of them was for the wireless card (it installed what seemed to be older drivers than what I had, but I guess I'll see what that does).

-Rob

Attached Files

MiniDumps.zip (64.2 KB, 0 views)

jcgriff2

Hi again Rob. . .

I know I said I like at least one memory dump per day to keep me occupied, but you sent two!

As I said - the more information, the better.

Well, this time the BSODs have a definitive cause - the Intel driver NETw4v64.sys is the faulting driver. I could not find the version number in the dumps (yet) but I did find the time stamp - Wednesday, January 9, 2008 -06:15:52. Please check with the Device Manager to see if this date is listed.

Your memory dumps are huge - which is great - more information. I am still going through them, then I will turn to the other information that you provided and see what come up.


Regards. . .

JC

RPracic

Thanks for looking through those!

It appears our previous suspicions were correct. After checking the device manager, I did not discover very much. No drivers applied to that date (keeping in mind I JUST updated the wireless drivers through windows update before you posted last). I checked the intel website and the drivers I had before were February, 2008. So that COULD have been it. Not sure.

After some brief searching, I have found a few forums that state people having the same issue with NETw4v64.sys. Most say that it is an issue with the duration which the wireless card is ON and connected. Based on the amount of connections at any given time, a BSOD could occur.

I'm not entirely sure I understand - seems like the more work you do that sends and recieves packets through the internet, using the wireless card, the more prone it is to a BSOD. Eventually, it will overload and cause the crash.

An interesting point made was that it DOES NOT occur on XP. Users had tested the card with several drivers on Vista systems and constantly encounter BSOD's or crashes or failures or freezes of some sort. After trying the same card and the same sets of drivers on an XP system, the problems would disappear.

A few of the forums I found are:
Microsoft
Microsoft 2
Vista

Fascinating.

On my laptop, I have done a search and located seven NETw4v64.sys files. Three of them are 3.46MB, Two are 2.99MB, and two are 3.04MB. Their version numbers all vary, and are as follows:

3.46MB (1) - 11.5.1.8 (The drivers I had from the HP site) 09/01/2008 <- This date corresponds with the above error you found.
3.46MB (2) - 11.5.1.8 (The drivers I had from the HP site) 09/01/2008 <- This date corresponds with the above error you found.
2.99MB (1) - 11.1.0.86 (Not sure where these came from. Default maybe) 01/03/2007
3.04MB (1) - 11.5.0.34 (These are the ones I got from Windows Update moments ago) 31/10/2007
3.46MB (3) - 11.5.1.8 (The drivers I had from the HP site) 09/01/2008 <- This date corresponds with the above error you found.
2.99MB (2) - 11.1.0.86 (Not sure where these came from. Default maybe) 01/03/2007
3.04MB (1) - 11.5.0.34 (These are the ones I got from Windows Update moments ago) 31/10/2007

None of the above had the time you provided. Closest was the 2.99MB and 3.04MB ones, at 6:44PM and 6:50AM.

Let me just say, I'm fairly confused.

-Rob

jcgriff2

Hi Rob. . .

I was processing memory dumps on another BSOD case and while they were running I was looking through the hexadecimal numbers in yours and saw something that caught my eye (the last six digits, anyway)-

426974436F6D65742E657865

which interpreted into ASCII is -

BitComet.exe

As you know, BitComet.exe belongs to the P2P program BitComet. I found this program as the primary program running at the time of the BSOD that caused the Intel NETw4v64.sys driver to "leak" memory and fault.

I highly suggest that you uninstall it and see if this helps to quiet the BSODs. If this program is anything like Limewire, it runs on boot-up and stays running in the background whether you are using it or not - even if you don't think you are using it - it is using your system. It's part of the typical P2P sharing network.

Please let me know of the results.

Regards. . .

JC

RPracic

Ok, I will give that a shot and let you know.
BitComet is what I use to torrent massive files to and from clients (that's what I used to test the 14GB earlier).

Using the drivers from Windows Update that installed recently (as I also said above), the laptop ran for a about 10 hours today with BitComet, but without MSN or Skype.

I will continue to let it run with both BitComet, MSN, and Skype until the next BSOD. At that point, I will do a fresh reboot into safe mode, remove BitComet completely, reboot again and use the laptop normally with MSN and Skype, and all else aside from BitComet.

Sound fair? Unless you need some results ASAP, I have no problem getting rid of it now, and then trying that out, reporting the results about 24 hours from now.

I'm just interested to see what changes (if any) these drivers did. Who knows.

Anyway, thanks for the update!! At last we have it pinned to one last tiny thing. Let's hope it stays that way.
Thanks a lot!

-Rob

jcgriff2

Hi again Rob. . .

Your plan is fine with me. A 24 hour "breather" is actually a good idea for your system as there were 10 or so Windows Updates that probably hit you this morning as well.

As for me, I can tell you that I have many memory dumps to process tonight, so I won't be bored!

Have a good day tomorrow, and let your system digest some of the changes made to it.

Bye for now. . .

JC

sjoker

Hi Everyone,

I have followed this thread with some interest for a while and had hoped the new Intel drivers released today (Sat 04/12/2008 for Vista x64) might be able to stop the problem - but apparently no such luck :( Still crashing on Vista Ultimate x64 SP1 with Intel 4965AGN - now using Intel Driver Version: 11.5.1.15 (NETw4v64) Driver Date: 03/13/2008.
Since the driver was just released today - it had apparently a couple of weeks to go through testing etc. I have to admit is seems faster - but bummer enough still crashes.

And no Intel symbols for NETw4v64.sys :( (see below)

----------------------------------------------------
Use !analyze -v to get detailed debugging information.

BugCheck A, {143c0000007c, 2, 1, fffff80001e7a163}

Unable to load image NETw4v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw4v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys

Probably caused by : NETw4v64.sys ( NETw4v64+77410 )

dai

the only solution i found to stop the bsod was to disable wireless and use bluetooth
if it was working before sp1,you could uninstall sp1 until intel sort the driver out

sjoker

Here a new example of app (Second Life) running when crash occurs.


Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini041708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Kernel base = 0xfffff800`01e53000 PsLoadedModuleList = 0xfffff800`02018db0
Debug session time: Thu Apr 17 00:47:18.716 2008 (GMT-4)
System Uptime: 0 days 11:47:52.014
Loading Kernel Symbols
..............................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {143c0000007c, 2, 1, fffff80001eb3163}

Unable to load image NETw4v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw4v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys


Probably caused by : NETw4v64.sys ( NETw4v64+77410 )

Followup: MachineOwner
---------

0: kd> ! analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000143c0000007c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001eb3163, address which referenced memory

Debugging Details:
------------------




WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000207c080
0000143c0000007c

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeAcquireSpinLockRaiseToDpc+13
fffff800`01eb3163 f0480fba2900 lock bts qword ptr [rcx],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SecondLife.exe

TRAP_FRAME: fffffa6010063890 -- (.trap 0xfffffa6010063890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000143c0000007c
rdx=fffffa800acdb110 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001eb3163 rsp=fffffa6010063a20 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000002 r10=f93e301e1f3e2f7d
r11=fffffa6010063b30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeAcquireSpinLockRaiseToDpc+0x13:
fffff800`01eb3163 f0480fba2900 lock bts qword ptr [rcx],0 ds:0000143c`0000007c=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ea812e to fffff80001ea8390

STACK_TEXT:
fffffa60`10063748 fffff800`01ea812e : 00000000`0000000a 0000143c`0000007c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`10063750 fffff800`01ea700b : 00000000`00000001 fffffa60`10063970 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`10063890 fffff800`01eb3163 : fffffa80`09b62000 fffffa80`08850510 fffffa80`08cac840 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`10063a20 fffffa60`0367d410 : fffffa60`04f15000 00000000`069d0060 01c87b80`00001000 fffffa60`036a461c : nt!KeAcquireSpinLockRaiseToDpc+0x13
fffffa60`10063a50 fffffa60`04f15000 : 00000000`069d0060 01c87b80`00001000 fffffa60`036a461c fffffa80`08f56cc0 : NETw4v64+0x77410
fffffa60`10063a58 00000000`069d0060 : 01c87b80`00001000 fffffa60`036a461c fffffa80`08f56cc0 00001f80`00620078 : 0xfffffa60`04f15000
fffffa60`10063a60 01c87b80`00001000 : fffffa60`036a461c fffffa80`08f56cc0 00001f80`00620078 00000000`00000000 : 0x69d0060
fffffa60`10063a68 fffffa60`036a461c : fffffa80`08f56cc0 00001f80`00620078 00000000`00000000 fffffa80`09b62040 : 0x1c87b80`00001000
fffffa60`10063a70 fffffa80`08f56cc0 : 00001f80`00620078 00000000`00000000 fffffa80`09b62040 00000000`00000000 : NETw4v64+0x9e61c
fffffa60`10063a78 00001f80`00620078 : 00000000`00000000 fffffa80`09b62040 00000000`00000000 00000000`00000000 : 0xfffffa80`08f56cc0
fffffa60`10063a80 00000000`00000000 : fffffa80`09b62040 00000000`00000000 00000000`00000000 00000000`00000002 : 0x1f80`00620078
fffffa60`10063a88 fffffa80`09b62040 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : 0x0
fffffa60`10063a90 00000000`00000000 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`09b62040
fffffa60`10063a98 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063aa0 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063aa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffffa60`10063ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063ae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063af0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063af8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`10063b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08211840 : 0x0
fffffa60`10063b08 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08211840 fffffa60`0361a871 : 0x0
fffffa60`10063b10 00000000`00000000 : 00000000`00000000 fffffa80`08211840 fffffa60`0361a871 00000000`069d00e9 : 0x0
fffffa60`10063b18 00000000`00000000 : fffffa80`08211840 fffffa60`0361a871 00000000`069d00e9 fffffa80`08f54950 : 0x0
fffffa60`10063b20 fffffa80`08211840 : fffffa60`0361a871 00000000`069d00e9 fffffa80`08f54950 fffffa80`09b69e60 : 0x0
fffffa60`10063b28 fffffa60`0361a871 : 00000000`069d00e9 fffffa80`08f54950 fffffa80`09b69e60 fffffa60`0367e350 : 0xfffffa80`08211840
fffffa60`10063b30 00000000`069d00e9 : fffffa80`08f54950 fffffa80`09b69e60 fffffa60`0367e350 fffffa80`0acdb110 : NETw4v64+0x14871
fffffa60`10063b38 fffffa80`08f54950 : fffffa80`09b69e60 fffffa60`0367e350 fffffa80`0acdb110 fffffa60`0367deee : 0x69d00e9
fffffa60`10063b40 fffffa80`09b69e60 : fffffa60`0367e350 fffffa80`0acdb110 fffffa60`0367deee fffffa80`08cace30 : 0xfffffa80`08f54950
fffffa60`10063b48 fffffa60`0367e350 : fffffa80`0acdb110 fffffa60`0367deee fffffa80`08cace30 fffffa80`08211840 : 0xfffffa80`09b69e60
fffffa60`10063b50 fffffa80`0acdb110 : fffffa60`0367deee fffffa80`08cace30 fffffa80`08211840 fffffa80`0857c9b0 : NETw4v64+0x78350
fffffa60`10063b58 fffffa60`0367deee : fffffa80`08cace30 fffffa80`08211840 fffffa80`0857c9b0 fffffa80`09b69e60 : 0xfffffa80`0acdb110
fffffa60`10063b60 fffffa80`08cace30 : fffffa80`08211840 fffffa80`0857c9b0 fffffa80`09b69e60 fffffa80`09b69e60 : NETw4v64+0x77eee
fffffa60`10063b68 fffffa80`08211840 : fffffa80`0857c9b0 fffffa80`09b69e60 fffffa80`09b69e60 fffffa60`0367e812 : 0xfffffa80`08cace30
fffffa60`10063b70 fffffa80`0857c9b0 : fffffa80`09b69e60 fffffa80`09b69e60 fffffa60`0367e812 00000000`00000010 : 0xfffffa80`08211840
fffffa60`10063b78 fffffa80`09b69e60 : fffffa80`09b69e60 fffffa60`0367e812 00000000`00000010 fffffa80`09b69e70 : 0xfffffa80`0857c9b0
fffffa60`10063b80 fffffa80`09b69e60 : fffffa60`0367e812 00000000`00000010 fffffa80`09b69e70 00000000`0000000d : 0xfffffa80`09b69e60
fffffa60`10063b88 fffffa60`0367e812 : 00000000`00000010 fffffa80`09b69e70 00000000`0000000d fffffa80`0acdb110 : 0xfffffa80`09b69e60
fffffa60`10063b90 00000000`00000010 : fffffa80`09b69e70 00000000`0000000d fffffa80`0acdb110 fffffa60`0367e350 : NETw4v64+0x78812
fffffa60`10063b98 fffffa80`09b69e70 : 00000000`0000000d fffffa80`0acdb110 fffffa60`0367e350 fffff800`01eb1d7c : 0x10
fffffa60`10063ba0 00000000`0000000d : fffffa80`0acdb110 fffffa60`0367e350 fffff800`01eb1d7c 00000000`00000010 : 0xfffffa80`09b69e70
fffffa60`10063ba8 fffffa80`0acdb110 : fffffa60`0367e350 fffff800`01eb1d7c 00000000`00000010 00000000`00000246 : 0xd
fffffa60`10063bb0 fffffa60`0367e350 : fffff800`01eb1d7c 00000000`00000010 00000000`00000246 fffffa60`10063be8 : 0xfffffa80`0acdb110
fffffa60`10063bb8 fffff800`01eb1d7c : 00000000`00000010 00000000`00000246 fffffa60`10063be8 00000000`00000018 : NETw4v64+0x78350
fffffa60`10063bc0 00000000`00000010 : 00000000`00000246 fffffa60`10063be8 00000000`00000018 fffffa80`0b968de0 : nt!KeReleaseSpinLock+0xc
fffffa60`10063bc8 00000000`00000246 : fffffa60`10063be8 00000000`00000018 fffffa80`0b968de0 fffffa60`0366b09e : 0x10
fffffa60`10063bd0 fffffa60`10063be8 : 00000000`00000018 fffffa80`0b968de0 fffffa60`0366b09e 00000000`00000000 : 0x246
fffffa60`10063bd8 00000000`00000018 : fffffa80`0b968de0 fffffa60`0366b09e 00000000`00000000 00000000`00000000 : 0xfffffa60`10063be8
fffffa60`10063be0 fffffa80`0b968de0 : fffffa60`0366b09e 00000000`00000000 00000000`00000000 fffffa80`08cac840 : 0x18
fffffa60`10063be8 fffffa60`0366b09e : 00000000`00000000 00000000`00000000 fffffa80`08cac840 fffffa80`08850510 : 0xfffffa80`0b968de0
fffffa60`10063bf0 00000000`00000000 : 00000000`00000000 fffffa80`08cac840 fffffa80`08850510 fffffa80`0acdb110 : NETw4v64+0x6509e
fffffa60`10063bf8 00000000`00000000 : fffffa80`08cac840 fffffa80`08850510 fffffa80`0acdb110 fffffa60`0361150e : 0x0
fffffa60`10063c00 fffffa80`08cac840 : fffffa80`08850510 fffffa80`0acdb110 fffffa60`0361150e 00000000`00000000 : 0x0
fffffa60`10063c08 fffffa80`08850510 : fffffa80`0acdb110 fffffa60`0361150e 00000000`00000000 00000000`00000001 : 0xfffffa80`08cac840
fffffa60`10063c10 fffffa80`0acdb110 : fffffa60`0361150e 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`08850510
fffffa60`10063c18 fffffa60`0361150e : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`0acdb110
fffffa60`10063c20 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : NETw4v64+0xb50e
fffffa60`10063c28 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa60`03820770 : 0x0
fffffa60`10063c30 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa60`03820770 00000000`00000000 : 0x1
fffffa60`10063c38 00000000`00000000 : 00000000`00000000 fffffa60`03820770 00000000`00000000 fffffa60`036293b4 : 0x0
fffffa60`10063c40 00000000`00000000 : fffffa60`03820770 00000000`00000000 fffffa60`036293b4 00000000`00000010 : 0x0
fffffa60`10063c48 fffffa60`03820770 : 00000000`00000000 fffffa60`036293b4 00000000`00000010 fffffa80`0acdb110 : 0x0
fffffa60`10063c50 00000000`00000000 : fffffa60`036293b4 00000000`00000010 fffffa80`0acdb110 fffffa80`07c504d0 : NETw4v64+0x21a770
fffffa60`10063c58 fffffa60`036293b4 : 00000000`00000010 fffffa80`0acdb110 fffffa80`07c504d0 fffffa80`09053460 : 0x0
fffffa60`10063c60 00000000`00000010 : fffffa80`0acdb110 fffffa80`07c504d0 fffffa80`09053460 fffffa80`00000010 : NETw4v64+0x233b4
fffffa60`10063c68 fffffa80`0acdb110 : fffffa80`07c504d0 fffffa80`09053460 fffffa80`00000010 fffffa80`08f21420 : 0x10
fffffa60`10063c70 fffffa80`07c504d0 : fffffa80`09053460 fffffa80`00000010 fffffa80`08f21420 fffffa80`07c504d0 : 0xfffffa80`0acdb110
fffffa60`10063c78 fffffa80`09053460 : fffffa80`00000010 fffffa80`08f21420 fffffa80`07c504d0 00000000`00000001 : 0xfffffa80`07c504d0
fffffa60`10063c80 fffffa80`00000010 : fffffa80`08f21420 fffffa80`07c504d0 00000000`00000001 fffffa80`000000a9 : 0xfffffa80`09053460


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw4v64+77410
fffffa60`0367d410 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: NETw4v64+77410

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw4v64

IMAGE_NAME: NETw4v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47d90554

FAILURE_BUCKET_ID: X64_0xA_W_NETw4v64+77410

BUCKET_ID: X64_0xA_W_NETw4v64+77410

Followup: MachineOwner
---------

jcgriff2

Hi Rob. . .

Two more items that I'd like to take a look at if you don't mind -

1. Another look at the CBS log, but from a different angle (the command differs slightly - as does the output file)

Go to an ELEVATED command prompt (START | type cmd.exe in the Start Search box | right-click on cmd.exe | select Run as Administrator) -
Type/paste the following EXACTLY as it appears:

findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log >c:\CBSlog18.txt

To paste it in the "DOS" box, go to the top and right-click then select edit. that will alow you to paste and will execute the command instantly.
Go into Windows Explorer and locate the file c:\CBSlog18.txt in the c: root.

2. Another Belarc Advisor report.

Please send both to me via Email. As before, please be sure to include your screen name in the subject area and a link to this thread in the body. Thanks.

Also - be sure to review the post by dai - a few posts above this.

Regards. . .

jcgriff2 (JC)

RPracic

Hi everyone,

I hope you have all had an excellent few weeks!

First off, my most sincere apologies for the late reply in this thread. I've been extremely busy lately (not even home half the time), and when I am around, I've been fighting this laptop into submission. I have made some "developments", if you will, in the problem.

JC - I will get that info for you and send it to your e-mail very shortly. Thank you very much for all the help you've provided!!

Dai - thanks for the tip. However, no offense, but your "solution" is a workaround, not a "fix", per se. Disabling wireless is something I would have done long ago if it didn't bother me. But not only do I need to use wireless quite often (I'm on the go all the time), but it would be on the back of my mind all the time that I've simply gone "around" the problem instead of actually fixing it. Still - I do appreciate your help very much!!
The problem still occured even before I had Vista SP1. Nonetheless, I went back to non-SP1, and problem was still there. Blue screen after a few hours of "extreme" use of the wireless card (sending/recieving files, MSN/skype, browsing, etc.)


My best solution so far has been to:
1. Close MSN and Skype whenever possible.
2. Transfer files in small amounts only (ie; one file at a time, small chunks of big files at one time).
3. Minimize bandwidth usage for any given time.
4. Don't do 10 different things at once.

The biggest thing for me was to stop using BitComet. I do have another laptop and I now let it do all of my transfers. I use an external hard drive to transfer files from this laptop to my other one, and then the other one can use BitComet to get my clients what they need... or to download from them. Disabling BitComet has lowered the amount of BSOD's from one a day to 2-3 a week.


Basically, I have determined beyond a doubt that it's the wireless card AND/OR Vista/Intel drivers that's causing the problem.


I just want to say thanks again to everyone who has supported me in this seemingly endless effort to stop the BSODs. You have all been a tremendous help, and I sincerely appreciate it all!! Thank you!


P.S. - I also have some dump reports, which I have just included here. I don't think they'll uncover anything we don't already know. But you never know... it is a computer after all.

Attached Files

MemoryDumpsNew.zip (108.0 KB, 1 views)

dai

the solution was posted as a work around until new drivers are available
it was not posted as the end solution

RPracic

Ok, fair enough. Like I said - I certainly do not mean any offense!!
I honestly do appreciate the suggestions! If I was doing this on my own, I would still be in the dark age and wouldn't even know what the problem is to begin with.

I do disable the wireless card whenever it is not in use, so as to not be wasteful.

Thanks again!!

-Rob

jcgriff2

Hi Rob. . .

As you predicted, the same Intel wireless driver was the cause of the most recent BSODs from 4-15 to 4-21.

I have seen this same adapter show up in other recent cases. I do hope that Intel provides a hot fix for this soon for you and others.

It has been a pleasure on this end working with you. I could not ask for more willing participant in doing everything possible in the search for a solution. If I come across anything that may help, I will get it to you.

Regards. . .

jcgriff2 (JC)

RPracic

JC,

Thanks very much for all of your support! It's been a great experience, and I certainly learned a lot about not only this specific problem, but some general things about computers. I appreciate you taking time out of your busy schedule to help me out!

I guess I'll call this one "Worked around" for now.. not quite fixed, but I think I can live with it. The average work day doesn't put enough strain on it to cause a Blue Screen - its just when I push it overboard. And even then, I can usually see it coming from a mile away so its not too big a deal.

I look forward to hopefully hearing from you again soon... maybe with some good news!
If I find anything, I'll be sure to post back here ASAP to let anyone know who may have been following the topic.


Good luck to all others with this issue (and any other problems encountered), and thanks again for all the help!

Have a good weekend!

-Rob

philfna

I think this is a great thread. At least I am not crazy. I have the exact same problem. I hope Intel updates the driver soon.

I opened a trouble ticket with Microsoft.