739 Benutzer online
21. November 2024, 22:01:12

Windows Community



Zum Thema HDAudio.sys und portcls.sys TREIBER PROBLEM bei Systemstart - Hallo!Ich hab Probleme mit meinem Notebook Samsung M55 Breetoo mit VISTA Ulitmate. Beschreibung:Der Notebook ist für mehrere Stunden aus. Wenn ich ihn einschalt... im Bereich PC Hardware & Treiber
Autor Thema:

HDAudio.sys und portcls.sys TREIBER PROBLEM bei Systemstart

 (Antworten: 0, Gelesen 11742 mal)

  • Windows 1.0
  • Beiträge: 2
HDAudio.sys und portcls.sys TREIBER PROBLEM bei Systemstart
« am: 24. Februar 2008, 12:37:20 »
Hallo!
Ich hab Probleme mit meinem Notebook Samsung M55 Breetoo mit VISTA Ulitmate.

Beschreibung:
Der Notebook ist für mehrere Stunden aus. Wenn ich ihn einschalte muss ich 2-3mal reseten bis Windows hochfährt, dann läuft es einwandfrei. Der High Definition Audio Treiber spuckt keinen Sound aus. (Bei Installation des Hersteller Treibers ist das Problem weiterhin vorhanden). Ich hab alle Hardware inkl. Memory auf fehler getestet, Treiber deaktiviert etc. da üblich Programm (bin fortgeschrittener User)

Ich hab ein Debug gemacht vom Crash Dump (WinDBG) und bräuchte mal eure Hilfe bei der Lösung, meines erachtens ist es der treiber hdaudio.sys, der die Probleme verursacht (Bluescreen) und der Treiber portcls.sys (Miniport). Es könnte aber auch sein das die beiden zusammenhängen.

Hier der vollständige Crash Dump von WinDBG:

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


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

Symbol search path is: C:\Users\Administrator\Desktop\symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ad0
Debug session time: Sun Feb 24 11:27:44.407 2008 (GMT+1)
System Uptime: 0 days 0:00:09.126
Loading Kernel Symbols
.............................................................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81dee4c1, 829223d4, 0}

Unable to load image \SystemRoot\system32\drivers\HdAudio.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HdAudio.sys
*** ERROR: Module load completed but symbols could not be loaded for HdAudio.sys


Probably caused by : portcls.sys ( portcls!CRegistryKey::Init+bb )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81dee4c1, The address that the exception occurred at
Arg3: 829223d4, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
nt!CmpAllocateDelayItem+8f
81dee4c1 897804          mov     dword ptr [eax+4],edi

TRAP_FRAME:  829223d4 -- (.trap 0xffffffff829223d4)
ErrCode = 00000002
eax=50535000 ebx=8ce2add0 ecx=00000000 edx=00000001 esi=81d25ea0 edi=81d25ec0
eip=81dee4c1 esp=82922448 ebp=8292246c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210202
nt!CmpAllocateDelayItem+0x8f:
81dee4c1 897804          mov     dword ptr [eax+4],edi ds:0023:50535004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 81dd5de4 to 81dee4c1

STACK_TEXT: 
82922450 81dd5de4 00000000 83423368 83423368 nt!CmpAllocateDelayItem+0x8f
8292246c 81dd5b72 00000000 3b9aca07 000007ff nt!CmpAddToDelayedClose+0x28
82922488 81decc05 83423368 00000000 83423368 nt!CmpDereferenceKeyControlBlockWithLock+0x58
829224ac 81dc7f08 83423368 85ffb98c 8340fd10 nt!CmpDereferenceKeyControlBlock+0x8d
82922600 81ddae7d 8340fd28 8528a040 85ffb8e8 nt!CmpParseKey+0xbae
82922690 81dccade 00000000 829226e8 00000240 nt!ObpLookupObjectName+0x615
829226f0 81e276fb 82922878 8528a040 00000000 nt!ObOpenObjectByName+0x13c
829227bc 81e258f0 829228a8 00020019 82922878 nt!CmOpenKey+0x1b1
829227e0 81c460fa 829228a8 00020019 82922878 nt!NtOpenKey+0x39
829227e0 81c44555 829228a8 00020019 82922878 nt!KiFastCallEntry+0x12a
82922864 81da058a 829228a8 00020019 82922878 nt!ZwOpenKey+0x11
82922890 81da40d7 81ef6f08 00020019 00000000 nt!IopOpenRegistryKeyEx+0x36
829228ac 81d82cc4 882bf0d8 829228ec 00020019 nt!PnpDeviceObjectToDeviceInstance+0x1c
829229cc 81d82b15 882bf0d8 00000002 000f003f nt!IopOpenOrCreateDeviceRegistryKey+0x139
829229e8 8efa786f 882bf0d8 00000002 000f003f nt!IoOpenDeviceRegistryKey+0x18
82922a0c 8efa80a6 8374c1f8 00000002 000f003f portcls!CRegistryKey::Init+0xbb
82922a40 8efd7a59 8374c1f8 00000000 00000002 portcls!PcNewRegistryKey+0x69
WARNING: Stack unwind information not available. Following frames may be wrong.
82922aa8 8efe3f24 8eff33e2 82922bb4 82922ae0 HdAudio+0x16a59
82922c80 8efe4841 87223048 8efd8d92 882e30d0 HdAudio+0x22f24
82922cd8 8efe6787 00000000 883080e0 883080e0 HdAudio+0x23841
82922cf4 8efa76ad 882e30d0 883080e0 837e8840 HdAudio+0x25787
82922d1c 8efa764a 00000000 00000000 882e30d0 portcls!PnpStartDevice+0x4f
82922d30 81e18fb0 882e30d0 837dcf58 8528e2d8 portcls!EnqueuedIoWorkItemCallback+0x20
82922d44 81c6b7aa 88305210 00000000 8528e2d8 nt!IopProcessWorkItem+0x23
82922d7c 81dafbad 88305210 82929680 00000000 nt!ExpWorkerThread+0xfd
82922dc0 81c9a346 81c6b6ad 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
portcls!CRegistryKey::Init+bb
8efa786f ebc1            jmp     portcls!CRegistryKey::Init+0x7e (8efa7832)

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  portcls!CRegistryKey::Init+bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4549b266

FAILURE_BUCKET_ID:  0x8E_portcls!CRegistryKey::Init+bb

BUCKET_ID:  0x8E_portcls!CRegistryKey::Init+bb

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

0: kd> lmvm portcls
start    end        module name
8ef94000 8efc1000   portcls    (pdb symbols)          C:\Users\Administrator\Desktop\symbols\portcls.pdb\D6CCD475C6E54324A85C6E44C245E0142\portcls.pdb
    Loaded symbol image file: portcls.sys
    Mapped memory image file: C:\Users\Administrator\Desktop\symbols\portcls.sys\4549B2662d000\portcls.sys
    Image path: \SystemRoot\system32\drivers\portcls.sys
    Image name: portcls.sys
    Timestamp:        Thu Nov 02 09:55:02 2006 (4549B266)
    CheckSum:         00034F0F
    ImageSize:        0002D000
    File version:     6.0.6000.16386
    Product version:  6.0.6000.16386
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.9 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     portcls.sys
    OriginalFilename: portcls.sys
    ProductVersion:   6.0.6000.16386
    FileVersion:      6.0.6000.16386 (vista_rtm.061101-2205)
    FileDescription:  Port Class (Class Driver for Port/Miniport Devices)
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
0: kd> .trap 0xffffffff829223d4
ErrCode = 00000002
eax=50535000 ebx=8ce2add0 ecx=00000000 edx=00000001 esi=81d25ea0 edi=81d25ec0
eip=81dee4c1 esp=82922448 ebp=8292246c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210202
nt!CmpAllocateDelayItem+0x8f:
81dee4c1 897804          mov     dword ptr [eax+4],edi ds:0023:50535004=????????
------------------------------------------------------------------------------------------------------------------------------------------------------------------

Der HOTFIX kb888111 funktioniert bei mir nicht. Es wäre nett wenn mir jemand von euch helfen könnte. Ich bin von der googlei ziemlich genervt und hab nix brauchbares gefunden!

Vielen Dank




(auto)bot

(auto)admin

vista aero windows pro update sound probleme error download neustart
treiber version bit driver problem treiberinstallation installation for installiert sys