Ergebnis 1 bis 6 von 6

Thema: Ein haufen Bsod - sogar beim installieren von windows.

  1. #1

    Standard Ein haufen Bsod - sogar beim installieren von windows.

    Guten Tag!
    ich dachte ich versuche es auch mal hier.

    Also.... ich habe einen neuen Pc gebaut, anfangs lief er gut, dann fingen die Bsod an - bis er nicht mehr boote wollte.
    Also eingeschickt, teile wurden ausgetauscht...

    und jetzt geht es wieder los. Ich bin an dem Punkt ich kann auf 2 unterschiedlichen Platten keine windows installation durchführen.

    Hier die daten

    specs
    AMD Ryzen 5 3600 6x 3.60GHz So.AM4 BOX



    550 Watt be quiet! Straight Power 11 Modular 80+ Gold


    8GB MSI GeForce RTX 2060 Super Ventus GP DDR6 PCI-E

    16GB Corsair Vengeance LPX LP schwarz DDR4-3200 DIMM CL16 Dual Kit

    MSI MAG X570 Tomahawk WIFI, So.AM4 (7C84-001R)


    genau wie vor der reperatur macht vor allem ntoskrnl.exe probleme oder Treiber - selbst beim installieren von Windows selbst?

  2. #2
    Moderator Avatar von Black & White
    Registriert seit
    18.06.2009
    Beiträge
    39.116

    Standard

    bios auf standard oder xmpo eingestellt? ram mal untertaktet? minimalkonfig probiert? außerhalb vom case? die infos geben leider zu wenig her bislang...
    Mit freundlichen Grüßen
    Ihr Moderatorenteam

    signaturbild mod - Ein haufen Bsod - sogar beim installieren von windows.
    Kontakt: Kundenbetreuung | Logistik | Reklamation | Technik | Service Level Gold | Infocenter | Highlights

    Sent from my fingers using my brain, both arms and my keyboard und NEIN, ich will nicht wissen, was irgendwer zum posten nutzt! solche msg darf man gern deaktivieren, danke!
    ...und nein, ich bin kein Mitarbeiter der Mindfactory AG!

  3. #3
    Private
    Themenstarter

    Registriert seit
    23.10.2020
    Beiträge
    7

    Standard

    ich habe xmp an und ausgeschalten. Leider kenne ich mich nicht soo gut aus mit bios einstellungen - ich habe es aber geupdatet und auf uefi gestellt, sonst ist alles standart-einstellungen.

    Momentan sind nur 2 ramriegel, die graka, 1 hdd, cpu und eben der cpu lüfter angeschlossen - im case, das steht aber offen da. (will die teile einfach nicht auf den boden legen)

    wie untertacktet man ram?

    edit: ich erstelle gerade ein weiteres windows-installationsmedium, da ich mir nich weiter zu helfen weiß

  4. #4

    Standard

    Du kannst mal whocrashed installieren und schauen ob das was ausspuckt! Resplendence Software - Free Downloads
    Das Universum und die Dummheit der Menschheit sind unendlich ! Beim Universum bin ich mir jedoch nicht ganz sicher ! (Albert Einstein)
    "Ich selbst habe keine GTX970 aber falls NVidia die Rücknahme anbietet, würde ich sie zurückschicken" (PCGH-Umfrage)
    Danke für den Beweis !

    Daddel-Kiste
    Gehäuse: Phanteks Enthoo Primo Special Edition BO / NT: Seasonic Focus Platinum 550Watt
    MB: Gigabyte X570 Aorus Ultra / CPU: AMD Ryzen 7 3700X / RAM: 4x8GB G.Skill Flare X 3200 CL14
    Graka: EVGA GTX 1080 FTW / CPU-Kühler: BeQuiet Dark Rock Pro 3
    SSD: Crucial MX 500 1TB / Samsung Evo 840 250GB / 2xWD Blue 4TB
    Sound: Creative Soundblaster X-Fi Titanium HD / Lautsprecher: Logitech Z2300 2.1 THX

  5. #5
    Private
    Themenstarter

    Registriert seit
    23.10.2020
    Beiträge
    7

    Standard

    Habe ich bei der einen festplatte die halbwegs läuft "ntoskrl.exe" das ist ein treiber fehler der sich nicht genauer bestimmen lässt.

    lass mich aber versuchen das ganze zu kopieren

  6. #6
    Private
    Themenstarter

    Registriert seit
    23.10.2020
    Beiträge
    7

    Standard

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\Windows
    C:\Windows\Minidump

    On Fri 23.10.2020 12:29:31 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\102320-21781-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 23.10.2020 12:29:31 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8279)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 23.10.2020 04:35:07 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\102320-17796-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
    Bugcheck code: 0xA (0x9895A8, 0xFF, 0x76, 0xFFFFF80456936C9B)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 23.10.2020 04:20:32 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\102320-17000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000BD117FC, 0xFFFFE580942B2920, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 23.10.2020 04:02:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\102320-20765-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
    Bugcheck code: 0xD1 (0xFFFFCA0BDC8B1370, 0xFF, 0xCC, 0xFFFFCA0BDC8B1370)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 23.10.2020 02:54:39 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\102320-18062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
    Bugcheck code: 0xA (0x0, 0xFF, 0xB6, 0xFFFFF80052C8778D)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Aktive Benutzer

Aktive Benutzer

Aktive Benutzer in diesem Thema: 1 (Registrierte Benutzer: 0, Gäste: 1)

Ähnliche Themen

  1. Antworten: 4
    Letzter Beitrag: 23.10.2020, 18:15
  2. BSOD Windows startet nicht
    Von Averris im Forum Probleme mit dem Rechner?
    Antworten: 4
    Letzter Beitrag: 13.02.2019, 19:59
  3. Neuer PC beim Spielen RSOD's und BSOD's (X99)
    Von WhiteTurtle im Forum Probleme mit dem Rechner?
    Antworten: 14
    Letzter Beitrag: 29.09.2014, 17:24
  4. Bekomme Fehler beim installieren von Windows auf einer SSD
    Von deaddedevil2299 im Forum Festplatten, SSDs & Laufwerke
    Antworten: 8
    Letzter Beitrag: 06.05.2014, 09:51
  5. Antworten: 17
    Letzter Beitrag: 07.11.2005, 21:36

Stichworte

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •