iDowngrade
New Member
- Messages
- 3
So I am having this problem, which is I get a BSOD, as specified in the debugging analization, is caused by uTorrent.
Error is driver_irql_not_less_or_equal (tcpip.sys).
I have already tried updating my Network's Drivers.
The the dump analyzation(debug check) is:
As you can see, it is caused by uTorrent, and as far as I've checked, only happens when uTorrent is doing work.
I really hope you guys can help me with this problem.
System Specs:
Toshiba Satellite l305-5944
Windows 8 32-Bit x86
NOTE: It also happened with Vuze back then, another BitTorrent program.
UPDATE: So I was checking through the internet, just because I'm desperate, I managed to fix the failed symbol problem, here's the new debug report:
Error is driver_irql_not_less_or_equal (tcpip.sys).
I have already tried updating my Network's Drivers.
The the dump analyzation(debug check) is:
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060214-19453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9200 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16384.x86fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0x81860000 PsLoadedModuleList = 0x81a4ade8
Debug session time: Mon Jun 2 16:45:53.570 2014 (UTC - 4:00)
System Uptime: 0 days 0:06:16.389
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {130, 2, 1, 82b390f5}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : tcpip.sys ( tcpip+1170f5 )
Followup: MachineOwner
---------
0: 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: 00000130, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82b390f5, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: tcpip
FAULTING_MODULE: 81860000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ac75
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000130
CURRENT_IRQL: 0
FAULTING_IP:
tcpip+1170f5
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from 819ce840 to 81957ccc
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b35970c4 819ce840 0000000a 00000130 00000002 nt+0xf7ccc
b35970e4 82b390f5 badb0d00 b359720c 00000000 nt+0x16e840
b3597234 82a93301 00000011 00000002 0000bc5d tcpip+0x1170f5
b359739c 82a93b96 00000000 00000011 85025368 tcpip+0x71301
b359745c 82a9af70 00000004 82b63fc8 85025368 tcpip+0x71b96
b3597478 82a9ba55 85858c10 b3597538 00000000 tcpip+0x78f70
b35976e8 82a9bf04 00000000 00000000 850c3b30 tcpip+0x79a55
b35978d8 82a9c22a 8513fd40 b359795c 81910370 tcpip+0x79f04
b35978e4 81910370 b35979a4 cdfdcfa9 00000000 tcpip+0x7a22a
b359795c 8190ffcf 82a9c217 b35979a4 00002400 nt+0xb0370
b359797c 82a9b3fb 82a9c217 b35979a4 00002400 nt+0xaffcf
b35979c0 8d85dc8c 850c3b30 b35979d8 85137008 tcpip+0x793fb
b3597a14 8d85d952 85137008 7c0d668e 7fff0000 afd+0x2cc8c
b3597ac8 8d84c573 00012001 8d84c573 b3597b90 afd+0x2c952
b3597c40 81aa87b2 85137008 00000001 0270f9e8 afd+0x1b573
b3597cf0 81aa85c9 85c17b40 0000046c 00000000 nt+0x2487b2
b3597d24 819cb2fc 00000454 0000046c 00000000 nt+0x2485c9
b3597d54 772f6954 badb0d00 0270f9b0 02000000 nt+0x16b2fc
b3597d58 badb0d00 0270f9b0 02000000 00000000 0x772f6954
b3597d5c 0270f9b0 02000000 00000000 00000000 0xbadb0d00
b3597d60 02000000 00000000 00000000 00000000 0x270f9b0
b3597d64 00000000 00000000 00000000 00000000 0x2000000
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip+1170f5
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tcpip+1170f5
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tcpip.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> .symfix
0: kd> lmvm nt
start end module name
81860000 81dee000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Jul 25 22:39:44 2012 (5010ADF0)
CheckSum: 00550165
ImageSize: 0058E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
As you can see, it is caused by uTorrent, and as far as I've checked, only happens when uTorrent is doing work.
I really hope you guys can help me with this problem.
System Specs:
Toshiba Satellite l305-5944
Windows 8 32-Bit x86
NOTE: It also happened with Vuze back then, another BitTorrent program.
UPDATE: So I was checking through the internet, just because I'm desperate, I managed to fix the failed symbol problem, here's the new debug report:
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060214-19453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;srv*
Executable search path is: srv*
Windows 8 Kernel Version 9200 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16384.x86fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0x81860000 PsLoadedModuleList = 0x81a4ade8
Debug session time: Mon Jun 2 16:45:53.570 2014 (UTC - 4:00)
System Uptime: 0 days 0:06:16.389
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {130, 2, 1, 82b390f5}
Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+20962 )
Followup: MachineOwner
---------
0: 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: 00000130, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82b390f5, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81a74470
Unable to read MiSystemVaType memory at 81a4a000
00000130
CURRENT_IRQL: 2
FAULTING_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: 3.4.1_31395.ex
TRAP_FRAME: b35970e4 -- (.trap 0xffffffffb35970e4)
ErrCode = 00000002
eax=00000130 ebx=851aa738 ecx=00000001 edx=b359720c esi=00000010 edi=8627ad48
eip=82b390f5 esp=b3597158 ebp=b3597234 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
tcpip! ?? ::FNODOBFM::`string'+0x20962:
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx ds:0023:00000130=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 819ce840 to 81957ccc
STACK_TEXT:
b35970c4 819ce840 0000000a 00000130 00000002 nt!KiBugCheck2
b35970c4 82b390f5 0000000a 00000130 00000002 nt!KiTrap0E+0x2c8
b3597234 82a93301 00000011 00000002 0000bc5d tcpip! ?? ::FNODOBFM::`string'+0x20962
b359739c 82a93b96 00000000 00000011 85025368 tcpip!IppInspectLocalDatagramsOut+0x658
b359745c 82a9af70 00000004 82b63fc8 85025368 tcpip!IppSendDatagramsCommon+0x39c
b3597478 82a9ba55 85858c10 b3597538 00000000 tcpip!IpNlpSendDatagrams+0x42
b35976e8 82a9bf04 00000000 00000000 850c3b30 tcpip!UdpSendMessagesOnPathCreation+0x4d4
b35978d8 82a9c22a 8513fd40 b359795c 81910370 tcpip!UdpSendMessages+0x1cd
b35978e4 81910370 b35979a4 cdfdcfa9 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13
b359795c 8190ffcf 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutInternal+0x38b
b359797c 82a9b3fb 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1f
b35979c0 8d85dc8c 850c3b30 b35979d8 85137008 tcpip!UdpTlProviderSendMessages+0x55
b3597a14 8d85d952 85137008 7c0d668e 7fff0000 afd!AfdTLFastDgramSend+0xc6
b3597ad0 8d84c573 b3597b90 00000000 00000000 afd!AfdFastDatagramSend+0x1fd
b3597c40 81aa87b2 85137008 00000001 0270f9e8 afd!AfdFastIoDeviceControl+0x56e
b3597cf0 81aa85c9 85c17b40 0000046c 00000000 nt!IopXxxControlFile+0x1cd
b3597d24 819cb2fc 00000454 0000046c 00000000 nt!NtDeviceIoControlFile+0x2a
b3597d24 772f6954 00000454 0000046c 00000000 nt!KiFastCallEntry+0x12c
WARNING: Frame IP not in any known module. Following frames may be wrong.
0270fab0 00000000 00000000 00000000 00000000 0x772f6954
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tcpip! ?? ::FNODOBFM::`string'+20962
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ac75
BUCKET_ID_FUNC_OFFSET: 20962
FAILURE_BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
Followup: MachineOwner
---------
0: 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: 00000130, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82b390f5, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81a74470
Unable to read MiSystemVaType memory at 81a4a000
00000130
CURRENT_IRQL: 2
FAULTING_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: 3.4.1_31395.ex
TRAP_FRAME: b35970e4 -- (.trap 0xffffffffb35970e4)
ErrCode = 00000002
eax=00000130 ebx=851aa738 ecx=00000001 edx=b359720c esi=00000010 edi=8627ad48
eip=82b390f5 esp=b3597158 ebp=b3597234 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
tcpip! ?? ::FNODOBFM::`string'+0x20962:
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx ds:0023:00000130=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 819ce840 to 81957ccc
STACK_TEXT:
b35970c4 819ce840 0000000a 00000130 00000002 nt!KiBugCheck2
b35970c4 82b390f5 0000000a 00000130 00000002 nt!KiTrap0E+0x2c8
b3597234 82a93301 00000011 00000002 0000bc5d tcpip! ?? ::FNODOBFM::`string'+0x20962
b359739c 82a93b96 00000000 00000011 85025368 tcpip!IppInspectLocalDatagramsOut+0x658
b359745c 82a9af70 00000004 82b63fc8 85025368 tcpip!IppSendDatagramsCommon+0x39c
b3597478 82a9ba55 85858c10 b3597538 00000000 tcpip!IpNlpSendDatagrams+0x42
b35976e8 82a9bf04 00000000 00000000 850c3b30 tcpip!UdpSendMessagesOnPathCreation+0x4d4
b35978d8 82a9c22a 8513fd40 b359795c 81910370 tcpip!UdpSendMessages+0x1cd
b35978e4 81910370 b35979a4 cdfdcfa9 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13
b359795c 8190ffcf 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutInternal+0x38b
b359797c 82a9b3fb 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1f
b35979c0 8d85dc8c 850c3b30 b35979d8 85137008 tcpip!UdpTlProviderSendMessages+0x55
b3597a14 8d85d952 85137008 7c0d668e 7fff0000 afd!AfdTLFastDgramSend+0xc6
b3597ad0 8d84c573 b3597b90 00000000 00000000 afd!AfdFastDatagramSend+0x1fd
b3597c40 81aa87b2 85137008 00000001 0270f9e8 afd!AfdFastIoDeviceControl+0x56e
b3597cf0 81aa85c9 85c17b40 0000046c 00000000 nt!IopXxxControlFile+0x1cd
b3597d24 819cb2fc 00000454 0000046c 00000000 nt!NtDeviceIoControlFile+0x2a
b3597d24 772f6954 00000454 0000046c 00000000 nt!KiFastCallEntry+0x12c
WARNING: Frame IP not in any known module. Following frames may be wrong.
0270fab0 00000000 00000000 00000000 00000000 0x772f6954
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tcpip! ?? ::FNODOBFM::`string'+20962
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ac75
BUCKET_ID_FUNC_OFFSET: 20962
FAILURE_BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
Followup: MachineOwner
---------
0: 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: 00000130, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82b390f5, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81a74470
Unable to read MiSystemVaType memory at 81a4a000
00000130
CURRENT_IRQL: 2
FAULTING_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: 3.4.1_31395.ex
TRAP_FRAME: b35970e4 -- (.trap 0xffffffffb35970e4)
ErrCode = 00000002
eax=00000130 ebx=851aa738 ecx=00000001 edx=b359720c esi=00000010 edi=8627ad48
eip=82b390f5 esp=b3597158 ebp=b3597234 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
tcpip! ?? ::FNODOBFM::`string'+0x20962:
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx ds:0023:00000130=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 819ce840 to 81957ccc
STACK_TEXT:
b35970c4 819ce840 0000000a 00000130 00000002 nt!KiBugCheck2
b35970c4 82b390f5 0000000a 00000130 00000002 nt!KiTrap0E+0x2c8
b3597234 82a93301 00000011 00000002 0000bc5d tcpip! ?? ::FNODOBFM::`string'+0x20962
b359739c 82a93b96 00000000 00000011 85025368 tcpip!IppInspectLocalDatagramsOut+0x658
b359745c 82a9af70 00000004 82b63fc8 85025368 tcpip!IppSendDatagramsCommon+0x39c
b3597478 82a9ba55 85858c10 b3597538 00000000 tcpip!IpNlpSendDatagrams+0x42
b35976e8 82a9bf04 00000000 00000000 850c3b30 tcpip!UdpSendMessagesOnPathCreation+0x4d4
b35978d8 82a9c22a 8513fd40 b359795c 81910370 tcpip!UdpSendMessages+0x1cd
b35978e4 81910370 b35979a4 cdfdcfa9 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13
b359795c 8190ffcf 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutInternal+0x38b
b359797c 82a9b3fb 82a9c217 b35979a4 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1f
b35979c0 8d85dc8c 850c3b30 b35979d8 85137008 tcpip!UdpTlProviderSendMessages+0x55
b3597a14 8d85d952 85137008 7c0d668e 7fff0000 afd!AfdTLFastDgramSend+0xc6
b3597ad0 8d84c573 b3597b90 00000000 00000000 afd!AfdFastDatagramSend+0x1fd
b3597c40 81aa87b2 85137008 00000001 0270f9e8 afd!AfdFastIoDeviceControl+0x56e
b3597cf0 81aa85c9 85c17b40 0000046c 00000000 nt!IopXxxControlFile+0x1cd
b3597d24 819cb2fc 00000454 0000046c 00000000 nt!NtDeviceIoControlFile+0x2a
b3597d24 772f6954 00000454 0000046c 00000000 nt!KiFastCallEntry+0x12c
WARNING: Frame IP not in any known module. Following frames may be wrong.
0270fab0 00000000 00000000 00000000 00000000 0x772f6954
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip! ?? ::FNODOBFM::`string'+20962
82b390f5 f00fc108 lock xadd dword ptr [eax],ecx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tcpip! ?? ::FNODOBFM::`string'+20962
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ac75
BUCKET_ID_FUNC_OFFSET: 20962
FAILURE_BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
BUCKET_ID: AV_tcpip!_??_::FNODOBFM::_string_
Followup: MachineOwner
---------
Last edited:
My Computer
System One
-
- OS
- Windows 8 32-Bit
- Computer type
- Laptop
- System Manufacturer/Model
- Toshiba Satellite l305-5944
- Graphics Card(s)
- Mobile Intel(R) 4 Series Express Chipset Family v2
- Sound Card
- Integrated Speakers (High Definition Audio Device)
- Monitor(s) Displays
- Integrated Monitor
- Screen Resolution
- 1280x800
- Hard Drives
- Integrated 231.5 GB Hard Drive
- Cooling
- Integrated Fan/External Cooler Master
- Keyboard
- Integrated Keyboard
- Mouse
- Microsoft Wireless Mobile Mouse 3000
- Internet Speed
- 4~5 Megabits (not sure)
- Browser
- Google Chrome
- Antivirus
- Malware Bytes