blue screen twice

NathanP2007 · Nov 11, 2009

So idk if theres anything you guys can help with, but its just weird, i was watchung Hulu desktop last night and my computer crashed twice to blue screen ( i have been watching hulu desktop for 3 weeks and had no issues) but it went blue screen during a episode, comp restarted, i started where i left off and it happened again (not the EXACT same spot). I am not familiar with what blue screen means so any help would be nice.

jusluv2play · Nov 11, 2009

I assume this is happening on the laptop in your sig?

If so, have you changed or updated any video drivers or codecs in the time period you are talking about?

That was the first thing to come to mind for you to check out.

Also, if it blue screens again, try and write down what the error message says and google it or let us know.

NathanP2007 · Nov 11, 2009

jusluv2play said:
I assume this is happening on the laptop in your sig?

If so, have you changed or updated any video drivers or codecs in the time period you are talking about?

That was the first thing to come to mind for you to check out.

Also, if it blue screens again, try and write down what the error message says and google it or let us know.

No sorry for not explaining more, its happening to my PC. Il try to do that, i read when it happened on the blue screen it had something to do with a driver..but that doesnt make a ton of sense to me considering my drivers are fully updated and my computer is freshly new (clean installed Win7) and doesnt have any junk on it. Only thing lately done to change anything is i had the recent windows update (that updated 5 office related things) and i have installed the hulu gadget that makes it so inside of windows media center, you see a hulu gadget..which when you click on it, opens hulu desktop.

NathanP2007 · Nov 13, 2009

Happened again, while installing yahoo messenger and checking Windows live mail. heres the report.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA8F14AA9D48
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800141B355
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\111309-18064-01.dmp
C:\Users\Nathan\AppData\Local\Temp\WER-33353-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

As for what it said on the blue screen, it does say "driver" but i have to see it again to catch more of what it says, considering it goes away so fast.

gimp · Nov 13, 2009

open up System Properties -> Advanced tab -> click Settings under "Startup and Recovery" -> UNcheck "Automatically restart"

now the BSOD will stay on the screen until you restart the computer.

NathanP2007 · Nov 13, 2009

Thank you, i did that, i will update with what it says next time it B-screens. This is really pissing me off though, i have a new computer, its running perfectly, i have a full clean install version of windows 7 pro, i have no weird stuff on my PC, yet its blue screening...it makes me worry about the stability of my PC. I didnt spend $100's of dollars to build a blue screening computer.

Sorry just a small vent.

Tawnos · Nov 13, 2009

From the same place you unchecked "automatically restart", change "write debugging information" to "Kernel memory dump"
Install windbg from http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
Next time you bluscreen, after reboot, launch windbg as admin
Open %SystemRoot%\MEMORY.DMP

From command line, execute the following
.symfix
.reload
!analyze -v

Paste the output

NathanP2007 · Nov 13, 2009

Ok im installing that now, il update the "output" once i get it.

NathanP2007 · Nov 30, 2009

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

1: kd> .symfix
1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 000000000416000c, Memory contents of the pool block
Arg4: fffffa8007083b70, Address of the block of pool being deallocated

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

NathanP2007 · Nov 30, 2009

This is the first time it has been "bad pool caller" the other 3 times were something else, im still waiting for that same one as those 3 to happen again to post those results too. Im worried about my computer...is my computer not stable?

NathanP2007 · Nov 30, 2009

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

POOL_ADDRESS: fffffa8007083b70

FREED_POOL_TAG: OSNL

BUGCHECK_STR: 0xc2_7_OSNL

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Azureus.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002bb960e to fffff80002a87f00

STACK_TEXT:
fffff880`0ab320e8 fffff800`02bb960e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`0416000c : nt!KeBugCheckEx
fffff880`0ab320f0 fffff880`01410ad2 : fffffa80`06241010 00000000`00000000 00000000`00000000 fffffa80`07083b90 : nt!ExFreePool+0xccb
fffff880`0ab321a0 fffff880`01e8805e : fffffa80`05e49310 fffffa80`059ef830 00000000`00000000 00000000`00000002 : ndis!NdisFreeNetBufferList+0x112
fffff880`0ab321d0 fffff880`01e1d5bb : fffffa80`06bee210 fffffa80`06267020 00000000`00000000 fffffa80`03c87fd0 : MRVW24C+0x105e
fffff880`0ab32200 fffff880`01e1f643 : fffffa80`06bee210 fffffa80`06bee210 fffffa80`03dbdc40 00000000`00000000 : nwifi!WPP_SF_dll+0x3ab
fffff880`0ab32240 fffff880`01497484 : fffffa80`04f941a0 00000000`00000000 00000000`00000000 00000000`00000000 : nwifi!MP6ReturnNBL+0x4b
fffff880`0ab32270 fffff880`014cd17b : fffffa80`06270bb0 fffffa80`04f941a0 00000000`00000000 fffffa80`0429ac80 : ndis!ndisReturnNetBufferListsInternal+0x94
fffff880`0ab322b0 fffff880`01672ff5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisReturnNetBufferLists+0x3b
fffff880`0ab322f0 fffff880`01503173 : 00000000`ffffffff 00000000`00000001 00000000`00000001 00000000`00000000 : tcpip!FlpReturnNetBufferListChain+0x95
fffff880`0ab32340 fffff880`0166cd41 : fffffa80`06bee210 00000000`00000000 fffff880`0ab323e0 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0xf3
fffff880`0ab323c0 fffff880`02c9560d : 00000000`ffffffff fffffa80`06bee210 fffff880`0ab32c60 fffffa80`06d9a350 : tcpip!TcpReleaseIndicationList+0x81
fffff880`0ab323f0 fffff880`02cd6995 : fffff880`0ab32930 fffffa80`06d9a350 00000000`ffffffff 00000000`00000000 : afd!AfdTLReleaseIndications+0x2d
fffff880`0ab32440 fffff880`02cbf051 : 00000000`00000000 00000000`00000000 00000000`00700000 fffff880`0ff3c299 : afd!AfdFastConnectionReceive+0xb65
fffff880`0ab32660 fffff800`02da0113 : 00000000`00004019 fffffa80`040f2310 00000000`058ef440 00000000`00000001 : afd!AfdFastIoDeviceControl+0x1041
fffff880`0ab329d0 fffff800`02da0c06 : fffff880`0ab32bb8 00000000`00000f10 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`0ab32b00 fffff800`02a87153 : fffff880`0ab32c60 fffffa80`052269b0 fffff880`0ab32bb8 fffff800`02da3d00 : nt!NtDeviceIoControlFile+0x56
fffff880`0ab32b70 00000000`72f52dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0581f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72f52dd9

STACK_COMMAND: kb

FOLLOWUP_IP:
MRVW24C+105e
fffff880`01e8805e 488bf3 mov rsi,rbx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: MRVW24C+105e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MRVW24C

IMAGE_NAME: MRVW24C.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 472551f7

FAILURE_BUCKET_ID: X64_0xc2_7_OSNL_MRVW24C+105e

BUCKET_ID: X64_0xc2_7_OSNL_MRVW24C+105e

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

Arainach · Nov 30, 2009

Sounds like Azureus installed a bad driver. Past that, are you running at stock speeds?

NathanP2007 · Nov 30, 2009

Oh good, yeah i had Azureus running so i was curious if that was the cause. Yeah stock speeds. Is there anything you can do about the Azureus driver? or just deal with it?

NathanP2007 · Dec 1, 2009

Blue screen again , but its the one i have gotten before multiple times, here are the results

*
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000000a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88005861fcd, address which referenced memory

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

*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys

READ_ADDRESS: 000000000000000a

CURRENT_IRQL: 2

FAULTING_IP:
nwifi!Dot11PacketConverterReceivePacket+139
fffff880`05861fcd f6410a05 test byte ptr [rcx+0Ah],5

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002f1b170 -- (.trap 0xfffff88002f1b170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80067c16c0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80063cd010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005861fcd rsp=fffff88002f1b300 rbp=0000000000000012
r8=fffffa8004a04570 r9=fffffa8003b3fdf0 r10=fffffa80063ff380
r11=fffffa8003a87430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nwifi!Dot11PacketConverterReceivePacket+0x139:
fffff880`05861fcd f6410a05 test byte ptr [rcx+0Ah],5 ds:0001:00000000`0000000a=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abb469 to fffff80002abbf00

STACK_TEXT:
fffff880`02f1b028 fffff800`02abb469 : 00000000`0000000a 00000000`0000000a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b030 fffff800`02aba0e0 : fffffa80`046c6690 fffffa80`067c4a70 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b170 fffff880`05861fcd : fffffa80`03a87430 fffffa80`067c4a70 fffffa80`067c4a70 fffffa80`069e5510 : nt!KiPageFault+0x260
fffff880`02f1b300 fffff880`05861643 : fffffa80`067c4a70 fffffa80`0618ec40 00000000`00000000 fffffa80`067c4a70 : nwifi!Dot11PacketConverterReceivePacket+0x139
fffff880`02f1b340 fffff880`01494484 : fffffa80`05d451a0 fffff880`02f1b400 00000000`00000000 fffffa80`063db010 : nwifi!MP6ReturnNBL+0x4b
fffff880`02f1b370 fffff880`0149b56c : fffffa80`05d451a0 fffffa80`05775ca0 fffff880`02f1b4a8 00000000`00000000 : ndis!ndisReturnNetBufferListsInternal+0x94
fffff880`02f1b3b0 fffff880`01416a24 : fffffa80`05d451a0 00000000`00000001 00000000`00000002 fffffa80`03a87430 : ndis! ?? :

KGKHJNI::`string'+0x3df8
fffff880`02f1b830 fffff880`014169e9 : 00000000`00000000 00000000`00000000 fffffa80`063fd020 00000000`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff880`02f1b870 fffff880`01416980 : fffff880`058975c0 fffffa80`063cd010 fffffa80`063fd020 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`02f1b8b0 fffff880`058607ee : fffffa80`063cd010 00000000`00000000 fffffa80`03a87430 fffff880`058975c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`02f1b8f0 fffff880`0142e2b7 : fffffa80`05d451a0 fffffa80`03b3fdf0 00000000`00000001 fffffa80`05d42a50 : nwifi!Pt6Receive+0x296
fffff880`02f1b950 fffff880`0428ca0f : fffffa80`0606aad0 fffffa80`05d10000 00000000`00000001 fffffa80`05d17190 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff880`02f1b9a0 fffff880`042918be : 00000000`00010000 fffffa80`0606aad0 fffffa80`05e2c92c 00000000`00000000 : MRVW24C+0x1a0f
fffff880`02f1ba30 fffff880`0429e5f4 : fffff880`00000231 fffffa80`05e2c98f fffffa80`05e2c5da fffffa80`0592a680 : MRVW24C+0x68be
fffff880`02f1ba60 fffff880`0429eb9a : 00000000`00000040 fffffa80`05e2c5da 00000000`00000000 00000000`00000000 : MRVW24C+0x135f4
fffff880`02f1bab0 fffff880`0429e9f2 : fffffa80`05e2c5da fffffa80`0606a2f0 fffffa80`05d66000 00000000`00000000 : MRVW24C+0x13b9a
fffff880`02f1bb10 fffff880`042915fd : fffffa80`05d66000 00000000`00000001 fffffa80`0606a2f0 00000000`01ca724d : MRVW24C+0x139f2
fffff880`02f1bb40 fffff880`042b7310 : fffffa80`05d10000 00000000`00000000 fffffa80`05d451a0 fffffa80`05d110a8 : MRVW24C+0x65fd
fffff880`02f1bba0 fffff880`042b2351 : fffffa80`05d4b010 fffffa80`05d451a0 fffffa80`05d4b500 00000000`00000000 : MRVW24C+0x2c310
fffff880`02f1bbf0 fffff880`0428f4b8 : fffffa80`05d4b500 fffff880`0428eed2 fffffa80`05d41880 fffffa80`05d4b010 : MRVW24C+0x27351
fffff880`02f1bc20 fffff880`0149308e : fffffa80`05d4b4fd fffffa80`05d451a0 fffffa80`05d4b500 00000000`00000000 : MRVW24C+0x44b8
fffff880`02f1bc60 fffff800`02ac75dc : fffff880`009e7180 fffffa80`05d4b53d fffffa80`05d4b4fd 00000000`00000000 : ndis!ndisMTimerDpcX+0x7e
fffff880`02f1bc90 fffff800`02ac46fa : fffff880`009e7180 fffff880`009f1f40 00000000`00000000 fffff880`01493010 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
nwifi!Dot11PacketConverterReceivePacket+139
fffff880`05861fcd f6410a05 test byte ptr [rcx+0Ah],5

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nwifi!Dot11PacketConverterReceivePacket+139

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME: nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b

FAILURE_BUCKET_ID: X64_0xD1_nwifi!Dot11PacketConverterReceivePacket+139

BUCKET_ID: X64_0xD1_nwifi!Dot11PacketConverterReceivePacket+139

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

NathanP2007 · Dec 1, 2009

Just happened again

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000012deca, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

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

*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x4E_7

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002b2b5b9 to fffff80002ac8f00

STACK_TEXT:
fffff800`00ba1198 fffff800`02b2b5b9 : 00000000`0000004e 00000000`00000007 00000000`0012deca 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba11a0 fffff800`02b3c12e : fffff800`02c41e80 fffffa80`03bce001 fffff800`00ba1200 fffffa80`063f5010 : nt! ?? ::FNODOBFM::`string'+0x16e06
fffff800`00ba11e0 fffff800`02acb2d8 : fffffa80`0591000c 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34989
fffff800`00ba1270 fffff880`02c76179 : 00000000`00000000 fffffa80`03bce002 fffffa80`051057d0 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff800`00ba1350 fffff880`0164622f : fffff800`00ba1578 fffffa80`06209980 00000000`00000000 fffff800`00ba1530 : afd!AfdTLCompleteBufferUserReceive+0x159
fffff800`00ba1450 fffff880`0167c7e6 : 00000000`000005b4 fffffa80`03f9f7c0 fffffa80`03f9f7c0 00000000`00000000 : tcpip!TcpSatisfyReceiveRequests+0x43f
fffff800`00ba1730 fffff880`0167d2f9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpDeliverDataToClient+0x106
fffff800`00ba18b0 fffff880`01676af8 : 00000001`bc8f6c6f fffff800`00ba1c50 fffffa80`03f9f802 fffff880`0166f64a : tcpip!TcpDeliverReceive+0xa9
fffff800`00ba19b0 fffff880`016776f5 : 00000000`00000014 00000000`00000000 fffffa80`0485e000 fffffa80`0575f3f0 : tcpip!TcpTcbFastDatagram+0x208
fffff800`00ba1b70 fffff880`0167c0ca : fffffa80`04869410 fffffa80`06545080 fffffa80`04829760 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5
fffff800`00ba1d20 fffff880`0167bc17 : fffffa80`05aca154 fffffa80`0485e000 00000000`00000000 fffff880`0165f400 : tcpip!TcpMatchReceive+0x1fa
fffff800`00ba1e70 fffff880`0165e3c7 : fffffa80`04858f07 fffffa80`0484ffc5 fffffa80`04868f07 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177
fffff800`00ba1f20 fffff880`0165e499 : fffff800`00ba20a0 fffff880`0176e9a0 fffff800`00ba20b0 00000000`00000001 : tcpip!IppDeliverListToProtocol+0x97
fffff800`00ba1fe0 fffff880`0165e990 : fffffa80`0485e000 fffffa80`06a02ba8 fffffa80`05287d20 fffff800`00ba20a0 : tcpip!IppProcessDeliverList+0x59
fffff800`00ba2050 fffff880`0165d821 : 2400000b`b2701a00 fffffa80`0485e000 fffff880`0176e9a0 00000000`063f4b01 : tcpip!IppReceiveHeaderBatch+0x231
fffff800`00ba2130 fffff880`0165c272 : fffffa80`063da5a0 00000000`00000000 fffffa80`063f4b01 fffff800`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff800`00ba2330 fffff880`016756ba : fffffa80`063f4bb0 fffff800`00ba2460 fffffa80`063f4bb0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff800`00ba2410 fffff800`02ad864a : fffffa80`064b6eb0 fffff800`00b9d000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`00ba2460 fffff880`016750e2 : fffff880`016755e0 fffff800`00ba2570 fffff800`02c41e02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff800`00ba2540 fffff880`0158a0eb : fffffa80`063f5010 00000000`00000000 fffffa80`04fc21a0 fffffa80`04fc21a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff800`00ba25b0 fffff880`01553fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff800`00ba2620 fffff880`014d6a24 : fffffa80`04fc21a0 00000000`00000002 00000000`00000001 fffffa80`064b6eb0 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff800`00ba2aa0 fffff880`014d69e9 : 00000000`00000000 00000000`00000000 fffffa80`063d8020 00000000`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff800`00ba2ae0 fffff880`014d6980 : fffff880`056ad5c0 fffffa80`062a6010 fffffa80`063d8020 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff800`00ba2b20 fffff880`056767ee : fffffa80`062a6010 00000000`00000000 fffffa80`064b6eb0 fffff880`056ad5c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff800`00ba2b60 fffff880`014ee2b7 : fffffa80`04fc21a0 fffffa80`03fdf5c0 00000000`00000001 fffff880`03c16e64 : nwifi!Pt6Receive+0x296
fffff800`00ba2bc0 fffff880`05700a0f : fffffa80`05b01220 fffffa80`0496c000 00000000`00000001 fffffa80`055c1c20 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff800`00ba2c10 fffff880`057058be : 00000000`00010000 fffffa80`05b01220 fffffa80`05a17927 00000000`00000000 : MRVW24C+0x1a0f
fffff800`00ba2ca0 fffff880`057125f4 : 00000000`00000604 fffffa80`05a17967 fffffa80`05a175da fffffa80`055c2680 : MRVW24C+0x68be
fffff800`00ba2cd0 fffff880`05712b9a : 00000000`00000040 fffffa80`05a175da 00000000`00000000 00000000`00000000 : MRVW24C+0x135f4
fffff800`00ba2d20 fffff880`057129f2 : fffffa80`05a175da fffffa80`05b01220 fffffa80`05951000 00000000`00000000 : MRVW24C+0x13b9a
fffff800`00ba2d80 fffff880`057055fd : fffffa80`05951000 00000000`00000001 fffffa80`05b01220 00000000`01ca725e : MRVW24C+0x139f2
fffff800`00ba2db0 fffff880`0572b310 : fffffa80`0496c000 00000000`00000000 fffffa80`04fc21a0 fffffa80`0496cdb0 : MRVW24C+0x65fd
fffff800`00ba2e10 fffff880`05726351 : fffffa80`05114660 fffffa80`04fc21a0 fffffa80`05114b00 00000000`00000000 : MRVW24C+0x2c310
fffff800`00ba2e60 fffff880`057034b8 : fffffa80`05114b00 fffff880`05702ed2 fffffa80`054d5310 fffffa80`05114660 : MRVW24C+0x27351
fffff800`00ba2e90 fffff880`0155308e : fffffa80`05114b4d fffffa80`04fc21a0 fffffa80`05114b00 00000000`00000000 : MRVW24C+0x44b8
fffff800`00ba2ed0 fffff800`02ad45dc : fffff800`02c41e80 fffffa80`05114b8d fffffa80`05114b4d 00000000`00000000 : ndis!ndisMTimerDpcX+0x7e
fffff800`00ba2f00 fffff800`02acf065 : 00000000`00000000 fffffa80`03f66760 00000000`00000000 fffff880`01553010 : nt!KiRetireDpcList+0x1bc
fffff800`00ba2fb0 fffff800`02acee7c : fffffa80`039b0840 fffff800`02a18895 fffff800`02a3d301 fffff880`09712c60 : nt!KxRetireDpcList+0x5
fffff880`09712ba0 fffff800`02b14793 : fffff800`02ac48e3 fffff800`02ac494f fffffa80`03f66760 00000000`00000000 : nt!KiDispatchInterruptContinue
fffff880`09712bd0 fffff800`02ac494f : fffffa80`03f66760 00000000`00000000 00000000`00000000 fffffa80`03a5b880 : nt!KiDpcInterruptBypass+0x13
fffff880`09712be0 00000000`71f6ead6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x19f
00000000`0020ef5c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x71f6ead6

STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdTLCompleteBufferUserReceive+159
fffff880`02c76179 f0834530ff lock add dword ptr [rbp+30h],0FFFFFFFFh

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: afd!AfdTLCompleteBufferUserReceive+159

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184

FAILURE_BUCKET_ID: X64_0x4E_7_afd!AfdTLCompleteBufferUserReceive+159

BUCKET_ID: X64_0x4E_7_afd!AfdTLCompleteBufferUserReceive+159

Followup: MachineOwner

Tawnos · Dec 1, 2009

Your (wireless) network drivers are causing the problem. What driver version are you running, and have you tried updating it with windows update?

number69 · Dec 1, 2009

Step 1, test your memory, step 2, test your drive. Whenever I come across random blue screens I always test the hardware first, that's just me.

NathanP2007 · Dec 1, 2009

Well as for my wireless adapter, it shows as only having one driver version (1.0) on their website. Windows update has nothing for me to update. I noticed under the driver specs that windows 7 isnt listed as its officially compatible. I have the Linksys Wireless N adapter. WUSB300N model.

As for testing memeory and testing my "drive". Idk how to do either.

Tawnos · Dec 1, 2009

number69 said:
Step 1, test your memory, step 2, test your drive. Whenever I come across random blue screens I always test the hardware first, that's just me.

It's not memory or his drive. Look at the crash dumps, they're all caused by the wifi driver.

Nathan, this is not an officially recommended solution, but you can try a generic marvell driver, since that's the chipset used.

http://www.marvell.com/drivers/driverDisplay.do?driverId=207

number69 · Dec 1, 2009

Tawnos said:
It's not memory or his drive. Look at the crash dumps, they're all caused by the wifi driver.

Nathan, this is not an officially recommended solution, but you can try a generic marvell driver, since that's the chipset used.

http://www.marvell.com/drivers/driverDisplay.do?driverId=207

You're probably right but I've seen bad memory cause dumps that pointed to anything from drivers to system files and everything in between...plenty of times. Not saying it is but I would check anyway.

Tawnos · Dec 1, 2009

number69 said:
I've had bad memory cause dumps that pointed to anything from drivers to system files and everything in between. Not saying it is but I would check anyway.

Have you had repeated bad memory dumps with stack traces that all point to the same device, which a quick search of the web will turn up multiple similar issues? Yeah, didn't think so...

number69 · Dec 1, 2009

Yes. Also his second stack trace has some differences.

Hell I even saw a new server blue screen and reboot when installing the same driver over and over..it was defective memory. Replaced the stick installed the driver, no more blue screens or reboots.

Anyway, I think you're probably right but does checking the memory really hurt?

NathanP2007 · Dec 1, 2009

Well what i tried, is i went to the linksys website and installed that 1.0 driver, and it installed fine, when i went and tried the install again to double check something i read, and it said "this driver is already installed are you sure you want to install again?" so im taking that as , considering the first time it didnt say that when i installed it, maybe that driver wasnt officially on my computer..so im gonna stick to that, and if it blue screens again cause of wifi, then il try that "generic marvell driver". Do you have a clue as to how to fix the azureus driver? Would uninstalling the program and reinstalling it work? I havent blue screened from that program ever, and i happen to open it yesterday and it needed a update, i update it, start DL'ing some torrents and 7 hours later bam a blue screen.

Tawnos · Dec 1, 2009

NathanP2007 said:
Well what i tried, is i went to the linksys website and installed that 1.0 driver, and it installed fine, when i went and tried the install again to double check something i read, and it said "this driver is already installed are you sure you want to install again?" so im taking that as , considering the first time it didnt say that when i installed it, maybe that driver wasnt officially on my computer..so im gonna stick to that, and if it blue screens again cause of wifi, then il try that "generic marvell driver". Do you have a clue as to how to fix the azureus driver? Would uninstalling the program and reinstalling it work? I havent blue screened from that program ever, and i happen to open it yesterday and it needed a update, i update it, start DL'ing some torrents and 7 hours later bam a blue screen.

Azureus (now Vuze, btw) doesn't have a driver. It's a java bittorrent client, running in a sandbox. The message you got about it already being installed is because you installed it once before.

Tawnos · Dec 1, 2009

number69 said:
Yes. Also his second stack trace has some differences.

Hell I even saw a new server blue screen and reboot when installing the same driver over and over..it was defective memory. Replaced the stick installed the driver, no more blue screens or reboots.

Anyway, I think you're probably right but does checking the memory really hurt?

The second stack trace is another part of the same driver...

First:
fffff880`0ab321d0 fffff880`01e1d5bb : fffffa80`06bee210 fffffa80`06267020 00000000`00000000 fffffa80`03c87fd0 : MRVW24C+0x105e

Second:
fffff880`02f1ba30 fffff880`0429e5f4 : fffff880`00000231 fffffa80`05e2c98f fffffa80`05e2c5da fffffa80`0592a680 : MRVW24C+0x68be

Third (note, same calling location, different arguments):
fffff800`00ba2ca0 fffff880`057125f4 : 00000000`00000604 fffffa80`05a17967 fffffa80`05a175da fffffa80`055c2680 : MRVW24C+0x68be

number69 · Dec 1, 2009

Tawnos said:
The second stack trace is another part of the same driver...

First:
fffff880`0ab321d0 fffff880`01e1d5bb : fffffa80`06bee210 fffffa80`06267020 00000000`00000000 fffffa80`03c87fd0 : MRVW24C+0x105e

Second:
fffff880`02f1ba30 fffff880`0429e5f4 : fffff880`00000231 fffffa80`05e2c98f fffffa80`05e2c5da fffffa80`0592a680 : MRVW24C+0x68be

Third (note, same calling location, different arguments):
fffff800`00ba2ca0 fffff880`057125f4 : 00000000`00000604 fffffa80`05a17967 fffffa80`05a175da fffffa80`055c2680 : MRVW24C+0x68be

I've seen defective memory cause the same stack traces as I mentioned above. In other words defective memory could cause problems with the same driver, it may not be the driver itself. You may want to lose the attitude also, I was just throwing out a suggestion for the guy.

NathanP2007 · Dec 1, 2009

How about helping the original poster? lol. I still dont know what you guys are talking bout barely, and i havent gotten any solutions that are applicable except Tawnos's Marvell driver idea. If Vuze doesnt have a driver, then what can i fix to make it not blue screen with the reason being vuze.

And i know i couldnt install it cause it already was, my point was that it let me install it the first time just fine...implying (at least to me) that it wasnt installed on my computer already. Cause if it was ,it would have said that pop up the first time.

number69 · Dec 1, 2009

NathanP2007 said:
How about helping the original poster? lol. I still dont know what you guys are talking bout barely, and i havent gotten any solutions that are applicable except Tawnos's Marvell driver idea. If Vuze doesnt have a driver, then what can i fix to make it not blue screen with the reason being vuze.

And i know i couldnt install it cause it already was, my point was that it let me install it the first time just fine...implying (at least to me) that it wasnt installed on my computer already. Cause if it was ,it would have said that pop up the first time.

If you read what I posted it is applicable IMO. To test your memory you could download UBCD(Ultimate Boot CD)........ not UBCD4win, that's different....... burn UBCD(Ultimate Boot CD) to a cd and boot from it, then run memtest. I'm just trying to give you another suggestion, not saying it's definitely the problem, it could very well be the driver which was working without issue for three weeks...as you mentioned. Google is great but so is process of elimination. Sometimes what looks to be the obvious answer is not and sometimes it is when dealing with this stuff. Process of elimination.

NathanP2007 · Dec 1, 2009

What you said NOW is applicable, and i thank you for it. I'll try that out tonight. How do i know if i failed or pasted the test of UBCD then memtest?

number69 · Dec 1, 2009

NathanP2007 said:
What you said NOW is applicable, and i thank you for it. I'll try that out tonight. How do i know if i failed or pasted the test of UBCD then memtest?

It'll tell you, you'll get a list of red entries as it runs if it finds problems, let it go for several full passes. If after several full passes you see no red entries you're good to go...usually. This will take some time depending how much ram you have installed. If you want to run it overnight go ahead. You can download memtest86+ by itself as well if you just want that. If it comes up with errors and you have multiple sticks installed you will have to remove one stick at a time and test again. If you're not comfortable with opening your computer and doing this then don't. Let a person who knows what they are doing open it for you and do this.

Tawnos · Dec 1, 2009

NathanP2007 said:
How about helping the original poster? lol. I still dont know what you guys are talking bout barely, and i havent gotten any solutions that are applicable except Tawnos's Marvell driver idea. If Vuze doesnt have a driver, then what can i fix to make it not blue screen with the reason being vuze.

And i know i couldnt install it cause it already was, my point was that it let me install it the first time just fine...implying (at least to me) that it wasnt installed on my computer already. Cause if it was ,it would have said that pop up the first time.

The truth is, if it is the network hardware causing issue, and the generic drivers don't fix it, you'll have to wait for a working driver or get new hardware.

NathanP2007 · Dec 1, 2009

I dont know the chances of Linksys making a new driver for Windows 7 (if thats whats needed to fix it) just cause they have had months of the RC being out to use as a work off point to make a driver, let alone the time the full real 7 has been out. As far as buying a new one, maybe il look into a different brand, cause as for Linksys, the one i got is still their currently sold Wireless Adapter N.

Tawnos · Dec 2, 2009

NathanP2007 said:
I dont know the chances of Linksys making a new driver for Windows 7 (if thats whats needed to fix it) just cause they have had months of the RC being out to use as a work off point to make a driver, let alone the time the full real 7 has been out. As far as buying a new one, maybe il look into a different brand, cause as for Linksys, the one i got is still their currently sold Wireless Adapter N.

Why don't you just try the marvell driver I linked you to?

NathanP2007 · Dec 24, 2009

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

*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: 0000000000000076

CURRENT_IRQL: 2

FAULTING_IP:
MRVW24C+673f
fffff880`0344673f 4c8b4a76 mov r9,qword ptr [rdx+76h]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: firefox.exe

TRAP_FRAME: fffff88002f22b10 -- (.trap 0xfffff88002f22b10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f22cc8 rbx=0000000000000000 rcx=fffffa8005b03000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800344673f rsp=fffff88002f22ca0 rbp=fffffa8005bc992a
r8=0000000000000000 r9=fffff8800176b9a0 r10=ffffffffffabaa30
r11=fffff88002f22c70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
MRVW24C+0x673f:
fffff880`0344673f 4c8b4a76 mov r9,qword ptr [rdx+76h] ds:0180:0076=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ac8469 to fffff80002ac8f00

STACK_TEXT:
fffff880`02f229c8 fffff800`02ac8469 : 00000000`0000000a 00000000`00000076 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f229d0 fffff800`02ac70e0 : fffffa80`03fa84b0 fffffa80`05bc997f fffff880`035be5c0 fffffa80`061e1010 : nt!KiBugCheckDispatch+0x69
fffff880`02f22b10 fffff880`0344673f : 00000000`00010000 fffffa80`05d0c2f0 fffffa80`05bc9929 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f22ca0 fffff880`034535f4 : fffffa80`000005f4 fffffa80`05bc997f fffffa80`05bc95da fffffa80`05662680 : MRVW24C+0x673f
fffff880`02f22cd0 fffff880`03453b9a : 00000000`00000040 fffffa80`05bc95da 00000000`00000000 00000000`00000000 : MRVW24C+0x135f4
fffff880`02f22d20 fffff880`034539f2 : fffffa80`05bc95da fffffa80`05d06ad0 fffffa80`05b03000 00000000`00000000 : MRVW24C+0x13b9a
fffff880`02f22d80 fffff880`034465fd : fffffa80`05b03000 00000000`00000001 fffffa80`05d06ad0 00000000`01ca8508 : MRVW24C+0x139f2
fffff880`02f22db0 fffff880`0346c310 : fffffa80`05858000 00000000`00000000 fffffa80`05a491a0 fffffa80`05858db0 : MRVW24C+0x65fd
fffff880`02f22e10 fffff880`03467351 : fffffa80`05b00010 fffffa80`05a491a0 fffffa80`05b00500 00000000`00000000 : MRVW24C+0x2c310
fffff880`02f22e60 fffff880`034444b8 : fffffa80`05b00500 fffff880`03443ed2 fffffa80`05ae4020 fffffa80`05b00010 : MRVW24C+0x27351
fffff880`02f22e90 fffff880`0157208e : fffffa80`05b004fd fffffa80`05a491a0 fffffa80`05b00500 00000000`0000ffff : MRVW24C+0x44b8
fffff880`02f22ed0 fffff800`02ad45dc : fffff880`009e7180 fffffa80`05b0053d fffffa80`05b004fd 00000000`0000ffff : ndis!ndisMTimerDpcX+0x7e
fffff880`02f22f00 fffff800`02acf065 : 3441582e`3b532b37 fffffa80`0660bb60 00000000`00000000 fffff880`01572010 : nt!KiRetireDpcList+0x1bc
fffff880`02f22fb0 fffff800`02acee7c : fffffa80`0438d840 00000000`7ef5f000 fffff880`09900b01 00000000`05dcec08 : nt!KxRetireDpcList+0x5
fffff880`099008f0 fffff800`02b14793 : fffff800`02ac48e3 fffff800`02ac494f ffffffff`00000001 fffff880`009e7101 : nt!KiDispatchInterruptContinue
fffff880`09900920 fffff800`02ac494f : ffffffff`00000001 fffff880`009e7101 00000000`00000000 00000000`00000001 : nt!KiDpcInterruptBypass+0x13
fffff880`09900930 fffff800`02dba5f3 : 00000000`00000000 fffff880`09900b30 00000000`00000000 fffff800`02adb1ab : nt!KiChainedDispatch+0x19f
fffff880`09900ac0 fffff800`02de4d3f : 00000000`00000000 00000000`00000002 fffffa80`039fb200 fffff880`09900b01 : nt!ObReferenceObjectByHandleWithTag+0xb3
fffff880`09900b90 fffff800`02ac8153 : fffffa80`0660bb60 00000000`00000000 00000000`00000000 fffffa80`03fba510 : nt!NtClearEvent+0x3f
fffff880`09900be0 00000000`74412dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05dcebe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74412dd9

STACK_COMMAND: kb

FOLLOWUP_IP:
MRVW24C+673f
fffff880`0344673f 4c8b4a76 mov r9,qword ptr [rdx+76h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: MRVW24C+673f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MRVW24C

IMAGE_NAME: MRVW24C.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 472551f7

FAILURE_BUCKET_ID: X64_0xD1_MRVW24C+673f

BUCKET_ID: X64_0xD1_MRVW24C+673f

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

Tawnos · Dec 25, 2009

Have you tried the new driver yet? If not, stop posting these, as they are useless.

NathanP2007 · Dec 29, 2009

Now Utorrent is the thing crashing my computer along with the wifi driver which i plan to install the driver one of you guys gave me. How is it a normal computer , with windows 7 fully cleanly installed , with normal programs installed on it, is having SO many driver issues?

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 00000000000e000c, Memory contents of the pool block
Arg4: fffffa800416a3a0, Address of the block of pool being deallocated

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

*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

POOL_ADDRESS: fffffa800416a3a0 Nonpaged pool

FREED_POOL_TAG: OSNB

BUGCHECK_STR: 0xc2_7_OSNB

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: uTorrent.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002bed60e to fffff80002abbf00

STACK_TEXT:
fffff880`0978bf08 fffff800`02bed60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`000e000c : nt!KeBugCheckEx
fffff880`0978bf10 fffff880`014a33cb : fffffa80`06338010 fffff800`02ac1dda fffffa80`05c1b080 00000000`00000000 : nt!ExFreePool+0xccb
fffff880`0978bfc0 fffff880`043ac04e : 00000000`00000000 fffffa80`0416a3c0 fffffa80`0723b8e0 00000000`00000002 : ndis!NdisFreeNetBuffer+0xfb
fffff880`0978bff0 fffff880`06a375bb : fffffa80`05be4030 fffffa80`0635e020 00000000`00000000 fffffa80`04423be0 : MRVW24C+0x104e
fffff880`0978c020 fffff880`06a39643 : fffffa80`05be4030 fffffa80`05be4030 fffffa80`05099800 00000000`00000000 : nwifi!WPP_SF_dll+0x3ab
fffff880`0978c060 fffff880`01527484 : fffffa80`05bd11a0 00000000`00000000 00000000`00000000 fffffa80`0476f530 : nwifi!MP6ReturnNBL+0x4b
fffff880`0978c090 fffff880`0155d17b : fffffa80`06366bb0 fffffa80`05bd11a0 00000000`00000000 00000000`00000000 : ndis!ndisReturnNetBufferListsInternal+0x94
fffff880`0978c0d0 fffff880`01674ff5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : ndis!NdisReturnNetBufferLists+0x3b
fffff880`0978c110 fffff880`015956a6 : fffffa80`05be4030 fffffa80`04f93480 00000000`00000000 fffffa80`05be4030 : tcpip!FlpReturnNetBufferListChain+0x95
fffff880`0978c160 fffff880`0143225a : fffffa80`05be4030 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferList+0x86
fffff880`0978c190 fffff880`03b9385f : fffffa80`05be4030 00000000`00000000 fffffa80`05be4030 fffff880`06a37630 : fwpkclnt!FwpsDereferenceNetBufferList0+0xaa
fffff880`0978c1e0 fffff880`03b9391e : fffffa80`052a5cc0 00000000`00000000 00000000`00000000 fffffa80`0564a9c0 : tunnel!TunnelUserRestoreAndFreeNblAndNbState+0x67
fffff880`0978c230 fffff880`01527484 : fffffa80`05bd11a0 00000000`00000000 00000000`00000000 fffffa80`047aecf0 : tunnel!TunnelUserReturnNetBufferLists+0x26
fffff880`0978c270 fffff880`0155d17b : fffffa80`052a44f0 fffffa80`049f61a0 00000000`00000000 fffffa80`047a3c20 : ndis!ndisReturnNetBufferListsInternal+0x94
fffff880`0978c2b0 fffff880`01674ff5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisReturnNetBufferLists+0x3b
fffff880`0978c2f0 fffff880`01593173 : 00000000`ffffffff 00000000`00000001 00000000`00000001 fffff800`02acb64a : tcpip!FlpReturnNetBufferListChain+0x95
fffff880`0978c340 fffff880`0166ed41 : fffffa80`04f93480 fffffa80`03ef3000 fffff880`0978c3e0 fffff880`0978c4f0 : NETIO!NetioDereferenceNetBufferListChain+0xf3
fffff880`0978c3c0 fffff880`02d0060d : 00000000`ffffffff fffffa80`04f93480 fffff880`0978cc60 fffffa80`041ca510 : tcpip!TcpReleaseIndicationList+0x81
fffff880`0978c3f0 fffff880`02d41995 : fffffa80`05c02cb0 fffffa80`041ca510 00000000`ffffffff 00000000`00000000 : afd!AfdTLReleaseIndications+0x2d
fffff880`0978c440 fffff880`02d2a051 : 00000000`00000010 00000000`00000001 00000000`00000000 fffffa80`0650b8a0 : afd!AfdFastConnectionReceive+0xb65
fffff880`0978c660 fffff800`02dd4113 : 00000000`00005898 fffffa80`041d59e0 00000000`0289fe0c 00000000`00000101 : afd!AfdFastIoDeviceControl+0x1041
fffff880`0978c9d0 fffff800`02dd4c06 : 00000000`00000218 00000000`00000314 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`0978cb00 fffff800`02abb153 : 00000000`00000000 fffff800`02dd5dfc fffff880`0978cc60 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`0978cb70 00000000`73bb2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`004ff0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73bb2dd9

STACK_COMMAND: kb

FOLLOWUP_IP:
MRVW24C+104e
fffff880`043ac04e 488b1e mov rbx,qword ptr [rsi]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: MRVW24C+104e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MRVW24C

IMAGE_NAME: MRVW24C.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 472551f7

FAILURE_BUCKET_ID: X64_0xc2_7_OSNB_MRVW24C+104e

BUCKET_ID: X64_0xc2_7_OSNB_MRVW24C+104e

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

Tawnos · Dec 29, 2009

No, it's not utorrent, it's still the same wifi driver faulting the system.

Your system is not having SO many issues, it's having one driver issue, over, and over, and over. You've just been too stubborn to listen to the advice given to you.

NathanP2007 · Dec 30, 2009

Id hold back on the judgments, Im not being stubborn, i just haven't gotten around to making a restore point on my PC then installing the wifi driver. Which i have to do , cause last time i installed the "update" to my Ethernet driver which showed up in the windows update window, it made my Ethernet port not work at all, so i had to use System Restore to restore to a point before i installed the new driver.

Tawnos · Dec 30, 2009

You don't need a restore point. simply install the driver I linked you to on the first of the month. If it doesn't work, go to device manager and roll back the driver.

NathanP2007 · Jan 1, 2010

I downloaded the Marvell link and there isnt anything to click on to start installing it.

blue screen twice

[H]ard|Gawd

Limp Gawd

[H]ard|Gawd

[H]ard|Gawd

[H]F Junkie

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

[H]ard|Gawd

2[H]4U

2[H]4U

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

2[H]4U

[H]ard|Gawd

2[H]4U

[H]ard|Gawd