Windows XP Black screen

gorenjc je 25. feb 2011 ob 16:55 izjavil:

Iz nič sigurno ni kar naenkrat prišlo do problema. Ali v varnem načinu tudi pride do BSOD? Naj se za začetek najprej onemogoči opcija za avtomatski restart pri Bsod in sicer:Desni klik Moj računalnik->lastnosti->napredno_>zagon in obnovitev->lastnosti_>opcija zaženi znova samodejno naj se onemogoči

Ne, v safe mode lepo dela normalno.
V bistvu ga moram sam restartat, sam se ne restarta.

Duhec je 25. feb 2011 ob 17:15 izjavil:

+ še preveri, če se ventilator na grafiki zadovoljivo vrti in da ni zaprašen-posledica pregrevanje grafike (utripanje) in s tem morebiten black screen.

Mja največji problem je ker sploh nima ventilatorja sama grafična kartica :S Bom pa jutr mal spucal prah dol.

Hvala obema za pomoč!

Kakšen Bsod ti vrže ven? Priloži dmp datoteko.

Duhec je 27. feb 2011 ob 12:55 izjavil:

Potem pa štartaj varni zagon, poženi MSCONFIG (Start/Run in vpiši v vrstico) nato v zavihku STARTUP (Zagon) odstrani kljukice pred vrsticami katere programe ne poznaš. Za začetek lahko odstraniš kar vse, shraniš in restartaš sistem.
Poročaj, če je po normalnem zagonu še črn ekran.
Če še, potem spet v varni zagon in v servisih disejblaj neznane servise (še prej odkljukaj "Hide all MS Services", da ti sfiltrira vse ostale, ki še ostanejo. Posebno bodi pozoren na antivirusni servis in ga disejblaj, mogoče prav on povzroča v normalnem zagonu črn ekran.

Probal, + še enkrat pognal grafični driver in se mi je celo prikazal napis "welcome" z enim čudnim belim 3x4cm pravokotnikom ob robu

in pol celo se mi namizje prikaže z sivo win98 menijsko verstico(tam kjer je start) in kurzor miške, ozadje pa je blo črno in skos je štekal tako da nism mogu nč poklikat in na 5sec je utripal monitor

Bom probal še z antivirusom pregledat za vsak slučaj

gorenjc je 27. feb 2011 ob 11:33 izjavil:

Kakšen Bsod ti vrže ven? Priloži dmp datoteko.

Z veseljem, samo s katerim programom naj odprem dmp. file?

Sm rešu tole z symbols mal poguglov..

Evo dmp. file:


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Mar 21 21:41:49.328 2011 (UTC + 1:00)
System Uptime: 0 days 0:13:02.925
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
...
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {86cdea40, 86c64680, f78c7cb4, 1}

Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp!bBetweenScreens+15d )

Followup: MachineOwner
---------

2 dmp



Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031711-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Mar 17 15:57:49.015 2011 (UTC + 1:00)
System Uptime: 0 days 0:15:26.597
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {86595b88, 86aa8dc8, f78d3cb4, 1}

Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp!bBetweenScreens+15d )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 86595b88, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 86aa8dc8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f78d3cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------

ERROR - could not read driver name for bugcheck parameter 3


FAULTING_THREAD: 86595b88

FAULTING_IP:
nv4_disp!bBetweenScreens+15d
bd03bbbd ?? ???

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c1a6

MODULE_NAME: nv4_disp

FAULTING_MODULE: bd012000 nv4_disp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: msnmsgr.exe

LAST_CONTROL_TRANSFER: from f77aca67 to 8054097f

STACK_TEXT:
b7485158 f77aca67 f78d3b94 00000000 00000000 nt!RtlIpv6StringToAddressW+0xbc
b748544c 804fcfbf f78d3b40 b7485498 b748548c watchdog!WatchdogKernelApc+0x13b
b748549c 80500198 00000000 00000000 00000000 nt!KeWaitForMultipleObjects+0xe5
b74854dc bf8871da 00000000 00000000 00000000 nt!FsRtlFindFirstOverlappingExclusiveNode+0x8f
b74854f8 bd03bbbd 86bc8ba8 b748552c 0001e210 win32k!EngWaitForSingleObject+0x23
b748554c ba360008 b7485648 00000000 000005c0 nv4_disp!bBetweenScreens+0x15d
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7485568 00000000 f2427000 0001e210 e1b24010 0xba360008


STACK_COMMAND: .thread 0xffffffff86595b88 ; kb

FOLLOWUP_IP:
nv4_disp!bBetweenScreens+15d
bd03bbbd ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nv4_disp!bBetweenScreens+15d

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2011_01_08

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2011_01_08

Followup: MachineOwner
---------

3 dmp:


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021911-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Feb 19 11:10:07.468 2011 (UTC + 1:00)
System Uptime: 0 days 0:02:37.070
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
...
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {85f28ba0, 864a0838, f7a07cb4, 1}

Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp!NV4_DmaPushSendUnicast+31 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 85f28ba0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 864a0838, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a07cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------

ERROR - could not read driver name for bugcheck parameter 3


FAULTING_THREAD: 85f28ba0

FAULTING_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 482dff70

MODULE_NAME: nv4_disp

FAULTING_MODULE: bf9d3000 nv4_disp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logonui.exe

LAST_CONTROL_TRANSFER: from bf8871da to 805409e2

STACK_TEXT:
baf374e0 bf8871da 00000000 00000000 00000000 nt!RtlIpv6StringToAddressW+0x11f
baf374fc bf9f47a1 86485350 baf37524 00008000 win32k!EngWaitForSingleObject+0x23
baf37518 f7c0a07e 002320a0 ffffd8f0 ffffffff nv4_disp!NV4_DmaPushSendUnicast+0x31
WARNING: Frame IP not in any known module. Following frames may be wrong.
baf37530 00000000 00000000 00000000 e1983018 0xf7c0a07e


STACK_COMMAND: .thread 0xffffffff85f28ba0 ; kb

FOLLOWUP_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp!NV4_DmaPushSendUnicast+31

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

Followup: MachineOwner
---------

3 dmp:



Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021911-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Feb 19 11:10:07.468 2011 (UTC + 1:00)
System Uptime: 0 days 0:02:37.070
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
...
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {85f28ba0, 864a0838, f7a07cb4, 1}

Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp!NV4_DmaPushSendUnicast+31 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 85f28ba0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 864a0838, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a07cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------

ERROR - could not read driver name for bugcheck parameter 3


FAULTING_THREAD: 85f28ba0

FAULTING_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 482dff70

MODULE_NAME: nv4_disp

FAULTING_MODULE: bf9d3000 nv4_disp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logonui.exe

LAST_CONTROL_TRANSFER: from bf8871da to 805409e2

STACK_TEXT:
baf374e0 bf8871da 00000000 00000000 00000000 nt!RtlIpv6StringToAddressW+0x11f
baf374fc bf9f47a1 86485350 baf37524 00008000 win32k!EngWaitForSingleObject+0x23
baf37518 f7c0a07e 002320a0 ffffd8f0 ffffffff nv4_disp!NV4_DmaPushSendUnicast+0x31
WARNING: Frame IP not in any known module. Following frames may be wrong.
baf37530 00000000 00000000 00000000 e1983018 0xf7c0a07e


STACK_COMMAND: .thread 0xffffffff85f28ba0 ; kb

FOLLOWUP_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp!NV4_DmaPushSendUnicast+31

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

Followup: MachineOwner
---------

3 dmp:


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021911-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Feb 19 11:10:07.468 2011 (UTC + 1:00)
System Uptime: 0 days 0:02:37.070
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
...
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {85f28ba0, 864a0838, f7a07cb4, 1}

Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp!NV4_DmaPushSendUnicast+31 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 85f28ba0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 864a0838, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a07cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------

ERROR - could not read driver name for bugcheck parameter 3


FAULTING_THREAD: 85f28ba0

FAULTING_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 482dff70

MODULE_NAME: nv4_disp

FAULTING_MODULE: bf9d3000 nv4_disp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logonui.exe

LAST_CONTROL_TRANSFER: from bf8871da to 805409e2

STACK_TEXT:
baf374e0 bf8871da 00000000 00000000 00000000 nt!RtlIpv6StringToAddressW+0x11f
baf374fc bf9f47a1 86485350 baf37524 00008000 win32k!EngWaitForSingleObject+0x23
baf37518 f7c0a07e 002320a0 ffffd8f0 ffffffff nv4_disp!NV4_DmaPushSendUnicast+0x31
WARNING: Frame IP not in any known module. Following frames may be wrong.
baf37530 00000000 00000000 00000000 e1983018 0xf7c0a07e


STACK_COMMAND: .thread 0xffffffff85f28ba0 ; kb

FOLLOWUP_IP:
nv4_disp!NV4_DmaPushSendUnicast+31
bf9f47a1 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp!NV4_DmaPushSendUnicast+31

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2008_05_16

Followup: MachineOwner
---------

Pa pr prvem dmp sem pozabu dat še analyz

@amigo no1 aha, bom sprobal, sicer pa sem že namestu gor en stari driver pa ni blo nč bolš, bom še to sprobov še enkrat..

Tnx