we are having sysetm errors and BSOD

On every BSOD, the culprit is Ntoskrnl.Exe. tried all of the fixes I could, MS had a hot fix, but its no longer downloadable.  Does anyone know of a fix?  Also tried a number of fixes on the internet
ptcurranAsked:
Who is Participating?
 
rindiCommented:
This looks like either a problem with your disk, file-system or RAM. Test your RAM using memtest86+, the disk using the manufacturer's diagnostic utility. If either of those tools report errors, replace the problem part, or if it is the disk, act according to what the utility says (probably also replace the disk). You'll find those tools on the UBCD:

http://ultimatebootcd.com

If both tests pass without errors, run a chkdsk DriveLetter: /f /r on all drive letters of your disk.
0
 
rindiCommented:
Zip your last 3 minidump files (if you have setup your system to make full memory dumps change the setting so only small dumps are made, then wait for 3 BSOD's) and attach the zip file with your next comment.
0
 
ptcurranAuthor Commented:
I am also getting a new error,

{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\System32\config\COMPONENTS' was corrupted and it has been recovered. Some data might have been lost.
This has shown up in the log for the past few days

Thank You for your help
Minidump.zip
0
 
ptcurranAuthor Commented:
Thanks a lot, it was new memory also
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.