Solved Constant Crashes...processor core? PLEASE HELP!

[Thaumaturge Jay]

Okay so Windows 7 64 bit system...has started acting weird (odd freezes, shuts down, etc) tried to run Malwarebytes and this causes system to crash. Checking event viewer shows a "processor core" error. Tried running jv16 to clean up some registry issues (there weren't many, like 11 registry issues) but that seemed to work fine.

System is still crashing and I can't figure out why, not getting a BSOD report just shuts down, I've left it running without doing anything and it has been on for 20+ minutes. However, if I try to do Windows update, or Malwarebytes etc it crashes almost immediately. I'm stumped anyone with any guesses or help would be GREATLY appreciated.

I'm going to post a couple pictures, if I can, of the error report in event viewer...If you cannot read the details of the attached image I can post them separately.

View attachment 236725

View attachment 236723

View attachment 236724

View attachment 236726

 

[koolkat77]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Thaumaturge Jay]

Sorry missed that! Thanks here is the file
I think I initially posted a little prematurely...here is the full file (I think?)

View attachment 236736

 

[koolkat77]

First off, get rid of all the McAfee stuff on your computer. It's known to cause BSoDs! Use MSE. It's free, light weight and does not cause problems on windows 7. Make a full scan after installed and updated

Start Menu\Programs\McAfee	Public:Start Menu\Programs\McAfee	Public
Start Menu\Programs\McAfee Online Backup	Public:Start Menu\Programs\McAfee Online Backup	Public
Start Menu\Programs\McAfee Security Scan Plus	Public:Start Menu\Programs\McAfee Security Scan Plus	Public

• McAfee Removal Tool
• McAfee Removal Tool - McAfee Uninstaller
• Microsoft Security Essentials - Free Antivirus for Windows

​

Run the System Files Checker that scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible and then run Disk Check on your hard disk/s for file system errors and bad sectors on it.

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• http://www.sevenforums.com/tutorials/433-disk-check.html

Your graphic card drivers need to be updated! Current version is one from 2009... Phewww, ancient.

Driver	c:\windows\system32\drivers\nvlddmkm.sys (7.15.11.7967, 9.23 MB (9,677,600 bytes), [COLOR="Blue"]3/6/2009[/COLOR] 12:52 PM)

Uninstall the older drivers first: Click on the Start rb: > Control Panel > Programs > Uninstall a program

Source for latest driver:

• Download NVIDIA Forceware 306.97 WHQL Vista 64 - FileHippo.com

Update your sound card drivers as well.

Driver	c:\windows\system32\drivers\chdrt64.sys (4.36.7.0, 217.50 KB (222,720 bytes), [COLOR="Red"]3/4/2008[/COLOR] 3:32 AM)

• Name Conexant High Definition SmartAudio 221 - Google Search

Do these and let us know the results

 

[Thaumaturge Jay]

Okay, did all that, the NVIDIA driver wouldn't work checked with NVIDIA directly and it said that was the most current driver same was true with the soundcard.

While doing all this I received a BSOD 0x0...24?

Wouldn't let me sfc /scannow kept stoping at random points, ran that in safemode and it completed.

Attached is the new SF Diagnostic .zip file
View attachment 236801

 

[koolkat77]

Did you run Disk Check?
Make a hard drive test from the hard drive manufacturers website

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS

For bug check 124, go through this guide:

• http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

What's the age of all the hard ware?

 

[Thaumaturge Jay]

The Hard Drive is about a year old, the original one failed after about a year...the stop error is 0x000000024 (0's may be in accurate) but it was just 24 at the end...everything I see points towards hardware failure? I did run check disk and it found no bad sectors. My worry is the processor?

I ran malwarebytes again and cleaned one thing off the machine, been running MSE for 2:35 and it is STILL going ugh...anyway when that finishes I will run the disk checker, AVG also has a pretty cool utility disk that I'll try and post any findings...you have any other guesses?


Thanks for your help so far BTW!

 

[koolkat77]

Sorry, I meant the computers "hardware"

 

[Thaumaturge Jay]

I think it is about 2 years +/-

 

[koolkat77]

Hmm okay, take your time and follow the 124 guide
Let me know the results for seatools and seatools DOS

 

[Thaumaturge Jay]

Couldn't run the seatools DOS as the CD drive isn't working...not showing up in device manager, also the coprocessor has no drivers installed?

The CD drive isn't identified by the system at all ?

It won't let me run windos update either Code 80072EFE? This stupid thing is about to irritate me

UPDATE: it suddenly decided to let me do the updates? I guess that trouble code relates to a connectivity issue? Whatever, this stupid machine is still irritating me though...

I've gone through the 124 stuff and don't find any major issues other than the CD drive and the coprocessor drivers?

 

[koolkat77]

If your having connectivity issue try getting the latest drivers for your network stuff.
I'm not sure about the coprocessor. Can you explain in details? Sounds like your CD Drive is spoiled?

 

[Thaumaturge Jay]

Well, lots of cussing some persistance and a TON of anger...I was able to run a few of the windows updates...which made the CD drive work? Who'da thunk it.

I've been blaming an OS/registry/whatever software issue for a while. Did finally get the Seagate DOS to run and that came back fine. Been running Memtest 86 for about 4 hours now and it is cycling the error count at about 1000 errors per second in test #9...right now it is up to 11369000 and counting FAST...

 

[koolkat77]

Do you mean you're seeing red errors? You can post some picture by clicking with a cam

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Thaumaturge Jay]

This has been running for over 5 hours about 4 3/4 of those have been on test 9 and Pass 52% and Test 84% all that time but the error count is SCREAMING by at nearly 1000 new errors a second literally....


View attachment 237173

 

[koolkat77]

Okay, looks bad.
How many sticks of RAM do you have? are you taking this test with all sticks inserted or just one?

 

[Thaumaturge Jay]

All in...2 sticks installed

 

[koolkat77]

Hmm.

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

 

[Thaumaturge Jay]

I guess I was wondering if I stop the test? I'm gonna do that and follow the steps above...let you know what's up tomorrow...

 

[koolkat77]

Okay, go ahead. See you soon