New
#11
After running memtest for all 8 gigs of my RAM overnight, the computer bluescreened with a different cause, still ntoskrnl.exe, but in a different locale or something. It wasn't x124 this time so I was hoping if you could scan it koolkat and see what comes back. Hopefully we've fixed something because hal.dll is no longer in bluescreenview as the cause, but if we could pinpoint what caused it this time, maybe it will be completely fixed. By the way, bluescreenview shows the bug check string as DRIVER_POWER_STATE_FAILURE if that helps. Thanks again for your amazing support koolkat!