BSOD Error BCCode d1

[stevejma]

Well my computer blue screened again. I've attached the dump reports. I don't know why it's still doing this; is it really still my wireless USB adapter? If it still is then I'll invest in a PCI wireless adapter instead.

Sorry I forgot to copy and paste the error report when Windows started.

Here's my specs:

i5-2500K Sandy Bridge stock @ 3.3GHz
16GB (4GBx4) DDR3 1600MHz Corsair Vengeance
NVIDIA GeForce GTX 570 HD 2.5GB [EDIT: the card is an EVGA branded card]
GigaByte GA-Z68MA
850W Corsair CMPSU-850TXV2
2TB (2TBx1) SATA-III 6.0Gb/s 64MB Cache 7200RPM HDD

 

[stevejma]

Ahh sorry I submitted the thread before I attached the .RAR files. Here you go.

 

[writhziden]

Loading Dump File [F:\BSODDmpFiles\stevejma\Windows_NT6_BSOD_jcgriff2\012412-18813-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`0328f670
Debug session time: Tue Jan 24 20:01:20.632 2012 (GMT-7)
System Uptime: 0 days 0:28:27.491
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {7fc4, 2, 0, fffff880016d2d67}

Probably caused by : nwifi.sys ( nwifi!Pt6Receive+296 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000007fc4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016d2d67, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f9100
 0000000000007fc4 

CURRENT_IRQL:  0

FAULTING_IP: 
tcpip!IppProcessDeliverList+87
fffff880`016d2d67 488b3e          mov     rdi,qword ptr [rsi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  	ÛÌ

TRAP_FRAME:  fffff8800318b590 -- (.trap 0xfffff8800318b590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800d383e40 rbx=0000000000000000 rcx=f880017ec1b40000
rdx=fffff880017ec128 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016d2d67 rsp=fffff8800318b720 rbp=fffff880017f29a0
 r8=fffff880017ed800  r9=fffff880017f29a0 r10=0000000000000010
r11=fffffa800d060850 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!IppProcessDeliverList+0x87:
fffff880`016d2d67 488b3e          mov     rdi,qword ptr [rsi] ds:cdc0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c61e9 to fffff800030c6c40

STACK_TEXT:  
fffff880`0318b448 fffff800`030c61e9 : 00000000`0000000a 00000000`00007fc4 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318b450 fffff800`030c4e60 : fffffa80`1068806c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0318b590 fffff880`016d2d67 : 00000000`00000000 fffff880`017f29a0 fffff880`0318b820 fffffa80`0c7e6b60 : nt!KiPageFault+0x260
fffff880`0318b720 fffff880`016d2339 : fffff6fb`7ea00350 fffffa80`00000001 00000000`00000000 fffff880`0318b810 : tcpip!IppProcessDeliverList+0x87
fffff880`0318b7c0 fffff880`016d00af : fffff880`0318b8b0 fffffa80`0d738000 fffff880`017f29a0 00000000`106f2701 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`0318b8a0 fffff880`016cf6a2 : fffffa80`106c6c10 00000000`00000000 fffffa80`106f2701 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`0318baa0 fffff880`016ceb3a : fffffa80`106f2790 fffff880`0318bbd0 fffffa80`106f2790 fffffa80`0ff10000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`0318bb80 fffff800`030d3618 : fffffa80`0ccfb450 00000000`00004800 fffffa80`0c7e6b60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`0318bbd0 fffff880`016cf202 : fffff880`016cea60 fffff880`06b0f8ce 0000004a`0f1e8002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0318bcb0 fffff880`015a90eb : fffffa80`0fe46010 00000000`00000000 fffffa80`0ff9c1a0 fffffa80`0ff9c1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`0318bd20 fffff880`01572ad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`0318bd90 fffff880`014f49c4 : fffffa80`0ff9c1a0 00000000`00000002 00000000`00000001 fffffa80`0ccfb450 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`0318c210 fffff880`014f4939 : 00000000`00000000 00000000`00000000 fffffa80`106f5810 00000000`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff880`0318c250 fffff880`014f48d0 : fffff880`07c825c0 fffffa80`1070c010 fffffa80`106f5810 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`0318c290 fffff880`07c4b7ee : fffffa80`1070c010 00000000`00000000 fffffa80`0ccfb450 fffff880`07c825c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`0318c2d0 fffff880`014f4939 : fffffa80`0ec7d790 00000000`00000000 00000000`00000001 00000000`00000001 : nwifi!Pt6Receive+0x296
fffff880`0318c330 fffff880`014f48d0 : fffffa80`106c2028 fffff880`0694c0c7 fffff880`0694d340 fffff880`02836057 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`0318c370 fffff880`069489c0 : fffff880`0694f110 00000000`00000000 00000000`00000001 fffffa80`106c2a78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`0318c3b0 fffff880`0150d4f7 : fffffa80`0ff9c1a0 fffffa80`0d1e43f0 fffffa80`0d1e43f0 00000000`00000001 : vwififlt!FilterReceiveNetBufferLists+0x158
fffff880`0318c410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xcf1f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6Receive+296
fffff880`07c4b7ee 83a3e010000000  and     dword ptr [rbx+10E0h],0

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  nwifi!Pt6Receive+296

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0xD1_nwifi!Pt6Receive+296

BUCKET_ID:  X64_0xD1_nwifi!Pt6Receive+296

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

This crash is usually caused by a driver. Recommend starting by updating your NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter driver. Use http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html as a reference for how to find your driver. If you need further help, let us know.



After you update your wireless driver, if you continue to have problems, an underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.