Hallo
Der Uzebox-Emulator uzem.exe lief seit Tagen ohne Probleme. Heute gibt
es jedesmal einen Bluescreen, wenn ich ihn mit einer Hex-Datei starte:
1 | A problem has been detected and Windows has been shut down to prevent damage
|
2 | to your computer.
|
3 |
|
4 | The problem seems to be caused by the following file: ntkrnlpa.exe
|
5 |
|
6 | CRITICAL_OBJECT_TERMINATION
|
7 |
|
8 | If this is the first time [...]
|
9 |
|
10 | Technical Information:
|
11 |
|
12 | *** STOP: 0x000000f4 (0x00000003, 0x893a95c8, 0x893a9714, 0x82a37b00)
|
13 |
|
14 | *** ntkrnlpa.exe - Address 0x828deabf base at 0x82811000 DateStamp 0x5037809b
|
(BluescreenView)
Mit einem Wiederherstellungspunkt und sfc konnte ich den Fehler nicht
beheben. Und mit dem Dump kann ich leider nur wenig anfangen:
1 | Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
|
2 | Copyright (c) Microsoft Corporation. All rights reserved.
|
3 |
|
4 |
|
5 | Loading Dump File [C:\Windows\Minidump\Mini021213-07.dmp]
|
6 | Mini Kernel Dump File: Only registers and stack trace are available
|
7 |
|
8 | Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
|
9 | Executable search path is:
|
10 | Windows 7 Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
|
11 | Product: WinNt, suite: TerminalServer SingleUserTS
|
12 | Built by: 6002.18686.x86fre.vistasp2_gdr.120824-0336
|
13 | Kernel base = 0x82811000 PsLoadedModuleList = 0x82928c70
|
14 | Debug session time: Tue Feb 12 13:30:20.056 2013 (GMT+1)
|
15 | System Uptime: 0 days 0:02:13.866
|
16 | Loading Kernel Symbols
|
17 | ...............................................................................................................................................................
|
18 | Loading User Symbols
|
19 | Loading unloaded module list
|
20 | .....
|
21 | *******************************************************************************
|
22 | * *
|
23 | * Bugcheck Analysis *
|
24 | * *
|
25 | *******************************************************************************
|
26 |
|
27 | Use !analyze -v to get detailed debugging information.
|
28 |
|
29 | BugCheck F4, {3, 893a95c8, 893a9714, 82a37b00}
|
30 |
|
31 | *** WARNING: Unable to verify timestamp for SYMEVENT.SYS
|
32 | *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
|
33 | Probably caused by : csrss.exe
|
34 |
|
35 | Followup: MachineOwner
|
36 | ---------
|
Allerdings müsste es doch möglich sein, mit einer entsprechenden
Sandbox/Debugger, die Ursache des Bluescreen zu finden, da ich den
Bluescreen sicher auslösen kann.
Was kann ich noch tun, um den Fehler zu beheben?
