PC restarts or freezes after 15-20 minutes of gaming, help!
PC restarts or freezes after 15-20 minutes of gaming, help!
Intel i7-3770 processor, Intel DZ77GA-70K motherboard, 16GB DDR3 RAM (4x4GB), 128GB SSD + 1TB HDD, GTX 970 graphics card, and a custom water cooling setup. These components are significantly outdated and likely the root cause of the instability you're experiencing – particularly the restarts during gaming sessions. The integrated DZ77GA-70K motherboard is notorious for compatibility issues with modern GPUs like the GTX 970, leading to crashes and reboots. The DDR3 RAM configuration also contributes to performance limitations. The combination of these factors creates a bottleneck that your system struggles to handle, especially when running demanding games. The SSD likely isn't sufficient for storing large game files and operating smoothly alongside the older HDD setup. While the water cooling is impressive, it doesn’t address the fundamental hardware incompatibility issues.
This guide addresses potential stability issues in Windows 7, particularly those related to system crashes and freezes. Enabling the HPET (High Precision Event Timer) within the BIOS/UEFI settings can resolve these problems by providing a more accurate timing mechanism for the operating system. The HPET allows Windows to respond to events with greater precision, preventing conflicts that can lead to system instability. Additionally, ensuring your 64-bit OS is installed if available can further enhance performance and stability. It's important to note that while this adjustment can often resolve crashes, it's a preventative measure aimed at addressing underlying timing issues rather than fixing software bugs directly.
HEXiT :
if your using win 7 (looking at your start bar you are) go into bios and enable hpet (high precision event timer) if its disabled as win 7 needs it to run certain essential windows elements.
if your using 64bit os then set it to 64 if that option is available.
Hi,
I did as you told, but it was not of any help. Still facing the same issue. Any idea?
Thanks
Thanks for your reply. Ok, I will do what you have told and see if it solves the issue or not.
Thanks
open your events log (cntrol panel ad,in tools/event viewer) and look for error 41 this is a marker error that is written 1s the pc recovered from a restart. its not the cause of the error, but as i say it is a marker. look at the time of that error 41 and look for other errors that appear just before it was created.
you can look for errors in the past 24 hours, if theres any critical that are listed, look at that list first.
after that look at errors an lastly warnings.
post the results if you think its relevant.
HEXiT :
open your events log (cntrol panel ad,in tools/event viewer) and look for error 41 this is a marker error that is written 1s the pc recovered from a restart. its not the cause of the error, but as i say it is a marker. look at the time of that error 41 and look for other errors that appear just before it was created.
you can look for errors in the past 24 hours, if theres any critical that are listed, look at that list first.
after that look at errors an lastly warnings.
post the results if you think its relevant.
Hi,
I looked at it, and I have posted the screenshots to help you understand the issue. If you need more information please tell me.
Thanks
you have 5 kernal events error 41's look at the times of these errors and go through the list and find the errors if any that show up just before the time of the error 41 codes.
How can I show you the full list of the logs in details, that way you will be able to understand much better. You have any idea?
Thanks
The system generated an event log entry indicating a failed login attempt. The event details include the timestamp, source computer name ("Om"), and specific binary data representing the authentication request and response. This data likely contains information about the username, password hash, and other security parameters used during the login process. The event severity is set to "Level 2," suggesting a potential security concern. Further investigation of this event log entry would be necessary to determine the root cause of the failed login attempt and assess any associated risks.
mate that error is listed 5 seconds after the error 41. you want errors before error 41.
but looking at the list of errors in that top box there isnt an error immediately before error 41. so it may not be a software error.
if thats the case it may be a hardware issue related to your psu as the system is resetting when stressed.