BSOD it's a Turkey for Thanksgiving

catsnoutsoup · 27 Nov 2013

Hi folks, I am hoping someone can have a look at my attached zip file concerning a BSOD.

I built this computer over a year ago and have never had an issue. Until the last week when I had two BSOD events.

I looked at the dump files using MS debug but I am no expert and do not really understand them. With some research I think it may have been pointing to my Intel PCI-E Wi-Fi card -- but I am not sure.

I did find that there were newer drivers for the Wi-Fi card, and I have updated them (after the events).

Could someone have a look at the files and tell me if I am on the right track.

Thanks very much.

Arc · 28 Nov 2013

Hi catsnoutsoup.

Update Intel® PROSet/Wireless Software and Drivers for Windows 7 which is for your Intel® Centrino® Wireless-N 2200.

Let us know the results.
_____________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {74, 2, 1, fffff880066c1edc}

*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+9eedc )

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

1: 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: 0000000000000074, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880066c1edc, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800028fd100
GetUlongFromAddress: unable to read from fffff800028fd1c0
 0000000000000074 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
Netwsw00+9eedc
fffff880`066c1edc ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800cce34f0 -- (.trap 0xfffff8800cce34f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008d9e9c0
rdx=fffffa8008d9e820 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880066c1edc rsp=fffff8800cce3680 rbp=0000000000000000
 r8=fffff8800cce3748  r9=0000000000000000 r10=fffff880070e3a80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Netwsw00+0x9eedc:
fffff880`066c1edc ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800026c5169 to fffff800026c5bc0

STACK_TEXT:  
fffff880`0cce33a8 fffff800`026c5169 : 00000000`0000000a 00000000`00000074 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0cce33b0 fffff800`026c3de0 : 00000000`00000000 00000000`00000000 fffffa80`07780080 fffffa80`08d067a0 : nt!KiBugCheckDispatch+0x69
fffff880`0cce34f0 fffff880`066c1edc : fffffa80`07780080 fffffa80`07552fc8 fffffa80`07780080 fffffa80`08b1c550 : nt!KiPageFault+0x260
fffff880`0cce3680 fffffa80`07780080 : fffffa80`07552fc8 fffffa80`07780080 fffffa80`08b1c550 00000000`00000006 : Netwsw00+0x9eedc
fffff880`0cce3688 fffffa80`07552fc8 : fffffa80`07780080 fffffa80`08b1c550 00000000`00000006 00000000`000000d2 : 0xfffffa80`07780080
fffff880`0cce3690 fffffa80`07780080 : fffffa80`08b1c550 00000000`00000006 00000000`000000d2 00000000`00000000 : 0xfffffa80`07552fc8
fffff880`0cce3698 fffffa80`08b1c550 : 00000000`00000006 00000000`000000d2 00000000`00000000 fffff880`06638d40 : 0xfffffa80`07780080
fffff880`0cce36a0 00000000`00000006 : 00000000`000000d2 00000000`00000000 fffff880`06638d40 00000000`00000030 : 0xfffffa80`08b1c550
fffff880`0cce36a8 00000000`000000d2 : 00000000`00000000 fffff880`06638d40 00000000`00000030 ffff0000`0a660697 : 0x6
fffff880`0cce36b0 00000000`00000000 : fffff880`06638d40 00000000`00000030 ffff0000`0a660697 00000000`00000006 : 0xd2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Netwsw00+9eedc
fffff880`066c1edc ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Netwsw00+9eedc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Netwsw00

IMAGE_NAME:  Netwsw00.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f42904f

FAILURE_BUCKET_ID:  X64_0xD1_Netwsw00+9eedc

BUCKET_ID:  X64_0xD1_Netwsw00+9eedc

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

1: kd> lmvm Netwsw00
start             end                 module name
fffff880`06623000 fffff880`07167000   Netwsw00 T (no symbols)           
    Loaded symbol image file: Netwsw00.sys
    Image path: Netwsw00.sys
    Image name: Netwsw00.sys
    Timestamp:        Mon Feb 20 23:56:23 2012 (4F42904F)
    CheckSum:         00AF64AA
    ImageSize:        00B44000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

catsnoutsoup · 28 Nov 2013

Thank you, good to know I was on the right track. I will return to this thread if I have any further events.

Once again, thank you very much for your time.