Windows 7 BSOD - Bugcheck 109

[Gizek]

hello, I'm posting because my PC crashing every day.. I see only Bugcheck 109 caused by ntkrnlmp.exe and memory_corruption, but there is no errors in Memtest86+, I have tested for 8 passes, please, help. Scan from SF Diagnstic Tool in attachments.

BugCheck 109, {a3a039d89a6d9af7, b3b7465eecea6a4d, fffff80003178b70, 1}


*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
TRIAGER: Could not open triage file : D:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt!ObpIncrementHandleCountEx+0 )


Followup: MachineOwner

TRIAGER: Could not open triage file : D:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2


FAULTING_IP:
nt!ObpIncrementHandleCountEx+0
fffff800`03178b70 4c894c2420 mov qword ptr [rsp+20h],r9


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT


BUGCHECK_STR: 0x109


PROCESS_NAME: System


CURRENT_IRQL: 0


STACK_TEXT:
fffff880`031af598 00000000`00000000 : 00000000`00000109 a3a039d8`9a6d9af7 b3b7465e`ecea6a4d fffff800`03178b70 : nt!KeBugCheckEx




STACK_COMMAND: kb


FOLLOWUP_IP:
nt!ObpIncrementHandleCountEx+0
fffff800`03178b70 4c894c2420 mov qword ptr [rsp+20h],r9


SYMBOL_NAME: nt!ObpIncrementHandleCountEx+0


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3


FAILURE_BUCKET_ID: X64_0x109_1_nt!ObpIncrementHandleCountEx+0


BUCKET_ID: X64_0x109_1_nt!ObpIncrementHandleCountEx+0


Followup: MachineOwner

TRIAGER: Could not open triage file : D:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2


FAULTING_IP:
nt!ObpIncrementHandleCountEx+0
fffff800`03178b70 4c894c2420 mov qword ptr [rsp+20h],r9


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT


BUGCHECK_STR: 0x109


PROCESS_NAME: System


CURRENT_IRQL: 0


STACK_TEXT:
fffff880`031af598 00000000`00000000 : 00000000`00000109 a3a039d8`9a6d9af7 b3b7465e`ecea6a4d fffff800`03178b70 : nt!KeBugCheckEx




STACK_COMMAND: kb


FOLLOWUP_IP:
nt!ObpIncrementHandleCountEx+0
fffff800`03178b70 4c894c2420 mov qword ptr [rsp+20h],r9


SYMBOL_NAME: nt!ObpIncrementHandleCountEx+0


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3


FAILURE_BUCKET_ID: X64_0x109_1_nt!ObpIncrementHandleCountEx+0


BUCKET_ID: X64_0x109_1_nt!ObpIncrementHandleCountEx+0


Followup: MachineOwner

 

[ChatGPT]

It looks like you're experiencing frequent crashes on your PC with Bugcheck 109 errors pointing to ntkrnlmp.exe and memory_corruption. Here's what we can deduce from the information you provided:

• Bugcheck 109 errors are typically related to critical kernel errors or critical kernel corruption. This could indicate issues with hardware, drivers, or the operating system.
• The specific error message you provided points at ntkrnlmp.exe as the likely cause of the crashes.
• Memory corruption could be caused by various factors, including faulty RAM, driver issues, or problematic hardware.

Since you've already mentioned that you ran Memtest86+ and it didn't detect any errors after 8 passes, which is a good sign, let's consider a few steps to further troubleshoot and potentially resolve the issue:

1. Update Drivers:
   • Ensure that all your drivers are up to date, especially graphics, chipset, and storage drivers. Outdated drivers can sometimes lead to system instability.
   []Check for System Updates:
   • Make sure that your operating system is fully updated. Windows updates often include bug fixes and improvements that could address the crashes.
   []Check for Overclocking:
   • If you have overclocked your CPU or RAM, try reverting to the default settings. Overclocking can sometimes lead to system instability.
   []Check for Malware:
   • Perform a thorough scan of your system for malware and viruses. Malware can cause various issues, including system crashes.
   []Check Hardware Connections:
   • Ensure all your hardware components are properly connected. Loose connections can sometimes lead to intermittent issues.
   []Event Viewer Analysis:
   • Check the Windows Event Viewer for any specific error messages or warnings that might provide additional clues about the crashes.
   []Diagnostic Tools:
   • You've used SF Diagnostic Tool, which is great. You might also consider running system file checker (sfc /scannow) to check for any corrupted system files.
2. Advanced Troubleshooting:
   • If the issue persists, you may consider running a system repair or restore, or performing a clean Windows installation to rule out any software-related issues. It's also worth mentioning that sometimes intermittent issues can be challenging to diagnose, so it may require a bit of trial and error to identify the root cause. If you encounter any specific error messages or behaviors that might provide more insight, feel free to share them for further analysis. Let me know if you need assistance with any of the steps mentioned above!