New
#41
How is your system running? Still no BSODs? Best wishes. :)
How is your system running? Still no BSODs? Best wishes. :)
Hey my system is running great solved the problem by deleting mouse software with drivers from 2009, because hp doesnt update old things i guess. Thank you guys for all your help and support i will make sure if i have any other issues i will post them here.
Thanks,
Mark
Uh there back again sigh, I stupidly ran a DX11 tessallation test even though i dont have a graphics card that supports it and ultimatly crashed my comp. Its working but im getting bluescreens now will make a zip file and attach to this post.
Thanks,
Mark
Caused by hardware but I would remove Symantec prior to do ing anything else just in case.
I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_...080710133834EN
Microsoft Security Essentials - Free Antivirus for Windows
Your .dmp file shows a stop error of 0x124 which is a general hardware error .
Some generic advice.A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress
If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.
You can read more on this error and what to try here... Stop 0x124 - what it means and what to try
I know Symantec is not the error because these BSODs only started after the ran the DX11 test from nvidia, bluescreenviewer also said something about hal.dll is there anything i should try in specific or just go down the list?
Just go down the list. Then report back whether you were able to stop the crashes.
Got another BSOD a couple minutes ago but with a black screen. It keeps saying hal.dll what is that? and i am looking over the link aswell
hal.dll is a system file. Bluescreenviewer typically blames system files for blue screen crashes and is not entirely reliable. If you are worried about it, though, you could try running Disk Check with both boxes checked and then SFC /SCANNOW Command - System File Checker (up to three times for sfc to fix all errors) to check for any system file corruption.
Edit: hal.dll is the hardware abstraction layer, so it may be pointed to due to the hardware fault crash you are receiving. Just FYI.
Last edited by writhziden; 09 Jan 2012 at 17:08. Reason: hal.dll info.
Running some tests right now and my video card drvier is fully updated. I am now checking other stuff.