Bluescreen - Treiber vermutet | Hidclass.sys & ntkrnlmp.exe

Diskutiere Bluescreen - Treiber vermutet | Hidclass.sys & ntkrnlmp.exe im Windows 7 Bluescreens Forum im Bereich Windows 7; In letzter Zeit bekomme ich bei jedem Start Bluescreen's, nach dem 4 oder 5. Start gelingt dann auch endlich der Start. Vermutet habe ich die...

  1. #1 Sanogo24, 10.09.2011
    Sanogo24

    Sanogo24 Neuer Benutzer

    Dabei seit:
    11.09.2010
    Beiträge:
    3
    Zustimmungen:
    0
    Version:
    Home Premium
    System:
    64bit
    In letzter Zeit bekomme ich bei jedem Start Bluescreen's, nach dem 4 oder 5. Start gelingt dann auch endlich der Start.

    Vermutet habe ich die NVIDIA-Grafikkarten-Treiber, welche ich auch komplett deinstalliert habe (Inklusive Driver-Cleaner, CCleaner und De-bzw. Neuinstallation der Grafikkarte). Dies hat allerdings nicht viel geholfen.
    Jetzt hoffe ich, dass ihr mir helfen könnt.

    Vielleicht noch ein kleiner Hinweiß, sowohl die Festplattenüberprüfung als auch der Memtest haben keinen Fehler festgestellt

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\091011-23415-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at start of path element
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03e0f000 PsLoadedModuleList = 0xfffff800`04054670
    Debug session time: Sat Sep 10 15:25:31.351 2011 (UTC + 2:00)
    System Uptime: 0 days 0:05:50.005
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {60001, 2, 1, fffff80003e9372c}
    
    Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+17c )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000060001, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003e9372c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800040be100
     0000000000060001 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`03e9372c 4c8938          mov     qword ptr [rax],r15
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  wmplayer.exe
    
    TRAP_FRAME:  fffff8800d79d870 -- (.trap 0xfffff8800d79d870)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000060001 rbx=0000000000000000 rcx=fffffa80076b7bc8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003e9372c rsp=fffff8800d79da00 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff880009e9180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeWaitForSingleObject+0x17c:
    fffff800`03e9372c 4c8938          mov     qword ptr [rax],r15 ds:7b20:00000000`00060001=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003e8b1e9 to fffff80003e8bc40
    
    STACK_TEXT:  
    fffff880`0d79d728 fffff800`03e8b1e9 : 00000000`0000000a 00000000`00060001 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0d79d730 fffff800`03e89e60 : 00000000`00000000 fffff880`0d79d940 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0d79d870 fffff800`03e9372c : fffffa80`08eca770 fffff800`04194950 fffff8a0`0017e010 fffffa80`0712ace0 : nt!KiPageFault+0x260
    fffff880`0d79da00 fffff800`03e5e61e : 00000000`00100000 fffff800`00000022 fffff880`0d79db00 fffff800`04180300 : nt!KeWaitForSingleObject+0x17c
    fffff880`0d79daa0 fffff800`03e9e1c5 : fffffa80`08eca770 fffff880`0100176f 00000001`00000001 00000000`00000001 : nt!KiAcquireFastMutex+0x4e
    fffff880`0d79dae0 fffff880`012aabbf : 00000000`00000000 fffff880`00100000 fffffa80`0780f500 fffff880`00de3110 : nt!ExAcquireFastMutex+0x45
    fffff880`0d79db10 fffff880`012b00ec : fffffa80`0712ace0 fffff8a0`0017e010 00000000`00000000 fffffa80`0b302368 : Ntfs!NtfsCreateScb+0x4f
    fffff880`0d79dbd0 fffff880`0129efe5 : fffffa80`0712ace0 fffffa80`0b302368 fffffa80`07859180 fffff8a0`0017e450 : Ntfs!NtfsOpenAttribute+0xac
    fffff880`0d79dce0 fffff880`0129ad9f : fffff880`0d79e4a0 00000000`c0000022 fffff880`0d79e4a0 00000000`00000000 : Ntfs!NtfsOpenExistingAttr+0x145
    fffff880`0d79dda0 fffff880`0129e09f : fffffa80`0712ace0 fffffa80`0b302010 fffff8a0`0017e450 fffff880`00000000 : Ntfs!NtfsOpenAttributeInExistingFile+0x50f
    fffff880`0d79df30 fffff880`012ae166 : fffffa80`0712ace0 fffffa80`0b302010 fffff8a0`0017e450 00000000`00000001 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
    fffff880`0d79e020 fffff880`012ab911 : fffffa80`0712ace0 fffffa80`0b302010 fffff880`0d79e1f0 fffff880`0d79e240 : Ntfs!NtfsFindStartingNode+0x5e6
    fffff880`0d79e0f0 fffff880`01214a3d : fffffa80`0712ace0 fffffa80`0b302010 fffff880`0d79e4a0 fffffa80`07e80e00 : Ntfs!NtfsCommonCreate+0x3e1
    fffff880`0d79e2d0 fffff800`03e98618 : fffff880`0d79e410 00000000`00000000 fffff880`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`0d79e300 fffff880`012151bf : fffff880`01214a20 fffff880`01214020 fffff880`0d79e400 fffff880`012b5f00 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0d79e3e0 fffff880`012ae99c : 00000000`00000000 00000000`00000000 fffff880`0d79e640 fffffa80`0b302010 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
    fffff880`0d79e440 fffff880`01002bcf : fffffa80`07859030 fffffa80`0b302010 00000000`00000000 fffffa80`076b5de0 : Ntfs!NtfsFsdCreate+0x1ac
    fffff880`0d79e5f0 fffff880`010222b9 : fffffa80`0b302010 fffffa80`0780d800 fffffa80`0b302000 fffffa80`076b5de0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0d79e680 fffff800`04189f95 : 00000000`00000005 fffffa80`08eca928 fffffa80`0749fb10 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`0d79e730 fffff800`04186838 : fffffa80`0768ba50 fffff800`00000000 fffffa80`08eca770 00000000`00000001 : nt!IopParseDevice+0x5a5
    fffff880`0d79e8c0 fffff800`04187a56 : 00000000`00000000 fffffa80`08eca770 fffff8a0`03010380 fffffa80`06726080 : nt!ObpLookupObjectName+0x588
    fffff880`0d79e9b0 fffff800`0418935c : fffff8a0`0469c8e0 00000000`00000000 fffff880`0d79ea01 00000000`00000000 : nt!ObOpenObjectByName+0x306
    fffff880`0d79ea80 fffff800`04174be4 : 00000000`026ae368 00000000`00100000 00000000`026aebc0 00000000`026ae308 : nt!IopCreateFile+0x2bc
    fffff880`0d79eb20 fffff800`03e8aed3 : fffffa80`0a71f580 00000000`026ae2f8 00000000`00000002 00000000`004033a0 : nt!NtOpenFile+0x58
    fffff880`0d79ebb0 00000000`77bc164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`026ae2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bc164a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`03e9372c 4c8938          mov     qword ptr [rax],r15
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KeWaitForSingleObject+17c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    
    BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    
    Followup: MachineOwner
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\091011-31028-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at start of path element
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServ
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03e0f000 PsLoadedModuleList = 0xfffff800`04054670
    Debug session time: Sat Sep 10 20:32:37.029 2011 (UTC + 2:00)
    System Uptime: 0 days 0:00:32.714
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......
    Loading User Symbols
    Loading unloaded module list
    ..
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {220, fffff88008bdd710, fffff9800dbdecf0, fffffa80093b55b0}
    
    Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
    	This IRP should either have been completed earlier or should have been passed
    	down.
    Arg2: fffff88008bdd710, The address in the driver's code where the error was detected.
    Arg3: fffff9800dbdecf0, IRP address.
    Arg4: fffffa80093b55b0, ProviderId.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_220
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220
    
    FAULTING_IP: 
    HIDCLASS!HidpMajorHandler+0
    fffff880`08bdd710 48895c2410      mov     qword ptr [rsp+10h],rbx
    
    FOLLOWUP_IP: 
    HIDCLASS!HidpMajorHandler+0
    fffff880`08bdd710 48895c2410      mov     qword ptr [rsp+10h],rbx
    
    IRP_ADDRESS:  fffff9800dbdecf0
    
    DEVICE_OBJECT: fffffa80094559a0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LOCK_ADDRESS:  fffff8000408ab80 -- (!locks fffff8000408ab80)
    
    Resource @ nt!PiEngineLock (0xfffff8000408ab80)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0xfffff8000408ab80
    	Thread Count  : 0
    	Thread address: 0x0000000000000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from fffff800043153dc to fffff80003e8bc40
    
    STACK_TEXT:  
    fffff880`03ba10a8 fffff800`043153dc : 00000000`000000c9 00000000`00000220 fffff880`08bdd710 fffff980`0dbdecf0 : nt!KeBugCheckEx
    fffff880`03ba10b0 fffff800`0431f47a : fffff800`043139f0 fffff880`08bdd710 fffff980`0dbdecf0 fffffa80`093b55b0 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`03ba10f0 fffff800`043200ff : 00000000`00000220 fffffa80`093b55b0 fffff980`0dbdecf0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`03ba1140 fffff800`043256a7 : fffff980`0dbdef28 fffff880`08bdd710 00000000`00000000 00000000`00000000 : nt!VfErrorReport10+0x6f
    fffff880`03ba1220 fffff800`0431504e : fffffa80`091c5330 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
    fffff880`03ba1250 fffff800`04321b2d : fffffa80`0904de10 fffffa80`091c5010 fffff980`0dbdecf0 fffff980`0dbdecf0 : nt!VfMajorVerifyIrpStackUpward+0x6e
    fffff880`03ba1290 fffff800`0433350d : fffff980`0dbdef28 fffff880`03ba1480 00000000`c0000010 fffff980`0dbdef28 : nt!IovpCompleteRequest2+0xad
    fffff880`03ba1300 fffff800`03e8f021 : fffff980`0dbdef2b 00000000`00000000 00000000`000000ff fffff800`04316eea : nt!IovpLocalCompletionRoutine+0x9d
    fffff880`03ba1360 fffff800`0432b19f : fffff980`0dbdecf0 fffff880`08be7400 fffffa80`09455a00 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff880`03ba1450 fffff800`03e71876 : fffff880`00000013 fffff880`03ba1578 fffff980`0dbdef28 fffffa80`09455af0 : nt!IovCompleteRequest+0x19f
    fffff880`03ba1520 fffff880`08bdda0f : 00000000`00000000 fffffa80`09455af0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
    fffff880`03ba1550 fffff880`08bdd7fb : 00000000`00000000 fffffa80`09455af0 fffff980`0dbdecf0 fffff880`03ba1600 : HIDCLASS!HidpIrpMajorDefault+0x8b
    fffff880`03ba1590 fffff800`04331c16 : fffff980`00000002 fffff980`0dbdecf0 00000000`00000002 fffff800`0432d37e : HIDCLASS!HidpMajorHandler+0xeb
    fffff880`03ba1600 fffff800`04330c42 : fffff980`0dbdef70 00000000`00000002 fffffa80`09449f50 fffffa80`08ddbf40 : nt!IovCallDriver+0x566
    fffff880`03ba1660 fffff800`04331c16 : fffff980`0dbdecf0 00000000`00000002 fffffa80`09449e00 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
    fffff880`03ba1690 fffff800`04330d58 : fffff980`0dbdecf0 fffffa80`09449e00 00000000`00000000 fffffa80`09350030 : nt!IovCallDriver+0x566
    fffff880`03ba16f0 fffff800`04330e42 : fffffa80`093b55b0 fffffa80`0675eb80 fffffa80`093b55b0 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
    fffff880`03ba1760 fffff800`0431dfaf : fffffa80`09420ba0 00000000`000007ff fffff800`03fc55b8 fffff800`04221899 : nt!VfWmiTestStartedPdoStack+0x72
    fffff880`03ba1800 fffff800`03f389d2 : fffffa80`09420ba0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
    fffff880`03ba1830 fffff800`04275e5c : fffffa80`09420ba0 fffffa80`0675eb80 00000000`00000001 01535242`0000000c : nt!PpvUtilTestStartedPdoStack+0x12
    fffff880`03ba1860 fffff800`04277a54 : fffffa80`09420ba0 fffffa80`09420ba0 fffffa80`0675eb80 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
    fffff880`03ba1950 fffff800`04277f3c : fffff800`04088500 00000000`00000000 00000000`00000001 fffff800`040f5814 : nt!PipProcessDevNodeTree+0x264
    fffff880`03ba1bc0 fffff800`03f888c2 : 00000001`00000003 fffff800`0402c2b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
    fffff880`03ba1c10 fffff800`03e96001 : fffff800`03f885c0 fffff800`04182901 fffffa80`06745600 fffffa80`06745680 : nt!PnpDeviceActionWorker+0x302
    fffff880`03ba1cb0 fffff800`04126fee : 00000000`00000000 fffffa80`06745680 00000000`00000080 fffffa80`066c0070 : nt!ExpWorkerThread+0x111
    fffff880`03ba1d40 fffff800`03e7d5e6 : fffff880`03964180 fffffa80`06745680 fffff880`0396efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03ba1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: HIDCLASS
    
    IMAGE_NAME:  HIDCLASS.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665
    
    FAILURE_BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0
    
    BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0
    
    Followup: MachineOwner
    LG
    Sanogo24
     
  2. #2 Sanogo24, 12.09.2011
    Sanogo24

    Sanogo24 Neuer Benutzer

    Dabei seit:
    11.09.2010
    Beiträge:
    3
    Zustimmungen:
    0
    Version:
    Home Premium
    System:
    64bit
    Grade festgestellt: Letzterer Bluescreen tritt nur bei aktiviertem Driver Verifierer auf, allerdings startet dann auch der PC nichtmehr (bzw. nur im abgesichertem Modus).
     
Thema: Bluescreen - Treiber vermutet | Hidclass.sys & ntkrnlmp.exe
Besucher kamen mit folgenden Suchen
  1. Hidclass.sys

    ,
  2. hidclass.sys bluescreen

    ,
  3. blue screen stop:0x0000007e hidclass.sys

    ,
  4. bluescreen hidclass.sys,
  5. ntkrnlmp.exe,
  6. ntkrnlmp.exe treiber,
  7. hidclass.sys windows 7,
  8. Bluescreen - Treiber vermutet,
  9. hidclass.sys fehler,
  10. bsod hidclass.sys,
  11. hidclass.sys,
  12. Probably caused by : ntkrnlmp.exe,
  13. ntkrnlmp.exe bluescreen,
  14. DRIVER_VERIFIER_IOMANAGER_VIOLATION nvlddmkm.sys,
  15. blue screen hidclass.sys,
  16. failure_bucket_id: x64_0xa_nt!kewaitforsingleobject 17c,
  17. hidclass.sys bluescreen windows7,
  18. hidclass.sys bluescreen win7,
  19. Windows 7 Bluescreen HIDCLASS.SYS,
  20. hidclass:sys,
  21. hidclass.sys bluescreen windows 7,
  22. hidclass.sys stop 0x000007e,
  23. bluescreen hidclass sys,
  24. hidclass.sys win7 system32,
  25. hid class treiber
Die Seite wird geladen...

Bluescreen - Treiber vermutet | Hidclass.sys & ntkrnlmp.exe - Ähnliche Themen

  1. Probleme: Bluescreen, Update, Treiber, Internet

    Probleme: Bluescreen, Update, Treiber, Internet: Wurde gebeten ein Laptop (Acer Aspire V3-772G) mit Windows 7 Home Premium auf Vordermann zu bringen, bei welchem unzählige Fehler auftraten. Bevor...
  2. Neuer PC - Probs mit Treibern und Hardwarebeschleunigung

    Neuer PC - Probs mit Treibern und Hardwarebeschleunigung: Das Motherboard meines "alten" Rechners hat nach 5 Jahren den Geist aufgegeben und so habe ich mir kurzentschlossen bei Conrad.at einen neuen...
  3. Auswegloser Bluescreen --> Treiber über Live CD deaktivieren?

    Auswegloser Bluescreen --> Treiber über Live CD deaktivieren?: Liebe Community, bisher hatte ich eigentlich immer lösbare Probleme, doch seit heute habe ich einen Bluescreen, der nicht verschwindet :mad:...
  4. BSOD Bluescreen bei Installation des Treibers (NVIDIA) für GeForce GTX 750 Ti Win 7

    BSOD Bluescreen bei Installation des Treibers (NVIDIA) für GeForce GTX 750 Ti Win 7: Hi, ich habe mein Windows 7 64-bit gerade frisch installiert, alle Windows-Updates und der neuste NVIDIA-Treiber (344.75) sind installiert....
  5. Windows 7 Bluescreen bei letzten Schritten der Installation

    Windows 7 Bluescreen bei letzten Schritten der Installation: Hallo liebe Forumnutzer ich ersuche euren Rat. Ich hab mir ein neues Mainboard, neue CPU, neuen RAM und eine neue HDD gekauft so das mein...