Fehlermeldung Minecraft: "GLFW error 65542 : WGL: The driver does not appear to support...

Ich bin mittlerweile echt verzweifelt, habe tausendmal gegoogelt und tutorials angeschaut nichts hat geholfen, vllt weiß ja jemand weiter oder hatte das schonmal.

Das sind meine technischen Daten:

Asus Laptop mit 2 Grafikkarten (Interne AMD Raedon und Nvidia GTX 1050, ich will die 2. nutzen)

Windows 11 (habs auch mit Windows 10 vorher versucht), 64-Bit

Das hab ich bereits versucht:

• minecraft deinstalliert und neu heruntergeladen
• java neuinstalliert
• neueste treiberversion installiert
• ältere teriberversion installiert
• opengl datei in bin ordner von java reingetan
• windows updates
• die AMD Raedon im System ausgestellt

Es hat nichts gebracht, eine Vermutung habe ich noch, dass es evtll am minecraft launcher liegen könnte, da irgendwann vor dem update des launchers es mal ging.

Wäre echt nett wenn mir jmd weiterhelfen könnte

:)

 

AW: [Sammelthread] SSD Kaufberatung, Troubleshooting und Begriffserklärung

corsair ruft die force3 zurück!

Corsair Force Series 3 SSD Issue Resolution: Drive Return Procedure - The Corsair Support Forums

Over the past several days, we have analyzed issues associated with the stability of our recently released 120GB Force Series 3 SSD. Our review has identified that a significant percentage of these drive do not perform to specifications. The solution will require changes to both the SSD firmware and the hardware components of the SSD itself. We have stopped shipments of the affected drive, Corsair part number CSSD-F120GB3-BK, effective immediately and have implemented the following remediation plan: (1) ALL users should cease using the CSSD-F120GBG3-BK drive immediately, even if you have not experienced issues of stability. (2) Users may then either RETURN the drive to Corsair, at Corsair's expense, to be exchanged with a replacement drive that does meet specifications OR (3) Return the drive to their place of purchase. Corsair is committed to product quality and we want to assure our customers that this remediation plan will be implemented at no cost to you. ] Zum Vergrößern anklicken....

 

arthur95 schrieb: AMD announces Adrenalin 21.4.1 GPU drivers with multiple new features - VideoCardz.com AMD Adrenalin 2020 21.4.1 Today AMD announces a new update to its Radeon Software. First of all, the new Adrenalin 21.4.1 driver does not come with the most anticipated feature: FidelityFX Super Resolution (FSR). This technology is sadly nowhere to be found in the new driver. It’s also worth... videocardz.com Zum Vergrößern anklicken....

Endlich keine Bloatware mehr!

 

AW: Mit ATI und nVidia zusammen PhysX nutzen(anleitung)

der link zum 1.04ff erzeugt eine fehlermeldung in norton 2010
website ist nicht sicher ...?????

mhhh...

sowie "Forbidden

You don't have permission to access /PhysX-mod-1.04ff.rar on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."

 

Wozu die Beta BIOS Version? Nimm mal die Version FD von 2012 und so schwer ist das garnicht was BIOS flashen angeht.
Mit USB Stick,

1. From GIGABYTE's website, download the latest compressed BIOS update file that matches your moth-erboard model.2. Extract the file and save the new BIOS file (e.g. z68apd32.f1) to your USB flash drive, or hard drive. Note: The USB flash drive or hard drive must use FAT32/16/12 file system. 3. Restart the system. During the POST, press the <End> key to enter Q-Flash. Note: You can access Q-Flash by either pressing the <End> key during the POST or pressing the <F8> key in BIOS Setup. However, if the BIOS update file is saved to a hard drive in RAID/AHCI mode or a hard drive attached to an independent SATA controller, use the <End> key during the POST to access Q-Flash.

 

Hallo liebe Community,
Hallo simpel...

Erstmal: Hut ab für dein Engagement und deine Hilfe! Ich bin wohl einer von vielen, die sich extra wegen dir hier anmelden. Soweit die gute Nachricht.

Die schlechte:
Ich bekomme die Fehlermeldung ebenfalls, habe schon die Minidumps ausgelesen und folgende Infos:


On Tue 17.01.2017 15:23:12 your computer crashed
crash dump file: C:\Windows\Minidump\011717-12136-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008359C70, 0xFFFFF80000BA0748, 0xFFFFFA800C0C4AB0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Tue 17.01.2017 15:23:12 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008359C70, 0xFFFFF80000BA0748, 0xFFFFFA800C0C4AB0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Tue 17.01.2017 12:42:52 your computer crashed
crash dump file: C:\Windows\Minidump\011717-8642-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008361D30, 0xFFFFF8000463E3D8, 0xFFFFFA80081BD010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Tue 17.01.2017 11:23:37 your computer crashed
crash dump file: C:\Windows\Minidump\011717-12230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008338990, 0xFFFFF80000BA0748, 0xFFFFFA800C859620)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 28.11.2016 15:03:56 your computer crashed
crash dump file: C:\Windows\Minidump\112816-11356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80082C54B0, 0xFFFFF80000B9A3D8, 0xFFFFFA800A9FA5B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.


Liegt also wohl am Kernel. Hängt mit Sicherheit mim WLAN Treiber zusammen, denn der Fehler taucht nur auf, wenn ich mich im WLAN befinde. Und aktuell sehr häufig. Habe den Treiber nach dem Dump um 15:23 neu installiert, er kam aber wieder. Den Dump "danach" habe ich leider nicht mehr, da ich eine Systemwiederherstellung vornehmen musste.

Habe versucht den Fehler mim Verifier zu beheben, erfolglos. Er lies mich nicht mehr starten, deshalb die Wiederherstellung. (Keine Angst Verifier ist bereits wieder resetet/ausgeschalten)

Die Dump Dateien habe ich hier nochmals beigefügt, ich hoffe du kannt mir helfen. Ich bin doch fast nur per WLAN im Netz und kriege den Fehler mehrmals täglich, wie du siehst teilweise innerhalb von 2 Stunden.