Hello all. I've been getting blue screen crashes for months (a check in my event viewer shows they started around January). Only recently did I decide enough was enough and to start looking into them.
Primarily, they manifest as STOP 0x109 errors, but there have also been a couple 0x1e errors and a few others show up once. I tried to enable driver verifier, as my research led me to believe that this was a driver error modifying the windows kernel. However, every time I tried to enable it and reboot, I would get a 0xc9 error. I found the erroneous driver that was causing this issue and deleted it, but upon digging back into the original repeated 0x109 errors I kept coming across the following in WinDbg:
"BugCheck 109, {a3a039d8a54ad540, 0, b266a988baa6cd90, 101}
Probably caused by : ntkrnlmp.exe ( nt+76e80 )"
A quick google search yielded that this is the NT Kernel Multiprocessor, and that this showing up is something of a red herring - that is to say, it's an inconclusive cause for the issue. So, I'm hoping someone can help me out and point me in the right direction to determine what hardware is causing this issue (as I am now fairly certain it's a hardware issue, since it's not a specific driver being returned).
Thanks in advance, and please let me know if there is any information I neglected.
Primarily, they manifest as STOP 0x109 errors, but there have also been a couple 0x1e errors and a few others show up once. I tried to enable driver verifier, as my research led me to believe that this was a driver error modifying the windows kernel. However, every time I tried to enable it and reboot, I would get a 0xc9 error. I found the erroneous driver that was causing this issue and deleted it, but upon digging back into the original repeated 0x109 errors I kept coming across the following in WinDbg:
"BugCheck 109, {a3a039d8a54ad540, 0, b266a988baa6cd90, 101}
Probably caused by : ntkrnlmp.exe ( nt+76e80 )"
A quick google search yielded that this is the NT Kernel Multiprocessor, and that this showing up is something of a red herring - that is to say, it's an inconclusive cause for the issue. So, I'm hoping someone can help me out and point me in the right direction to determine what hardware is causing this issue (as I am now fairly certain it's a hardware issue, since it's not a specific driver being returned).
Thanks in advance, and please let me know if there is any information I neglected.
Last edited:
My Computer
At a glance
Windows 7 Professional x64AMD Phenom II X6 1100T2 x F3-17066CL7D-4GBPIS & 2 x F3-10666CL9D-8GBSRXFX Radeon HD 6970 & XFX Radeon HD 6950 (Cros...
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- custom build
- OS
- Windows 7 Professional x64
- CPU
- AMD Phenom II X6 1100T
- Motherboard
- 890FXA-GD70
- Memory
- 2 x F3-17066CL7D-4GBPIS & 2 x F3-10666CL9D-8GBSR
- Graphics Card(s)
- XFX Radeon HD 6970 & XFX Radeon HD 6950 (CrossFireX)
- Hard Drives
- Seagate Barracuda XT ST32000641AS 2TB 7200 RPM