MSI P45 Platinum HC Edition
Intel Core 2 Duo E8500
4x2Gb G Skill PC6400
VisionTek HD 3870
Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.
Create Account How it WorksMicrosoft ฎ Windows Debugger Version 6.9.0003.113 AMD64
Copyright ฉ Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\FUBAR\Downloads\Windows_7_Memory_Dump\Windows 7 Memory Dump\091108-34226-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c6c050
Debug session time: Thu Sep 11 05:45:11.486 2008 (GMT-4)
System Uptime: 0 days 0:08:35.373
Loading Kernel Symbols
....................................................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {b8, 2, 0, fffff8800137efc0}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
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: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800137efc0, address which referenced memory
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cd70e0
00000000000000b8
CURRENT_IRQL: 2
FAULTING_IP:
tdx!TdxEventReceiveConnection+300
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff88005707460 -- (.trap 0xfffff88005707460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=fffffa80096ec778 rcx=fffffa800978c390
rdx=0000000000000000 rsi=0000000000000004 rdi=0000000000000004
rip=fffff8800137efc0 rsp=fffff880057075f0 rbp=fffff880057078b8
r8=0000000000000000 r9=fffff88005707630 r10=fffff88003221500
r11=fffff880057075c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
tdx!TdxEventReceiveConnection+0x300:
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h] ds:0002:00000000`000000b8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ab8e69 to fffff80002ab9900
STACK_TEXT:
fffff880`05707318 fffff800`02ab8e69 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05707320 fffff800`02ab7b1d : 00000000`00000000 00000000`000000b8 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05707460 fffff880`0137efc0 : 00000000`c000021b fffffa80`08b00f40 fffffa80`0978c390 00000000`c0000016 : nt!KiPageFault+0x25d
fffff880`057075f0 fffff880`00e894ee : 00000000`00000006 00000000`00000000 00000000`00000000 fffff880`00e54d76 : tdx!TdxEventReceiveConnection+0x300
fffff880`05707730 fffff880`00e84310 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpIndicateData+0xfe
fffff880`05707830 fffff880`00e88545 : 00000000`00000000 fffffa80`097f8890 00000000`00000002 00000000`00000007 : tcpip!TcpDeliverDataToClient+0x370
fffff880`05707990 fffff880`00e84bb7 : fffffa80`071da040 fffff880`05707ca8 fffffa80`07b94520 fffffa80`09a91010 : tcpip!TcpDeliverReceive+0xa5
fffff880`05707a80 fffff880`00e87925 : fffff880`05707c80 fffffa80`00000000 fffffa80`0982d570 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x207
fffff880`05707bd0 fffff880`00e88ef9 : fffffa80`07bd3f00 fffffa80`0982d570 fffffa80`07bd4000 00000000`00000000 : tcpip!TcpTcbReceive+0x275
fffff880`05707da0 fffff880`00e889bc : fffff880`04e7e022 fffffa80`07bd4000 00000000`00000000 fffff880`00e69501 : tcpip!TcpMatchReceive+0x1e9
fffff880`05707ee0 fffff880`00e66e6d : fffffa80`07bd3f00 fffff880`00f858b0 fffff880`057007c0 fffffa80`086677d0 : tcpip!TcpPreValidatedReceive+0x31c
fffff880`05707fc0 fffff880`00e67a69 : 00000000`00000000 00000000`00000000 ffff0000`05878dff 00000051`00000481 : tcpip!IppDeliverListToProtocol+0x4d
fffff880`05708080 fffff880`00e670f0 : fffff880`00f858b0 fffffa80`08667800 00000000`00000000 fffff880`05708140 : tcpip!IppProcessDeliverList+0x59
fffff880`057080f0 fffff880`00e687c4 : 00000000`00000000 fffffa80`07bd4000 fffff880`00f858b0 00000000`0869d001 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`057081e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x664
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!TdxEventReceiveConnection+300
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tdx!TdxEventReceiveConnection+300
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4943190b
FAILURE_BUCKET_ID: X64_0xD1_tdx!TdxEventReceiveConnection+300
BUCKET_ID: X64_0xD1_tdx!TdxEventReceiveConnection+300
Followup: MachineOwner
---------
Edited by usasma, 09 April 2009 - 09:42 AM.
Edited by usasma, 09 April 2009 - 10:16 AM.
2) Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.
1. Select 2nd option - "Create custom settings (for code developers)" 2. Select 2nd option - "Select individual settings from a full list" 3. Check these boxes - Special Pool Pool Tracking Force IRQL checking Deadlock Detection Miscellaneous Checks</blockquote> 4. Select last option - "Select driver names from a list" 5. Click on the Provider heading - sorts list by Provider 6. Check ALL boxes where Microsoft is not the Provider 7. Click on Finish 8. Re-boot
0 members, 0 guests, 0 anonymous users
Community Forum Software by IP.Board
Licensed to: Geeks to Go, Inc.