Weird crash and after moment system restarted on 9900K and 2080 Ti.
- Ersteller sew333
- Erstellt am
V
VoAlgdH
Gast
Das stimmt schon, ist nur ein Anhaltspunkt. Wenn es nur am Treiber liegt, um so besser.
DriveByFM
Rear Admiral
- Registriert
- Juni 2008
- Beiträge
- 5.925
Hatte nämlich ein ähnliches Problem vor langer Zeit, keine Ahnung vorher es kam, aber es lag nur am Nvidia Treiber. Hatte auch das Netzteil im Verdacht und sogar mehrere getestet. Aber einfach DDU und dann Treiber neuinstallieren und schon keine Idle crashes mit Kernel 41 mehr. 
You mean KERNEL 41 restart after quitting game or during game?DriveByFM schrieb:Hatte nämlich ein ähnliches Problem vor langer Zeit, keine Ahnung vorher es kam, aber es lag nur am Nvidia Treiber. Hatte auch das Netzteil im Verdacht und sogar mehrere getestet. Aber einfach DDU und dann Treiber neuinstallieren und schon keine Idle crashes mit Kernel 41 mehr.
Dextro1975
Commodore
- Registriert
- Juni 2008
- Beiträge
- 4.182
Bei mir kam ab und zu ein Kernel 41 Problem und es lag an der Soundkarte die ein Wackelkontakt hatte.
When Metro crashes i decide to logout from system and log back again. ( By ctrl alt delet ). Because system was unresponsible ( turning circle ).
The system crashes ( rebooted itself ) after i logout ( CTRL + ALT + DELETE ) from system and log back again to refresh system. Then bum reboot ( kernel 41 ).
The system crashes ( rebooted itself ) after i logout ( CTRL + ALT + DELETE ) from system and log back again to refresh system. Then bum reboot ( kernel 41 ).
Hey guys,sorry i must write.
I found this in windows/livekernelreports/ pow32kwatchdog.dmp
File appeared 5 minutes before reboot. And my question is. It was that file related to that reboot or bsod ?
But like i said that reboot was so quick that i even dont saw blue screen on a display. Just simply reboot.
Somebody said that this was caused by faulty memory or psu. But i checked memtest86 and ramtest and no issues. Realbench and other games no issues.
Thanks. Its my last question
Apologize for my bad language.
I found this in windows/livekernelreports/ pow32kwatchdog.dmp
File appeared 5 minutes before reboot. And my question is. It was that file related to that reboot or bsod ?
But like i said that reboot was so quick that i even dont saw blue screen on a display. Just simply reboot.
Somebody said that this was caused by faulty memory or psu. But i checked memtest86 and ramtest and no issues. Realbench and other games no issues.
Thanks. Its my last question
Apologize for my bad language.Game was running maybe 21 hours. Game crashed when i click EXIT TO MAIN MENU.
I get BLACK SCREEN and no monitor signal for 1 minute, and crash to desktop with TDR driver crash in event log. After that i log off from system and log back in again and system rebooted unexpected.
Just after crash to desktop pc get rebooted after i log off from system ( and back in ) by CTRL ALT DELETE.
Maybe something messed up during logging off and back on again.
There was not bugcheck in event log. Only Kernel 41 power.
And file appeared C:/Windows/livekernelreports/pow32kwatchdog.dmp
1 arrow: 3 driver crashes from a game with black screen,CTD,turning circle instead of arrow
2 arrow:winlogon, i decide to ctrl alt delete , log out and log back again in
3 arrow: kernel 41 power and weird reboot
I get BLACK SCREEN and no monitor signal for 1 minute, and crash to desktop with TDR driver crash in event log. After that i log off from system and log back in again and system rebooted unexpected.
Just after crash to desktop pc get rebooted after i log off from system ( and back in ) by CTRL ALT DELETE.
Maybe something messed up during logging off and back on again.
There was not bugcheck in event log. Only Kernel 41 power.
And file appeared C:/Windows/livekernelreports/pow32kwatchdog.dmp
1 arrow: 3 driver crashes from a game with black screen,CTD,turning circle instead of arrow
2 arrow:winlogon, i decide to ctrl alt delete , log out and log back again in
3 arrow: kernel 41 power and weird reboot
DarkSoul
Commander
- Registriert
- Aug. 2008
- Beiträge
- 2.632
May be just caused by a faulty game code. No game is intended to be run so many hours. Maybe the memory cleanup did not work correctly and your system went out of RAM. Maybe the game itself crashed due to this memory issue or any other reason.
The questions are:
1. Does the same game crash if you play it only a few hours?
2. Do other games also crash if you leave them unattended for also 20 hours?
3. Does the system crash if you don't run any program or game for 20 hours (idling all the time)?
The questions are:
1. Does the same game crash if you play it only a few hours?
2. Do other games also crash if you leave them unattended for also 20 hours?
3. Does the system crash if you don't run any program or game for 20 hours (idling all the time)?
1. No crash again in Metro. All stable. Happened once.
2.Other games never crashed like this ,even after 20 hours.
3.SYstem never crash if i dont run any program or game for 24 hours.
Just after Metro Exodus it happened once,no able to reproduce.
2.Other games never crashed like this ,even after 20 hours.
3.SYstem never crash if i dont run any program or game for 24 hours.
Just after Metro Exodus it happened once,no able to reproduce.
I am worried because somebody said this to me:"Something is almost stable. Things like this are incredibly hard to pinpoint, but generally you'll need to run whatever stress tests you're playing with for 24 hours or more to catch them. My bet is on RAM voltage being slightly too low (which will eventually show up in Memtest after a few days). ANY errors in Memtest, no matter how long you run it (within reason) point to a problem. "
What you think?
What you think?
Ähnliche Themen
