Windows 7 BSOD on Server 2008, possibly OC related

[ZippoLag]

Hello and thanks for reading, I was doing some OC on both the motherboard (fsb, cpu and ram) and vga, and about after a week I got a BSOD, it had been a while since the system was running fine, and I had never found this stop code before. For now I've gone back to the normal non-OC configuration of the hardware as a precaution, but I would really appreciate if anyone could clear my doubts.

Facts:
- SO: Windows Server Enterprise 2008 R2 SP1 (x64); Installed about a yer ago
- Hardware has been working for about 4 years (K9N2 SLI Platinum, XFX GeForce 9500GT)
- System has thrown other BSODs in the past, no cause found (althought the oldest ones may have been related to a keyboard driver (that has been ridden of long ago)
- System was in a OC state when BSOD occured (normal and oc state CPU-Z links in the file)
- OC'd state had been thoroughly tested (prime95, memtest, furmkark) and used for about a week without any problems before BSOD occured.
- BSOD's code was 0x00000101

 

[ChatGPT]

It seems like you've encountered a BSOD (Blue Screen of Death) with stop code 0x00000101 while your system was in an overclocked state. Here are some insights and steps you can take to troubleshoot this issue:

Understanding Stop Code 0x00000101:​

• The stop code 0x00000101 typically indicates a hardware issue. It's often associated with problems related to overclocking, CPU, motherboard, or power supply issues.

  Troubleshooting Steps:​

  1. Check System Stability:
     • Ensure that your system is stable in its default (non-OC) configuration. This will help determine if the overclocking caused the BSOD.

1. Monitor Temperatures:
   • Check the temperatures of your CPU and GPU during overclocking. High temperatures can lead to instability.
   []Reset Overclock:
   • Since you've reverted to the non-OC configuration, monitor the system for stability. If it remains stable, the overclock could have caused the issue.
   []Review Hardware Changes:
   • Any recent changes in hardware configurations or installations should be considered. Undo any recent changes if possible.
   []Update Drivers and Firmware:
   • Ensure that all your drivers and firmware are up-to-date, including motherboard chipset drivers, GPU drivers, and BIOS updates.
   []Run System Diagnostics:
   • Use Windows Reliability Monitor to view system stability history and any reported issues.
   []Check Event Viewer:
   • Look for error logs in the Event Viewer related to the BSOD. This can provide more details on the cause.
   []Check for Windows Updates:
   • Make sure your system has all the latest Windows updates installed.

     Additional Recommendations:​

     • Run stress tests like Prime95, Memtest, and Furmark again after reverting to default settings to confirm system stability.
     • Consider gradually overclocking your system again, ensuring each step is stable before moving to the next.
     By following these steps, you can identify the root cause of the BSOD and potentially prevent such issues in the future. If the problem persists, further hardware diagnostics might be necessary. Feel free to provide more details for tailored assistance.