Ik weet niet of dit beter in Win Clients past of Software Algemeen, want het gaat hier om een BSOD maar over specifieke software.
Iedere keer als ik een .vob importeer in Encore CS3 krijg ik een BSOD. Verder werkt alles wat te maken heeft met video/CS3/nVidia (spelletjes) gewoon goed.
Ik weet niet zo goed waar ik het zoeken moet. Hier is de BSoD melding:
Ik probeerde wat via WinDBG te weten te komen maar ik wordt er niet veel wijzer uit. Mede omdat "symbols could not be loaded for nvlddmkm.sys", dus ik heb al geprobeert (tip van google) extra symbols op te geven via http://msdl.microsoft.com/download/symbols maar dat verandert niets.
Debug:
Heb je niet zoveel aan dus. Brakke nvlddmkm.sys en dxgkrnl.sys zeggen "Attempt to reset the display driver and recover from timeout failed" omdat Encore CS3 mijn vobs niet leuk vind.
Iemand ervaring mee?
Iedere keer als ik een .vob importeer in Encore CS3 krijg ik een BSOD. Verder werkt alles wat te maken heeft met video/CS3/nVidia (spelletjes) gewoon goed.
Ik weet niet zo goed waar ik het zoeken moet. Hier is de BSoD melding:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: dxgkrnl.sys If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x00000116 (0xfffffa8009b2d1c0, 0xfffff88007594220, 0x0000000000000000, 0x0000000000000002) *** dxgkrnl.sys - Address 0xfffff880044a1ef8 base at 0xfffff88004445000 DateStamp 0x4ac5509e |
Ik probeerde wat via WinDBG te weten te komen maar ik wordt er niet veel wijzer uit. Mede omdat "symbols could not be loaded for nvlddmkm.sys", dus ik heb al geprobeert (tip van google) extra symbols op te geven via http://msdl.microsoft.com/download/symbols maar dat verandert niets.
Debug:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
| Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Home\Desktop\Crash100107\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*D:\Common\Win7 Debug Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0400c000 PsLoadedModuleList = 0xfffff800`04249e50
Debug session time: Thu Jan 7 19:37:09.668 2010 (GMT+1)
System Uptime: 0 days 20:43:08.682
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8009b2d1c0, fffff88007594220, 0, 2}
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009b2d1c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007594220, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+e7220
fffff880`07594220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`07f00258)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`052eb9c8 fffff880`044a1ef8 : 00000000`00000116 fffffa80`09b2d1c0 fffff880`07594220 00000000`00000000 : nt!KeBugCheckEx
fffff880`052eb9d0 fffff880`044a1c02 : fffff880`07594220 fffffa80`09b2d1c0 fffffa80`03c20260 fffffa80`06d0a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`052eba10 fffff880`04548f07 : fffffa80`09b2d1c0 00000000`00000000 fffffa80`03c20260 fffffa80`06d0a410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`052eba40 fffff880`04572b75 : 00000000`ffffffff 00000000`0048f41c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`052ebb20 fffff880`045712bb : 00000000`00000102 00000000`00000003 00000000`0048f41c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`052ebb50 fffff880`045442c6 : ffffffff`ff676980 fffffa80`06d0a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`052ebbf0 fffff880`04570e7a : 00000000`00000000 fffffa80`09ac5510 00000000`00000080 fffffa80`06d0a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`052ebd00 fffff800`04321166 : 00000000`fffffc32 fffffa80`06a8eb60 fffffa80`039cc040 fffffa80`06a8eb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`052ebd40 fffff800`0405c486 : fffff800`041f6e80 fffffa80`06a8eb60 fffff800`04204c40 fffff880`0142da90 : nt!PspSystemThreadStartup+0x5a
fffff880`052ebd80 00000000`00000000 : fffff880`052ec000 fffff880`052e6000 fffff880`052eaca0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+e7220
fffff880`07594220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`07f00258)],0
SYMBOL_NAME: nvlddmkm+e7220
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
--------- |
Heb je niet zoveel aan dus. Brakke nvlddmkm.sys en dxgkrnl.sys zeggen "Attempt to reset the display driver and recover from timeout failed" omdat Encore CS3 mijn vobs niet leuk vind.
Iemand ervaring mee?
🇪🇺 Buy from EU (GoT)