Problem With the driver

ghmd86 · Sep 28, 2010

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: 00000020, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f36f173a, address which referenced memory

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

READ_ADDRESS: 00000020

CURRENT_IRQL: 2

FAULTING_IP:
afd!AfdCheckAndReferenceConnection+c
f36f173a 8b0a mov ecx,dword ptr [edx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f36fee3b to f36f173a

STACK_TEXT:
f7aa791c f36fee3b 00000000 00000e20 f7aa7a94 afd!AfdCheckAndReferenceConnection+0xc
f7aa7960 f38576c7 86876598 00000000 00000e20 afd!AfdBReceiveEventHandler+0x25
WARNING: Stack unwind information not available. Following frames may be wrong.
f7aa7994 f3857573 85a33848 f7aa79cc 00000000 SYMTDI+0xc6c7
f7aa79d4 f6eaf5e2 85699f90 00000000 00000e20 SYMTDI+0xc573
f7aa7a34 f388b34b 852851d0 00000000 00000e20 kl1+0x3c5e2
f7aa7a78 f3888730 00000014 f6eaf640 852851d0 tcpip!IndicateData+0x225
f7aa7a98 f38883e5 00000000 00001850 86ff3430 tcpip!FindTCB+0xe7
f7aa7b20 f3885ef5 867d70e0 0100007f 0100007f tcpip!TCPRcv+0xbb0
f7aa7b80 f3885b19 00000020 867d70e0 f38880b6 tcpip!DeliverToUser+0x18e
f7aa7bfc f3885836 f38c58f0 867d70e0 f7aa7d18 tcpip!DeliverToUserEx+0x95e
f7aa7cb4 f3891ce6 867d70e0 f7aa7d2c 00000020 tcpip!IPRcvPacket+0x6cb
f7aa7d60 f78dc3e4 f38c5680 867d70e0 f38c5690 tcpip!LoopXmitRtn+0x195
f7aa7d7c 8053879d 867d70e0 00000000 871c23c8 TDI!CTEpEventHandler+0x32
f7aa7dac 805cff62 f38c5680 00000000 00000000 nt!ExpWorkerThread+0xef
f7aa7ddc 8054612e 805386ae 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
SYMTDI+c6c7
f38576c7 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: SYMTDI+c6c7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SYMTDI

IMAGE_NAME: SYMTDI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 470168eb

FAILURE_BUCKET_ID: 0xD1_SYMTDI+c6c7

BUCKET_ID: 0xD1_SYMTDI+c6c7

ghmd86 · Sep 28, 2010

Please help me with this error, really bugging me for over a month

ghmd86 · Sep 28, 2010

Unable to load image SYMTDI.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
Probably caused by : SYMTDI.SYS ( SYMTDI+2bf1 )

ghmd86 · Sep 28, 2010

these are the minidumps

Caliban · Sep 28, 2010

Greetings, ghmd86.

Need to know your operating system and service pack #, make and model # of your machine, and a good description of your symptoms.

DavidGP · Sep 28, 2010

Hi

Before this started to happen did you install any new software or updated a driver etc if so what?

The file that is faulting is from your Symantec security software, so do you have Symantec or Norton security application installed? if so or you have just removed it follow the below.

What you need to do if you have removed Norton to use another Antivirus or security application (do note you can get issues like this if you have two or more antivirus or security suites installed at once, so choose one and uninstall the rest) is to use the Norton Removal Tool HERE to remove any left over components and Reboot.

Then uninstall any other security application you have installed, then reboot and run CCleaner and its cleaner and then the registry tool and run the registry one until nothing shows for removal, after this does your PC work ok.

If not boot into Safe Mode (F8 at boot) does your PC work fine now with no BSOD messages?

If you only have Symantec/Norton installed then do the above anyways as we need to remove Norton fully and then reinstall to troubleshoot) and once done reboot your PC and does it work ok? if so then reinstall your Version of Norton (as mentioned its a good thing to know what version you have of Windows and Norton as well so we can see if your version has issues with your particular Windows version).

ghmd86 · Sep 29, 2010

Thanks it was indeed Symantec security software problem. the Norton remove tool did the trick and solved the problem . Till now system didn't gave any problem.

Halo said: ↑

Hi

Before this started to happen did you install any new software or updated a driver etc if so what?

The file that is faulting is from your Symantec security software, so do you have Symantec or Norton security application installed? if so or you have just removed it follow the below.

What you need to do if you have removed Norton to use another Antivirus or security application (do note you can get issues like this if you have two or more antivirus or security suites installed at once, so choose one and uninstall the rest) is to use the Norton Removal Tool HERE to remove any left over components and Reboot.

Then uninstall any other security application you have installed, then reboot and run CCleaner and its cleaner and then the registry tool and run the registry one until nothing shows for removal, after this does your PC work ok.

If not boot into Safe Mode (F8 at boot) does your PC work fine now with no BSOD messages?

If you only have Symantec/Norton installed then do the above anyways as we need to remove Norton fully and then reinstall to troubleshoot) and once done reboot your PC and does it work ok? if so then reinstall your Version of Norton (as mentioned its a good thing to know what version you have of Windows and Norton as well so we can see if your version has issues with your particular Windows version).
Click to expand...

Caliban · Sep 29, 2010

Glad you got it - Halo knows his stuff. :major

ghmd86 · Sep 29, 2010

hush that was really headache actually the laptop belongs to my boss ............thanks to halo for his great help. But I wonder why such a big firm like Symantec will try to build such a irritating software

DavidGP · Sep 29, 2010

Hi

Glad the issue was just Norton/Symantec one and the advice helped and cheers for letting us know that the suggestion fixed the issue.

Symantec/norton dont make too bad a software package these days, yeah some think its a little fat around the middle and resource hungry but its a fair security application, some others are better and some worse.

Odd times are that a 3rd party application or running some over eager cleanup utilities and/or a bad update can corrupt any software package and its possible this is what happened.

ghmd86 · Sep 30, 2010

I may arise due to corrupt update or incomplete uninstallation

Log in or Sign up

Problem With the driver

ghmd86 Private E-2

ghmd86 Private E-2

ghmd86 Private E-2

ghmd86 Private E-2

Attached Files:

Mini092710-01.txt

Mini092710-02.txt

Mini092710-03.txt

Mini092810-01.txt

Caliban I don't need no steenkin' title!

DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

ghmd86 Private E-2

Caliban I don't need no steenkin' title!

ghmd86 Private E-2

DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

ghmd86 Private E-2