Hi,
I am currently having some problems with BSoD appearing while I'm browsing local network shares on our company servers through F5 Firepass vpn. It seems to come at random when you are viewing/editing office documents, but you can force the same bsod by searching for ppt etc on a network disk and just scroll down the page.
It seems for now that it is only affecting our Dell laptops, especially the Latitude E6410 but other models are affected too. Ive tried a few different Win 7 pro x64 images, the latest being with sp1 included. I did some tests with a Lenovo Thinkpad T60 and it stopped getting bsod after I installed Win 7 with sp1 included.
Give me a shout if you need any more information.
Thanks for all your help in advance.
I am currently having some problems with BSoD appearing while I'm browsing local network shares on our company servers through F5 Firepass vpn. It seems to come at random when you are viewing/editing office documents, but you can force the same bsod by searching for ppt etc on a network disk and just scroll down the page.
It seems for now that it is only affecting our Dell laptops, especially the Latitude E6410 but other models are affected too. Ive tried a few different Win 7 pro x64 images, the latest being with sp1 included. I did some tests with a Lenovo Thinkpad T60 and it stopped getting bsod after I installed Win 7 with sp1 included.
Give me a shout if you need any more information.
Thanks for all your help in advance.
Code:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88001892c24
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: TunnelServer.e
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002cc82a9 to fffff80002cc8d00
STACK_TEXT:
fffff800`00ba4d28 fffff800`02cc82a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02cc6772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`01892c24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`064db000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tdx!TdxSendConnection+0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!TdxSendConnection+4
fffff880`01892c24 4154 push r12
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tdx!TdxSendConnection+4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79332
FAILURE_BUCKET_ID: X64_0x7f_8_tdx!TdxSendConnection+4
BUCKET_ID: X64_0x7f_8_tdx!TdxSendConnection+4
Followup: MachineOwner
Attachments
Last edited: