[abrahams child]

Another crash this morning without Malware installed.

Attached Files

•  JR 7.zip   22.45KB   273 downloads

[Advertisements]

PROCESS_NAME:  MsMpEng.exe

 

 

This is a driver associated with Windows Defender, have you re enabled this since you post your last Speccy report as it was previously shown to be disabled.

 

Operating System

Windows 7 Home Premium 64-bit SP1

Computer type: Desktop

Installation Date: 30/07/2011 1:14:15 PM

Windows Security Center

User Account Control (UAC): Enabled

Notify level: 2 - Default

Firewall: Enabled

Windows Update

AutoUpdate: Not configured

Windows Defender

Windows Defender: Disabled

Antivirus

Antivirus: Enabled

Company Name: Microsoft

Display Name: Microsoft Security Essentials

Product Version: 4.10.209.0

Virus Signature Database: Up to date

[phillpower2]

PROCESS_NAME:  MsMpEng.exe

 

 

This is a driver associated with Windows Defender, have you re enabled this since you post your last Speccy report as it was previously shown to be disabled.

 

Operating System

Windows 7 Home Premium 64-bit SP1

Computer type: Desktop

Installation Date: 30/07/2011 1:14:15 PM

Windows Security Center

User Account Control (UAC): Enabled

Notify level: 2 - Default

Firewall: Enabled

Windows Update

AutoUpdate: Not configured

Windows Defender

Windows Defender: Disabled

Antivirus

Antivirus: Enabled

Company Name: Microsoft

Display Name: Microsoft Security Essentials

Product Version: 4.10.209.0

Virus Signature Database: Up to date

[abrahams child]

I tried to enable windows defender but it comes up with error code:0x800705b4.

[abrahams child]

I did some optional window updates and KB3172605 failed to install.  Now when I try to turn on windows defender it comes up with error code:0x80016ba.

[phillpower2]

I tried to enable windows defender but it comes up with error code:0x800705b4.

 

 

Was not suggesting that you try and enable Defender only if you had, more precisely I should have asked had you tried to re enable it, you have Microsoft Security Essentials which has its own version of Defender and was trying to determine if it was that that was flagged up in your crash dmp, try uninstalling MSE and then reinstalling it and see how that goes.

 

While you are seeing how reinstalling MSE goes you can stress test your CPU, there is a very good guide on the Windows 10 forum here that you can follow, the same guide can be used for Windows 7.

[abrahams child]

Had another BSD this morning after uninstalling and reinstalling MSE.  Didn't run the CPU test as it says the CPU can get really hot and I didn't want to risk toasting the CPU.

Attached Files

•  JR 8.zip   22.9KB   308 downloads

[phillpower2]

You asked back in your reply #18;

"How do you determine the health of the CPU?"

 

 

 

From my reply #19;

 

You could try AMD System Monitor and see if that tells you anything.

 

 

You never gave us any feedback so I asked in my reply #21;

 

 

did you try the AMD tool that was suggested.

 

 

 

Not knowing the answer to the above question and you still getting CPU related problems stress testing the processor was the only cause of action to offer, up to yourself if you do not run the test and no one here is trying to tell you otherwise only trying to help you get to the bottom of this one way or another.

 

 

IE gets the blame this time but still the same CLOCK_WATCHDOG_TIMEOUT (101) issue present, one of the drivers that has failed to load spsys.sys is also related to the processor, this driver is normally provided by way of a Windows update nowadays, check for and install any/all important/recommended Windows 7 updates, once done, grab a screenshot of the Windows update page that says that Windows is up to date and attach the screenshot to your next reply for us.

 

Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600

Machine Name:

Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e48750

Debug session time: Wed Aug 30 09:04:39.490 2017 (UTC - 4:00)

System Uptime: 0 days 3:32:33.378

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffff880009e7180, The PRCB address of the hung processor.

Arg4: 0000000000000001, 0.

 

Debugging Details:

------------------

 

 

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

 

PROCESS_NAME:  iexplore.exe

 

 

 

Unloaded modules:

fffff880`05ac7000 fffff880`05b38000   spsys.sys

fffff880`05b43000 fffff880`05bb4000   spsys.sys

fffff880`05ac7000 fffff880`05b38000   spsys.sys

[abrahams child]

I ran the AMD System Monitor and both CPU's are running in the green barely registering and both are running between 1000 to 2600 MHz but the video card is showing nothing.

[phillpower2]

Acknowledged 

 

Just do the following for us now if you will;

 

check for and install any/all important/recommended Windows 7 updates, once done, grab a screenshot of the Windows update page that says that Windows is up to date and attach the screenshot to your next reply for us.

 

[abrahams child]

Screen shot.

Attached Thumbnails

• 

[phillpower2]

Thanks, being fully up to date should mean that any drivers provided by Windows should also be up to date, I say should but would like you to do a quick check for us before I post the next steps, btw, just checked the ASUS homepage for the latest chipset drivers and BIOS, both are many years old and still beta versions, see here

 

Run SlimDrivers (free) from here, allow the program to scan your computer to check for any missing or out of date drivers.

 

Remember to always create a new restore point before updating any drivers.

 

Please note that I am not suggesting that you use any other product or service that may be offered at the link and be sure to uncheck the SlimCleaner free download box.

[abrahams child]

Done

Attached Thumbnails

• 
• 

[phillpower2]

Was hoping to see a newer chipset driver but never mind, can`t see that updating any of those drivers would help but if you do update them please make sure to create a new restore point before installing each one.

 

A rather long winded task now, we need to see if we can force any particular driver to crash and be flagged up by Driver Verifier, if this does not work I will be at a loss and can only suggest moving on to testing hardware;

 

 

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2   

 

1. Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

2. Run Driver Verifier -

- Windows 7 & Vista - START | type verifier 
- Windows 10/8.1/8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier 

Make these selections - 
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -

▪ Special Pool 
▪ Pool Tracking 
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8) The Concurrency Stress Test option is not available in Win10.
▪ DDI compliance checking (new as of Windows 8) 
▪ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish 
8. Re-boot[/HIDE]

 

 

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

 

- After re-start, you may not be able to log on to normal Windows

... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

... • Select "System Restore"

... • Choose the restore point that you created in step #1

 

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

- To turn Driver Verifier off - verifier /reset then re-boot

 

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.

- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

 

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

 

Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.  

[abrahams child]

After following the given instructions and rebooting I did have to repeatedly tap F8 to login.  But before I was able to login it had a BSOD and I was unable to us my restore point.  It said to use another restore point.

Attached Files

•  JR 9.zip   19.57KB   277 downloads

[abrahams child]

^{Another BSOD about an hour and twenty minutes later.  Was unable to do a restore point that I created or any other for that matter.}

Attached Files

•  JR 10.zip   19.85KB   267 downloads