What's the blue screen code? Crashes that reference HAL.DLL don't generally mean HAL.DLL is corrupted, just that there was an issue with hardware. Can you increase your memory/CPU Voltage slightly to see if that resolves the issue?
On Thu, Jan 10, 2013 at 4:38 PM, DSinc <[email protected]> wrote: > For the past several months I have been trying many things to > fix the MS black screen, "your hal.dll is missing/corrupt......" > I thought I fixed this back in NOV12. Apparently not. > Yes, the OS is WinXPsp3. And yes, my C2D is running with only > ONE core active. > I have 'fixed the mbr' > I have 'replaced the hal.dll file' (maybe NOT properly) > I have scanned the machine ad nauseam finding nothing > I have been patient. > > Yes, I do know what my last fix may be.......erase/reload. > Does anyone recall a link to the MS KB that deals with this trouble? > Thanks, > Duncan > >
