New
#1
BSOD: hal.dll and ntoskrnl.exe at fault
I have recently updated from 32-bit windows 7 to 64-bit windows 7 for obvious reasons. I have had 5 BSODs since I did that, I have checked my drivers and they seemed to be fine on most of the programmes I used, I have also used cmd to scan for errors using the sfc /scannow command first time it found corrupted files second time it didn't. After it happened again I then used Bluescreen viewer to see what caused it and all but one had something to do with hal.dll and ntoskrnl.exe, so now I am confused as many things I have read says its a driver or bios issue, but seeing as I am not that good at this sort of thing I thought I should ask for help.
I have grabbed all using the SF diagnostic Tool
*Ok I had another BSoD so I thought I would troubleshoot this myself. The bug check code is 0x00000124 and the cause is hal.dll so I read that it was a hardware issue, but since the computer worked perfectly on 32-bit I don't think that is the problem but I checked temperatures to see if anything was overheating (see below) I then checked drivers again and found 3 drivers on Driver Magician after scanning, audio, card reader and motherboard options so I installed them all, but the motherboard driver I was given was 15.57-nforce-winvista-win7-64bit-international-whql, I scanned again and it give me the same driver....I don't know if that is the problem, but if someone could translate the dump files and point me in the right direction.
I used a driver identifier to check all my drivers and it only found 3 that needed updating (see below) but no motherboard driver that needs updating so now either it is false information or I have a corrupt driver somewhere I think.
Last edited by mastahelix; 24 Nov 2013 at 19:11. Reason: New info