Analyzer Shutdown

Hi
When i open the bex analyzer and selecting the report, variable screen is popping up. When i click on the variable screen to enter the values, application gets shut down. This is happening all the time. What is to be checked to correct the problem. There is no message displayed as well. Application just shuts.
Thanks
Annie

Hi,
It looks like Operating system is terminating the application due to some error. check in Event View for error message.
To open event viewer:
http://support.microsoft.com/kb/308427
Regards,
Pruthvi R

Similar Messages

Analyze shutdown-sequence ?

Hi,
The problem:
We have desktops (hp) that the user shuts down normally.
The problem is that some (not all) , won't boot correctly the day after.
They are presented with "start windows normally" or "Repair windows".
If they choose "normally" than they are presented with the loginscreen. After filling in the credentials and pressing ENTER, the'll receive the alert that there is "no trust relationship with the AD".
Running the "repair windows" only makes things worse.
QUESTION:
Since there is no way to know what computer will fail next, i can't use Windows Performance Kit tools to do a trace of the shutdown. How can i determine the reason for this strange behaviour?
Can i find this in the eventlog? If so where do i look?
Other suggestions are most welcome?
Kind regards,
Kristof

Hi Kristof,
To get a list of shutdown event with datetime and reason, we can take use of Event Viewer to filter Event ID: 1074 in System Event log.
Run Eventvwr.exe->Windows Logs\System->Right-Click on it and select "Filter Current Log…"->Filter: Event log: System Event ID: 1074
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Analyze and Write a log of windows logon/shutdown script and policy

Good Morning,
Is there a way to write a complete log of pc from when it start to receive the domain policy for the machine and user and for the startup/shutdown process?
Thanks for you help.
Salento.

Hi Salento,
Before going further, what do we want to do? Are we troubleshooting something?
If we want to troubleshoot group policy, we can collect group policy result to check if our policy settings get applied properly.
To collect group policy result:
1. On domain controller, click Start -> Run, type GPMC.MSC, it will load the GPMC console.
2. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper
user in the wizard)
3. Right click the resulting group policy result and click the "Save Report…" => save report to save the report to a HTML file.
If we need more specific information for troubleshooting group policy, we can enable gpsvc logging for group policy processing.
To enable Gpsvc logging, the following blog can be referred to as reference.
Userenvlog for Windows Vista/2008/Win7
http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx
In addition, regarding group policy debug log settings, the following article can be referred to for more information.
Group Policy Debug Log Settings
http://social.technet.microsoft.com/wiki/contents/articles/4506.group-policy-debug-log-settings.aspx
Best regards,
Frank Shen

How to find out the info regarding Solaris, server hang or shutdown.

Hi
As I am handling the Solaris 9 Server remotely.
As in last week the server has stopped to respond suddenly, we have tried to ping, ssh which was not working. As ultimately we have asked the Data Centre Team to hard reboot the same, to resolve the issue.
In the same ref I would like to know how we come to know the reason, what caused to reboot the same, i.e . any log file, etc..
I have check /var/adm/messages, but not found any detail for the same.
Thanks
Rajan
I

No core files?
No hope for an answer.
As you learned in the other Internet forum.
http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-find-out-the-info-regarding-solaris-server-hang-or-shutdown.-621500/
To get such corefiles analyzed,
you would need to use your service contract and log a support case with Sun.
They have the special software tools to do that.

Windows 7 bluescreens on shutdown, problem persists after Windows reinstall

PAGE_FAULT_IN_NONPAGED_AREA. The video shuts down too quickly for me to read anything else.
Sure, it sounds like a hardware problem. However,
1) It doesn't happen when I shutdown from safe mode (before nor after reinstalling Windows)
2) I ran the Windows memory diagnostics and they come up clean
I live in Brazil so I'm running the Brazilian Portuguese version.
Any clues?

Hi,
As ZigZag3143x says, detail information is very important for analyzing.
Before we could get your Minidump files, I would like to suggest you try the following:
1. Update your display card and chipset drivers.
2. check disk.
Run Check Disk from a Command Line to Check for and fix Disk Errors
http://technet.microsoft.com/en-us/magazine/ee872425.aspx
3. Also refer to the article below which explains about this error.
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
In addition, you may refer to the following link to check the issue:
"Resolving stop (blue screen) errors in Windows 7
http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7
Hope it helps.
Regards,
Blair Deng
Blair Deng
TechNet Community Support

Analyzing Table

The table has millions of records and my Oracle db is 8.1.6 . I need to analyze this table , when can i do analyze this big table. Actually my environment is offline env, after 6 Pm it would be shutdown .
So please help me out when can i do analye that table and please send me the steps for doing analyzation.
Thanks

816:
http://download.oracle.com/docs/cd/A81042_01/DOC/server.816/a76989/ch4d8.htm#30559
If the database is down at 6pm, i'd do it before 6pm. Like right after it comes up.
Why do you feel you need to analyze the table? What optimizer mode are you running?

Read last shutdown information

Hello.
Where can I read information about last shutdown (a type of shutdown - normal, transactional, immediate, abort ...)?
Thanks.

Hi,
In that case you can write a startup and shutdown trigger on the database.
In the shutdown trigger,
-You would add a record in your table (say log table), all the details which you need to analyze by your client application.
The below is optional if you want to check for abort condition.
In the startup trigger.
-You would add a record about the timing of the startup of the database.
- Moreover you would also check the last inserted record. If the last inserted record was that of startup. This would mean that the last shutdown was not a clear shutdown could be a result of crash/abort (As it does not fire the shutdown trigger). If this is the case you would make a entry of shutdown here (time of shutdown would not be known but you can do approximation from v$log / v$archived_log).
Regards
Anurag Tibrewal.

Hyperion Analyzer Server

I installed Hyperion Analyzer 7.2.5.3 on the window server. I also installed IIS and it seems to be working. I need to connect this to Essbase and I did change the Essbase server name in Analyzer.properties file, but when I click on the url from my application, I get the error "Page not found".
Does anybody know the cause? Do I need to install Essbase Client version for Windows on the server?
Thanks

hi,
In order to connect reports, tomcat service should be run contionously. If you logged off the server, these services can be shutdown.
You can make the tomcat service as windows service, so even if you logged off (serivce will remain active).
To move analyzer reports from development to production, take the export (from dev) and import (in prod).
Export is available in analyzer by using File->Export. You can export one report or all reports in one file.
Once export file is complete, copy it in prod server and take the import from analyzer.
thanks,

SAPCCM4X Agent Shutdown

Hello
A few SAPCCM4X agents are shutting down by itself. Analyzing the log of this agents the message below is informed:
Mon Aug 23 12:15:16 2010
CCMCTRL: ERROR: csm_show_file: no permission to read /usr/sap/PRD/SYS/profile/PR
D_G08_sapprdi
CCMCTRL: ERROR: csm_show_file: Please check sapccmsr.ini
I tried to find the profile mentioned in the warning but with no succes. I know that the cause of the shutdown of the agent is that because the correct profile is PRD_D08_sapprdi instead of PRD_G08_sapprdi. I also checked sapccmsr.ini but found nothing.
I can start the agent normally choosing the correct parameter (PRD_D08_sapprdi) but sometimes the agent shutdown by itself with the error message above.
Why the agent search for the wrong profile and where can I change it to the right profile?
Thanks in advance

Thank you Mani, I will make this test in only one appl server and monitor.
I will let you know the resul of my tests.
Regards

Syslog Analyzer and RME4.0.5

I checked previous discussion regarding this topic and was unable to find a solution. My syslog analyzer was working at one point, but now it has stopped and I can not get it back to a working condition. It appears the Analyzer is running, but not registering with the collector:
RME displays zero messages received by syslog collector
Syslog collector status always returns the following but is running
SLCA0132: Collector Status is currently not available.
Check whether the SyslogAnalyzer process is running normally.
        Process= SyslogCollector
        State = Program started - No mgt msgs received
        Pid    = 4452
        RC     = 0
        Signo = 0
        Start = 7/12/2010 12:27:19 PM
        Stop   = Not applicable
        Core   = Not applicable
        Info   = Server started by admin request
     Process= jrm
        State = Running normally
        Pid    = 5812
        RC     = 0
        Signo = 0
        Start = 7/12/2010 12:27:40 PM
        Stop   = Not applicable
        Core   = Not applicable
        Info   = Server started by admin request
        Process= CTMJrmServer
        State = Running normally
        Pid    = 9824
        RC     = 0
        Signo = 0
        Start = 7/12/2010 12:31:02 PM
        Stop   = Not applicable
        Core   = Not applicable
        Info   = CTMJrmServer started.
        Process= SyslogAnalyzer
        State = Program started - No mgt msgs received
        Pid    = 4564
        RC     = 0
        Signo = 0
        Start = 7/12/2010 12:32:00 PM
        Stop   = Not applicable
SYSLOG Collector.log
SyslogCollector - [Thread: main] INFO , 12 Jul 2010 12:27:19,703, Logging System Initialized.
SyslogCollector - [Thread: main] INFO , 12 Jul 2010 12:27:19,703, System Initialized.
SyslogCollector - [Thread: main] INFO , 12 Jul 2010 12:27:19,917, Subscriber list is empty!
SyslogCollector - [Thread: main] INFO , 12 Jul 2010 12:27:26,247, Service started...
Tried to subscribe to the collector - received the folowing message.
SLCA0126: Could not subscribe to the Collector.
1.Check whether the collector is running.
2.Make sure that SSL certificates are imported/exported correctly and process restarted.
3.Check whether the Certificates exported/imported are valid and have not expired.
4.Check whether SyslogAnalyzer process is running.
Any help would be appreciated.
Thanks

You are running a very old version of RME. You should consider upgrading to RME 4.0.6 at least.
Shutdown the SyslogCollector and SyslogAnalyzer daemons. Empty out the contents of NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/sa/data/collectors.dat and NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/filters.dat. Then restart both daemons, and see if the subscription occurs. Note: due to a bug in your version of RME, this may take a long time to sync if you have numerous automated actions configured.

SAP - shutdown

Hi,
We had our Production System went down suddenly. When I analyzed the log details. I found the following. I went manually using SIDADM and started the SAP. Now it is working. But i would like to know what had caused the sudden interruption. Can someone help us?
Mon Mar 1 04:01:17 2010
***LOG Q0E=> SigIGenAction, signal ( 33) [sigux.c      1067]
DpHalt: shutdown server >DBSERVER_UP1_00                         < (normal)
DpModState: change server state from ACTIVE to SHUTDOWN
Stop work processes
Mon Mar 1 04:01:20 2010
Stop gateway
ERROR => DpProcKill: kill failed (3: No such process) [dpuxdisp.c   404]
Stop icman
Terminate gui connections
wait for end of work processes
waiting for termination of work processes ...
Mon Mar 1 04:01:23 2010
waiting for termination of work processes ...
Mon Mar 1 04:01:24 2010
Mon Mar 1 04:01:27 2010
waiting for termination of work processes ...
Mon Mar 1 04:01:28 2010
waiting for termination of work processes ...
DpStartStopMsg: send stop message (myname is >DBSERVER_UP1_00
      <)
***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3948]
ERROR => NiIWrite: SiSendV failed for hdl 3 / sock 12
    (SI_ECONN_BROKEN/32; UD; ST; 192.168.102.244:3900) [nixxi.cpp    3948]
ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi.c      2480]
ERROR => MsISnd2: MsINiWrite (rc=NIECONN_BROKEN) [msxxi.c      1438]
MBUF state OFF
MBUF component DOWN
ERROR => DpStartStopMsg: MsSnd2Type failed (rc=-100) [dpxxdisp.c   14285]
ERROR => MsIReceive: not_attached [msxxi.c      1201]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
ERROR => DpHalt: MsSendKeepalive failed (-3) [dpxxdisp.c   10943]
detach from message server
cleanup EM
cleanup event management
cleanup shared memory/semaphores
Mon Mar 1 04:01:59 2010
removing request queue
***LOG Q05=> DpHalt, DPStop ( 618560) [dpxxdisp.c   11257]
shutdown completed - server stopped ***
=> Stack Trace:
        DpHalt() at 0x101300f34
        SigIGenAction() at 0x1000c1f04
        Unknown at 0x44a4
!!! Invalid stack address encountered: 0x0
!!! Stack corrupted.

> Mon Mar 1 04:01:17 2010
> ***LOG Q0E=> SigIGenAction, signal ( 33) [sigux.c      1067]
> DpHalt: shutdown server >DBSERVER_UP1_00                         < (normal)
> DpModState: change server state from ACTIVE to SHUTDOWN
> Stop work processes
Someone issued a "normal shutdown" of the instance.
Markus

Automatic shutdown on PlayBook

hi folks,
my playbook shut down automatic! If i'm on a game or make music comes the popup your PlayBook shutdown! It was 4 or 5 times maybe! The Battery is full and i have restart the PlayBook from time to time! Anyone's knows what it is? To much sideloading?
Kind Regards
Funky Dread

I think i known that the issue is from an Android App! Everytime if opend the Android Player i see a popup in the left top corner, with the Android sympol and error loading app information!
Well, this is from to much sideloading i think! The latest PlayBook update with 30mb stopped on 23% and load after a short time the completly OS with 430mb and install it!
I will reset the PlayBook in the next day's and we will look what it does! It was cool if the PlayBook has a Event Log like on BB Phones! Or any tool to analyzed what it happend
Kind Regards
Funky Dread

Node shutdown or crash

When a primary node shutdown or crash happens, somtimes the node is not getting shutdown properly because some cluster processes like "/etc/rc0.d/K05initrgm stop" are continously running . Meanwhile
The application is getting failovered to seondary node , but it is going to intermediate stage "Pending Online".
And both are hung.Below is the status
cldevicegroup status:
=== Cluster Device Groups ===
--- Device Group Status ---
Device Group Name Primary Secondary Status
devset - - Offline
What might cause above problem like some cluster processes not coming out ...

You are not saying which specific Sun Cluster version you are using. Since you refer to /etc/rc0.d/K05initrgm I assume it is Sun Cluster 3.1. The question is, which update and patch level?
You should make sure to have the most recent Patches for this release applied. There are known and fixed problems around this script being hung - but they are fixed for quite some time in the corresponding Patches.
If you have all recent Patches applied, I suggest to open a service call to further analyze the problem.
Greets
Thorsten

EAP service causes slow shutdown

Hi
I've got a problem with my desktop PC Win7 pro. serv. pack 1.
All of the sudden I have a very slow shutdown (2-3 min) - for no apparent reason.
I've pinned the problem down to the service EAP (extensible authentication protocol) when this service is stopped Win7 shuts down normally (5 sec).
But I need EAP for internet - currently EAP is set to manual...
Clear pagefile at shutdown is disabled and waittokill is set to the min. value of 2000
Any suggestions?
I've got a etl shutdown trace file for Win performance analyzer, can anybody help me interpret it?
By the way I've got all of my drivers updated..!

I solved the problem on my own - a bit embarrassing perhaps, but here goes.
I found out that "IsDegradation "true" means that some Windows built-in application or service has caused this slowdown. For example
sidebar.exe (Desktop Gadgets) or ssdpsrv (SSDP Discovery). If it reads "false", the problem lies elsewhere." (thanks https://www.winhelp.us/troubleshoot-performance-in-windows-vista-and-7.html)
When I connect direct lan (cable in PC) shutdown was normal, so it had to do with the wireless network connection, I had another look at adapter settings and I always had two connections there with a red cross (active but not connected) those where:
Intel(R) 82579V Gigabit Network Connection and Microsoft Virtual WiFi Miniport Adapter #2 - I deactivated those two (right click and deactivate) and problem was solved, PC shutdown is back to 8 sec. (wireless setting on Atheros must have been changed somehow
conflicting with other inactive connections?) but inactive conn. most probably should have been deactivated long time ago #)
So - Controlpanel - Network and sharing center - Change adapter settings - Deactivate all other connections than Qualcomm Atheros AR9287.

Wdf01000.sys BSOD on shutdown after imaging

We have SCCM 2012 R2 and Dell. Using the latest combo drivers on Dell, imaging Win7 x86/x64.
I've been seeing BSOD on shutdown on almost all desktops/laptops. They don't BSOD every time, maybe 20-30% of the time on 5-10% of all desktops/laptops.
Dump is below.
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\katiecc\Downloads\e7440_111214-8330-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`032a2890
Debug session time: Wed Nov 12 13:49:33.070 2014 (UTC - 8:00)
System Uptime: 0 days 0:07:08.907
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88000ec6cce, fffff8800a993308, fffff8800a992b60}
*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
Probably caused by : TeeDriverx64.sys ( TeeDriverx64+fc0d )
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000ec6cce, The address that the exception occurred at
Arg3: fffff8800a993308, Exception Record Address
Arg4: fffff8800a992b60, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
Wdf01000!FxIoQueue::CancelForQueue+252
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14
EXCEPTION_RECORD: fffff8800a993308 -- (.exr 0xfffff8800a993308)
ExceptionAddress: fffff88000ec6cce (Wdf01000!FxIoQueue::CancelForQueue+0x0000000000000252)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000038
Attempt to write to address 0000000000000038
CONTEXT: fffff8800a992b60 -- (.cxr 0xfffff8800a992b60;r)
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
r8=0000000000001000 r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
r8=0000000000001000 r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000038
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
GetUlongFromAddress: unable to read from fffff8000330c1c0
0000000000000038 Nonpaged pool
FOLLOWUP_IP:
TeeDriverx64+fc0d
fffff880`05117c0d ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff88000ec665b to fffff88000ec6cce
STACK_TEXT:
fffff880`0a993540 fffff880`00ec665b : fffffa80`109c14a0 fffff880`0a993600 00000000`00000000 fffffa80`109c14a0 : Wdf01000!FxIoQueue::CancelForQueue+0x252
fffff880`0a9935b0 fffff880`00eb33d3 : 00000000`00000000 fffffa80`109c14a0 0000057f`ef63eb58 00000000`00001003 : Wdf01000!FxIoQueue::QueuePurge+0x28f
fffff880`0a993630 fffff880`05117c0d : fffffa80`109c14a0 fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 : Wdf01000!imp_WdfIoQueuePurge+0x10b
fffff880`0a993690 fffffa80`109c14a0 : fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 : TeeDriverx64+0xfc0d
fffff880`0a993698 fffffa80`109912d0 : fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a : 0xfffffa80`109c14a0
fffff880`0a9936a0 fffff880`0511c028 : fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 : 0xfffffa80`109912d0
fffff880`0a9936a8 fffff880`0511c028 : fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 : TeeDriverx64+0x14028
fffff880`0a9936b0 fffffa80`109901e0 : fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 : TeeDriverx64+0x14028
fffff880`0a9936b8 fffff880`00e64e1a : fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 00000000`00000000 : 0xfffffa80`109901e0
fffff880`0a9936c0 fffff880`00e58288 : fffffa80`109901e0 00000000`00000000 00000000`00000005 fffff880`0a9937d8 : Wdf01000!FxPkgPnp::NotifyResourceObjectsDx+0x4a
fffff880`0a993730 fffff880`00e64e99 : 00000000`00000000 fffff880`0a9938b0 fffff880`00edb200 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0x120
fffff880`0a993780 fffff880`00e5b0f8 : 00000000`0000031c fffff880`0a9938b0 00000000`ffff7fff fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0x9
fffff880`0a9937b0 fffff880`00e5ada6 : fffff880`00edb1c0 fffffa80`10990398 fffffa80`109901e0 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`0a993910 fffff880`00e5b627 : 00000000`00000000 fffff880`0a9939f0 fffffa80`10990380 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`0a993980 fffff880`00e65dd3 : 00000000`00000000 fffffa80`109901e0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`0a993a20 fffff880`00e476f2 : 00000000`00000002 0000057f`ef66efd8 fffffa80`109a8bb0 fffffa80`12b46402 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`0a993a70 fffff880`00e4679a : fffffa80`12b46410 fffffa80`12b46410 fffffa80`12b46410 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`0a993ad0 fffff880`00e46866 : fffffa80`12b46410 00000000`00000000 fffffa80`109a8bb0 fffffa80`109a8bb0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`0a993b10 fffff800`031f0eb5 : 00000000`00000001 00000000`00000000 fffffa80`109a8bb0 fffffa80`12b464b8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`0a993b50 fffff800`0337073a : ffffffff`fa0a1f00 fffffa80`1235ab50 00000000`00000080 fffff8a0`00000002 : nt!PopIrpWorker+0x3c5
fffff880`0a993c00 fffff800`030c58e6 : fffff800`0324fe80 fffffa80`1235ab50 fffffa80`13004b50 fffffa80`13b9f010 : nt!PspSystemThreadStartup+0x5a
fffff880`0a993c40 00000000`00000000 : fffff880`0a994000 fffff880`0a98e000 fffff880`0a9932e0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: TeeDriverx64+fc0d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TeeDriverx64
IMAGE_NAME: TeeDriverx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51d31e10
STACK_COMMAND: .cxr 0xfffff8800a992b60 ; kb
FAILURE_BUCKET_ID: X64_0x7E_TeeDriverx64+fc0d
BUCKET_ID: X64_0x7E_TeeDriverx64+fc0d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_teedriverx64+fc0d
FAILURE_ID_HASH: {c079e5d7-83f0-230c-5936-8e6123aa32cd}
Followup: MachineOwner

Hi,
>> *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
>> *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
>> Probably caused by : TeeDriverx64.sys ( TeeDriverx64+fc0d )
I suspect the BSOD is caused by Intel(R) Management Engine Interface (c:\windows\system32\drivers\teedriverx64.sys).
Uninstall it and make sure TeeDriverx64.sys is deleted.
Restart machine several times.
After restart, windows will auto configure the appropriate native system driver.
Reference:
Please help keep getting BSOD aiming to wdf01000.sys error
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/please-help-keep-getting-bsod-aiming-to/1e5f7c9b-1dd3-4423-8dfb-37d4b37b995a
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Analyzer Shutdown

Similar Messages

Maybe you are looking for