my computer keeps shytting of in the middle of things and I went to the events viewer and this is the last recorded event. I am goin g crazy with this maching. Help!!!!!
-
mercoledì 14 marzo 2012 22:36Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 3/14/2012 3:45:36 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: BarbaraDepne-pc
Description:
Session "Homegroup Log" failed to start with the following error: 0xC0000035
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2012-03-14T21:45:36.748216700Z" />
<EventRecordID>189</EventRecordID>
<Correlation />
<Execution ProcessID="1012" ThreadID="6268" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>BarbaraDepne-pc</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Homegroup Log</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225525</Data>
<Data Name="LoggingMode">285212677</Data>
</EventData>
</Event>
Tutte le risposte
-
mercoledì 14 marzo 2012 23:27
goto memtest.org and download the CD/USB version as needed and test your memory to be sure its OK
Windows MVP 2010-11, XP, Vista, 7. Expanding into Windows Server 2008 R2, SQL Server, SharePoint, Cloud, Virtualization etc. etc.
Hardcore Games, Legendary is the only Way to Play
Developer | Windows IT | Chess | Economics | Vegan Advocate | PC Reviews
-
venerdì 16 marzo 2012 07:10Moderatore
You may boot in Clean Boot Mode.
If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.
Another way is enable muni-dump and use Windbg. Please refer:
How to read the small memory dump files that Windows creates for debugging
You may paste the result in your next post for analyzing.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Contrassegnato come risposta Arthur XieMicrosoft Contingent Staff, Moderator mercoledì 28 marzo 2012 08:59
-
venerdì 16 marzo 2012 13:56
Some of the things I do when faced with PC problems:
1) Has it ever worked? Has it been stable in the past?
2) If yes, when the problem started occurring what if anything changed? New hardware? New software? The external environment change?
3) When was the last time the PC was checked for clogged fans / dust?
-Dennis
Occams Razor

