BSOD when connecting via wireless, logs attached

[ellessone]

Hello all, first post, looking for assistance on ntoskrnl.exe

Windows 7 Pro 64 bit SP1 on Thinkpad X220. I've attached the requested zip file and also my screenshot from Blue Screen Viewer.

Any help is greatly appreciated.

This only seems to occur, on battery, right away when the laptop is trying to connect to a familiar wireless network.

Thanks in advance

 

[Capt.Jack Sparrow]

Hello all, first post, looking for assistance on ntoskrnl.exe

Windows 7 Pro 64 bit SP1 on Thinkpad X220. I've attached the requested zip file and also my screenshot from Blue Screen Viewer.

Any help is greatly appreciated.

This only seems to occur, on battery, right away when the laptop is trying to connect to a familiar wireless network.

Thanks in advance

Hello there!

Seems like multiple things are going on. Download a update version of Network drivers and Remove you Network drivers and install the new one. If your Overclocking please stop. Reset the BIOS to default settings.

Run Hardware Diagnostic (RAM, GPU and Hard drive) : Hardware Diagnostic | Captain Debugger

Run SFC SCANNOW to make sure all the OS files are intact.

Update the Following Drivers:

TVicPort64.SYS Wed Mar 30 14:42:54 2005 - EnTech Taiwan
psadd.sys      Tue Feb 20 00:26:37 2007  - SMBIOS Driver

How to Update Drivers on Windows 7 | Captain Debugger

Bugcheck:

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: ffffb80001c95888, 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: fffff80001ad0e60, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cff100
 ffffb80001c95888 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+2ce
fffff800`01ad0e60 f0410fba2907    lock bts dword ptr [r9],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800251d840 -- (.trap 0xfffff8800251d840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff80001c95878
rdx=fffff80001c518a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001ad0e60 rsp=fffff8800251d9d0 rbp=0000000000000000
 r8=fffff80001c51690  r9=ffffb80001c95888 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KeSetEvent+0x2ce:
fffff800`01ad0e60 f0410fba2907    lock bts dword ptr [r9],7 ds:0010:ffffb800`01c95888=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001acc1e9 to fffff80001accc40

STACK_TEXT:  
fffff880`0251d6f8 fffff800`01acc1e9 : 00000000`0000000a ffffb800`01c95888 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0251d700 fffff800`01acae60 : 0000129d`00000001 00001f80`00d00080 00000000`000001d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0251d840 fffff800`01ad0e60 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0251d9d0 fffff800`01ab796c : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffff800`01c518a0 : nt!KeSetEvent+0x2ce
fffff880`0251da40 fffff800`01ab7cd3 : 00000000`00000008 fffff880`0251dad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x1b4
fffff880`0251da90 fffff800`01d67fee : fffffa80`066b68e0 00000000`00000080 fffffa80`06673b30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0251dc00 fffff800`01abe5e6 : fffff880`009e5180 fffffa80`066b68e0 fffff880`009effc0 1d4db102`4be54915 : nt!PspSystemThreadStartup+0x5a
fffff880`0251dc40 00000000`00000000 : fffff880`0251e000 fffff880`02518000 fffff880`0251d5c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeSetEvent+2ce
fffff800`01ad0e60 f0410fba2907    lock bts dword ptr [r9],7

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeSetEvent+2ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEvent+2ce

BUCKET_ID:  X64_0xA_nt!KeSetEvent+2ce

Followup: MachineOwner