BSOD pri Remote Desktopu v Win 2003 Server R2 Enterprise SP2

Pozdravljeni

Imam problem z napako 0x0000008e. Napaka nastane samo kadar se odjavimo Log off iz remote desktopa, PC dela še 30 sekund potem pa vrže BSOD in psyhical memory dump do 100, nato pa frizne in je potreben reset. PC ni defekten, do prejšnega tedna sem uporabljal XPje brez težav. Računalnik je bil kupjen novembra 06 in je delal perfektno odkar so bili XPji. Tudi zdaj v serverju dela normalno brez felerjev. PC lahko mantram pa nebo šteknil. Edino kar je problem in nevem zakaj se to pojavi, kadar se neka oseba tudi administrator preko remote desktopa od logira. Delam pa v Administrator računu, ta račun je tudi skoz prijavlen.

Error code 1000008e, parameter1 c0000047, parameter2 8082ba92, parameter3 8089a03c, parameter4 00000000.

Konfiguracija je: Core2 Duo 6600 nenavit, Asus P5B -1604, 2 GB ram patriot 667mhz CL5 nenaviti, LC 550w, wd3200ks in wd2500ks in asus 7600 gt silent 2. PC se ne pregreva, rami so rezhibni, ni navit.

OS: Windows Server 2003 R2 Enterprise Edition Service Pack 2, Tazadnji driverji - vse je updatano.

Vse nastavitve sem že pregledal. Žal nisem še nič konkretnega najdel. Je treba slučajno server naštelat v Manage server kot remote access / VPN server???? trenutno sta samo File Server in Print Server na YES.

Ne. Ni to to. Je isto, vrže BSOD. Kaj pa je Terminal Server? Piše samo 120 dni licence.

Nevem, nisem več tak pameten. In to naj bi bila stabilnost win 2003. Je še slabše kot XP. Upam da bo kdo to pogruntal kaj je narobe. Windowsi delajo po performencih dosti boljše kot XP, zato bi jih rad tudi obdržal. Drugač bom moral it nazaj na XP samo zaradi remote desktopa :(

Hm, je možno da nesme bit Administrator račun skoz vkloplen, kadar delajo drugi gor??? Zdaj trenutno ni nobenega konektanega, in sem se preko omrežja konektal na administrator račun, sem nekaj za hec naredil, par oken odprl in zbrisal koš. Pol sem se pa odlogiral in sem počakal 5 min preden sem se spet prijavil za računalnik na račun Administrator in mi ni vrglo BSODa. Je možno da je treba malo počakat, ker prej ko sem testiral nevem če je 15 sek minlo.

Ne, nimam nobene od teh zvočnih kart. BSOD je metal ven ko je bil čist sveže naložen, ko še ni bilo nobenih programčkov. Res pa je da sem zdaj dosti programov inštaliral, ampak vsi delajo BP.

Čakte zdaj, to bom prišel do dna. Tak dolgo bom brozil, dokler se nebo zrušlo. Ko se enkrat zraven vsedem potem vse zrihtam

Samo to:

System Error

Error code 1000008e, parameter1 c0000047, parameter2 8082ba92, parameter3 8089a03c, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.a....

A imaš slučajno kakšen analogen softverski modem? Na enem strežniku (sicer Win2000) so bili isti problemi, da se je kišta sesula po odjavi (helper za modem ni deloval pravilno, če se je zagnal več kot enkrat - podobne težave lahko povzročijo tudi drugi programi, ki tečejo v sistemskem pladnju - desno spodaj, zraven ure)

Bom takoj probal, takoj naslednjič ko mi vrže BSOD. Trenutno ga še ni vrglo, ker vsakič počakam najmanj 5 min preden se vpišem nazaj.

EVO , spet je vrgel BSOD, tokrat mede delom v remote desktopom. Tokrat je pa pod 0x0000008e vrglo še nv4_disp.dll, mislim da so to nvidia display driverji krivi, trenutno imam 162.18 WHQL. Probam dat gor 162.50 za quadro serijo???? Kaj mislite???

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


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the - y < symbol_path > argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Tue Aug 14 11:47:28.250 2007 (GMT+2)
System Uptime: 0 days 1:53:32.974
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image \SystemRoot\System32\nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfa391c0, b98b4674, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nv4_disp.dll ( nv4_disp+531c0 )

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