BSOD error when connecting to wifi

Welcome to SevenForums

Looks like the BSOD was caused by F-Secure Distributed Firewall Driver.

Please uninstall it and see if the issue persists. (Look for its removal tool in Google, or uninstall using Revo Uninstaller [Free] Advanced Mode)

What antivirus are you using BTW?

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• Good and Free system security combination.

Run a full scan with both (separately) once downloaded, installed and updated.

You might also want to look for updates on your graphic card drivers.

Code:

Driver	c:\windows\system32\drivers\atikmpag.sys (8.14.1.6233, 310.50 KB (317,952 bytes), 29/09/2011 02:34)

The following is for information purpose only;

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff88003ad1459}

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100
GetUlongFromAddress: unable to read from fffff80002efa1c0
 0000000000000028 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
fsdfw+d459
fffff880`03ad1459 8b4628          mov     eax,dword ptr [rsi+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  CCC.exe

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f20e00 -- (.trap 0xfffff88002f20e00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000036 rbx=0000000000000000 rcx=0000000000000042
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003ad1459 rsp=fffff88002f20f90 rbp=00000000ffffffea
 r8=0000000000000014  r9=fffff88002f21038 r10=fffff88003ad1950
r11=fffff88002f21008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fsdfw+0xd459:
fffff880`03ad1459 8b4628          mov     eax,dword ptr [rsi+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cca569 to fffff80002ccafc0

STACK_TEXT:  
fffff880`02f20cb8 fffff800`02cca569 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f20cc0 fffff800`02cc91e0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`02f215e0 : nt!KiBugCheckDispatch+0x69
fffff880`02f20e00 fffff880`03ad1459 : 00000000`00000000 fffff880`0162ed11 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f20f90 00000000`00000000 : fffff880`0162ed11 00000000`00000000 00000000`00000000 fffff880`02f216a0 : fsdfw+0xd459


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fsdfw+d459
fffff880`03ad1459 8b4628          mov     eax,dword ptr [rsi+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  fsdfw+d459

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fsdfw

IMAGE_NAME:  fsdfw.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c160ca5

FAILURE_BUCKET_ID:  X64_0xD1_fsdfw+d459

BUCKET_ID:  X64_0xD1_fsdfw+d459

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

1: kd> lmvm fsdfw
start             end                 module name
fffff880`03ac4000 fffff880`03ad9380   fsdfw    T (no symbols)           
    Loaded symbol image file: fsdfw.sys
    Image path: \SystemRoot\System32\drivers\fsdfw.sys
    Image name: fsdfw.sys
    Timestamp:        Mon Jun 14 17:04:05 2010 (4C160CA5)
    CheckSum:         0002374F
    ImageSize:        00015380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Let us know the results and further .dmps

sgc3000000 said:

so would my best option be to uninstall the entire programme using revo?

Yes, or at least to test and if the bugs go away. You can see that fsdfw.sys is on the "probably caused by:" line = Driver Reference Table

Any updates?

• If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner.