*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {fffff800041fcff0, 0, 0, fffff80002a864fc}
Probably caused by : hardware ( nt!KiInterruptHandler+29 )
Followup: MachineOwner
874257407 KB total disk space.
79661744 KB in 126202 files.
81224 KB in 31362 indexes.
0 KB in bad sectors.
345279 KB in use by the system.
65536 KB occupied by the log file.
794169160 KB available on disk.
4096 bytes in each allocation unit.
218564351 total allocation units on disk.
198542290 allocation units available on disk.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-09-30T08:49:39.791223300Z" />
<EventRecordID>15914</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Dom-Komputer</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff80002c20730, fffff80002c20710, fffff80002c20730}
Probably caused by : memory_corruption
Followup: memory_corruption
ref:There are many programs that can generate this type of error. Any suggestions found on support forum or software developers sites should be verified that they apply to your application (though comments for other applications may provide additional clues in solving this). The first step in troubleshooting this would be to check for updates for the application specified in the event.
A common application causing this problem is Adobe Designer (C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe). From an Adobe Support Forum: "For Vista 64 bit users this error seems to be caused by a wrong manifest embedded in the FormDesigner application. It references the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first."
A similar comment (almost identical but with more details), that apparently, if followed, can fix the problem: "This error is caused by a wrong manifest embedded in the FormDesigner application. If you open the application in Visual Studio and extract the manifest you will see two references to the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first. To test just try removing the processor-agnostic reference from the manifest and resave the app in Visual Studio. When you rerun the app the errors are gone.
IMO this should be fixed by Adobe - and obviously since the FormDesigner app is 32-bit the reference should be restricted to 32-bit."
x 15
Explanation
This event is written during startup following an unexpected restart or shutdown. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer's reset button or unplugs the power cord.
If the Persistent Time Stamp group policy setting is either enabled or not configured, system information is written to the data section of this event. This information includes a timestamp that indicates the computer's uptime in seconds before the unexpected shutdown occurred.
User Action
One or more of the following actions might help to determine the cause of the unexpected shutdown:
- Check the system event log for other events that occurred around the same time as the unexpected shutdown.
- Find out whether the computer's reset button was pressed, the power cord was unplugged, or a general power failure occurred.
- Configure Windows to perform a memory dump of system failures and submit that data to Microsoft for debugging through Windows Error Reporting. For more information about Windows Error Reporting, see Help and Support.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002bbba9b, fffff880033a8418, fffff880033a7c70}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )
Followup: Pool_corruption