Last question first: hal.dll is the way that Windows communicates with the hardware on your system. If the hardware isn't recognized by hal.dll, there won't be any communication - and there will be errors (such as BSOD's). This mostly happens with hardware problems and/or incompatibility issues.
Back to the first post....
MSINFO32 shows these 2 devices having issues:
Code:
Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
sptd ROOT\LEGACY_SPTD\0000 This device is not present, is not working properly, or does not have all its drivers installed.
I see the first one most often with malware infections, so I'd suggest running one of the free scans here:
Malware (read the details at the link)
I see the second one most often when there's issues with Daemon Tools or Alcohol 120%. Please uninstall Daemon Tools, and then run this free program to UNINSTALL the sptd.sys file:
DuplexSecure - Downloads
Check Device Manager when done with the above to ensure that there's no errors remaining there.
While you're at it, please uninstall the Catalyst Control Center. It can cause issues with some Win7 installations. If you need it, feel free to reinstall the latest version AFTER we're finished troubleshooting.
The BSOD error is a STOP 0x124 error. This is an error that's captured by your CPU and forwarded to Windows for processing - as such there's not much information that we can understand.
Most of these errors are hardware problems or compatibility issues. They can also be Windows issues, or corrupted drivers (not all analysts agree with the last one).
You can check compatibility of your hardware and software here:
Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads
And, to troubleshoot the STOP 0x124 error, please start with this topic:
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
BSOD BUGCHECK SUMMARY
Code:
[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 9 20:35:59.228 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.102
BugCheck 124, {0, fffffa8004baf8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR: 0x124_AuthenticAMD
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]