Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD STOP CODE 0x7E When Machine Is Left On For Extended Time

20 Apr 2015   #1
ChrisStayner21

Windows 10 Professional 64-bit
 
 
BSOD STOP CODE 0x7E When Machine Is Left On For Extended Time

Hello all,

I am getting this stop code on one of the computers I manage where I work:

STOP CODE 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDELED

Unfortunately, I am not around to see it happen, and the person who uses the computer gives me information that leaves a LOT to be desired.

So far it sounds like it happens mostly when the computer is left on for an extended period of time, like over a weekend.

I have created a zip file using the SF Diagnostic Tool and have attatched it to this thread. Please take a look at it and let me know about anything you see. I would do it myself, but I am not that good at debugging errors and such like this.


My System SpecsSystem Spec
.
20 Apr 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It is a different computer than that is shown in the system specs. It is a HP Compaq 8200 Elite SFF PC.

Go to HP's site and update Intel Management Interface. (If you think IME is unnecessary for you, you may uninstall it, too).

Report us for any further BSOD.
________________________________________________
Code:
BugCheck 1000007E, {c0000005, 837c2cb3, aff2b8a0, aff2b480}

Unable to load image \SystemRoot\system32\DRIVERS\TeeDriver.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TeeDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriver.sys
Probably caused by : TeeDriver.sys ( TeeDriver+d3ae )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 837c2cb3, The address that the exception occurred at
Arg3: aff2b8a0, Exception Record Address
Arg4: aff2b480, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
Wdf01000!FxIoQueue::CancelForQueue+199
837c2cb3 89501c          mov     dword ptr [eax+1Ch],edx

EXCEPTION_RECORD:  aff2b8a0 -- (.exr 0xffffffffaff2b8a0)
ExceptionAddress: 837c2cb3 (Wdf01000!FxIoQueue::CancelForQueue+0x00000199)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 0000001c
Attempt to write to address 0000001c

CONTEXT:  aff2b480 -- (.cxr 0xffffffffaff2b480;r)
eax=00000000 ebx=85b11bf0 ecx=85b11c00 edx=00000000 esi=cdfb1748 edi=88caeee8
eip=837c2cb3 esp=aff2b968 ebp=aff2b978 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
Wdf01000!FxIoQueue::CancelForQueue+0x199:
837c2cb3 89501c          mov     dword ptr [eax+1Ch],edx ds:0023:0000001c=????????
Last set context:
eax=00000000 ebx=85b11bf0 ecx=85b11c00 edx=00000000 esi=cdfb1748 edi=88caeee8
eip=837c2cb3 esp=aff2b968 ebp=aff2b978 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
Wdf01000!FxIoQueue::CancelForQueue+0x199:
837c2cb3 89501c          mov     dword ptr [eax+1Ch],edx ds:0023:0000001c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  0000001c

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8317e84c
Unable to read MiSystemVaType memory at 8315df00
 0000001c 

FOLLOWUP_IP: 
TeeDriver+d3ae
949153ae ??              ???

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 837c27e1 to 837c2cb3

STACK_TEXT:  
aff2b978 837c27e1 85b11bf0 cdfb1700 7a4ee408 Wdf01000!FxIoQueue::CancelForQueue+0x199
aff2b9a8 837b514c 85b11bf0 00000001 00000001 Wdf01000!FxIoQueue::QueuePurge+0x1cc
aff2b9d4 949153ae 88caefd0 85b11bf0 00000000 Wdf01000!imp_WdfIoQueuePurge+0x9a
WARNING: Stack unwind information not available. Following frames may be wrong.
aff2b9f8 9490ef21 88cb3e78 94918014 88cb3e78 TeeDriver+0xd3ae
aff2ba10 9490e0fa 88cb3e78 00000000 00000000 TeeDriver+0x6f21
aff2ba30 9490deeb 88cb3e78 00000005 88c84ce8 TeeDriver+0x60fa
aff2ba48 8377db58 7734c300 00000005 837d1d88 TeeDriver+0x5eeb
aff2ba6c 8377e2d3 aff2bb10 8377ce18 88c84ce8 Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0xb3
aff2ba74 8377ce18 88c84ce8 00001000 837d1d60 Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0xd
aff2bb10 8377c2e5 88c84ce8 0000031c 88c84e08 Wdf01000!FxPkgPnp::PowerEnterNewState+0x15c
aff2bb38 8377c0e1 88c84ce8 aff2bb64 aff2bba8 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x167
aff2bb70 8377616b 88c84ce8 837760d6 88caeee8 Wdf01000!FxPkgPnp::PowerProcessEvent+0x185
aff2bb78 837760d6 88caeee8 88c84ce8 aff2bbb4 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x89
aff2bb88 83772d85 88c84ce8 aff2bba8 88cb3dbc Wdf01000!FxPkgFdo::_DispatchSetPower+0x28
aff2bbb4 8376d52e e0072008 88c84020 e0072008 Wdf01000!FxPkgPnp::Dispatch+0x1ad
aff2bbdc 8376d39f 88c84020 e0072008 88c84020 Wdf01000!FxDevice::Dispatch+0x155
aff2bbf8 83029e6d 88c84020 e0072008 00000000 Wdf01000!FxDevice::DispatchWithLock+0x77
aff2bc50 8321e00f 898b1930 87411240 00000000 nt!PopIrpWorker+0x351
aff2bc90 830c4699 83029b1c 898b1930 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  TeeDriver+d3ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: TeeDriver

IMAGE_NAME:  TeeDriver.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  512bc899

STACK_COMMAND:  .cxr 0xffffffffaff2b480 ; kb

FAILURE_BUCKET_ID:  0x7E_TeeDriver+d3ae

BUCKET_ID:  0x7E_TeeDriver+d3ae

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7e_teedriver+d3ae

FAILURE_ID_HASH:  {b4ed87b9-6549-8864-fdc4-2251586cb34f}

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

3: kd> lmvm TeeDriver
start    end        module name
94908000 9491f000   TeeDriver T (no symbols)           
    Loaded symbol image file: TeeDriver.sys
    Image path: \SystemRoot\system32\DRIVERS\TeeDriver.sys
    Image name: TeeDriver.sys
    Timestamp:        Tue Feb 26 01:54:57 2013 (512BC899)
    CheckSum:         0001D4FA
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 BSOD STOP CODE 0x7E When Machine Is Left On For Extended Time




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD when left idle, STOP code 0x0000007A
Basically as titled. When left idle for any extended period of time (sometimes after 30 minutes, sometimes it's gone as long as about 30 hours), I come back to a BSOD, either a crucial process or thread has stopped or a kernel inpage error. Started roughly a month ago... today's the first time...
BSOD Help and Support
Bsod Stop:0x7e on shutdown
I just updated my some hardware(cpu, motherboard, ram) but had to format because I'm stupid... any who, I had to update my drivers (I'm really not sure if that's the cause) I also have the latest BIOS but whenever I shutdown I get a BSOD with stop 0x7e. So those are pretty much my circumstances and...
BSOD Help and Support
Daily BSOD with various stop codes 0x1e, 0x3b, 0x7e
Hello. I finally gave up all hope trying to solve my problem by myself. Thing is early this year I started getting very random blue screens mostly blaming ntoskrnl, or other windows services. These blue screens didn't seem to have any real pattern and sometimes occurred when playing games...
BSOD Help and Support
BSOD using HDD for extended periods of time, error STOP 0x0000004f
Hello everyone, I've decided to join the forum seeking for help with this problem I'm facing on a relatively new Dell XPS 15 laptop. The machine is around 7 months old, has Windows 7 Home Premium 64 bit edition installed (OEM) and has been updated to SP1. The problem first appeared when trying...
BSOD Help and Support
BSOD : 0x7e with error code 0xC0000005
Hi, Attaching here BSOD crash dump file, BTW i am using Windows XP embedded OS, If this is not the right place to ask help for XP embedded then please suggest.
BSOD Help and Support
BSOD STOP: 0x3B atikmdag.sys/STOP: 0x7E dxgmms1.sys
Guys I'm at a loss I'm getting BSOD's all the time I really don't know what to do with it, and I'm not computer heavy so. If someone here could help me that would be appreciated. I've included a Dxdiag file with the rest.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:15.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App