[phillpower2]

First and foremost I suggest that you uninstall uTorrent.

Next run Windows own memory diagnostic tool (see Here) if nothing is reported you should next run Driver Verifier, please see below;

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"

2. Run the Driver Verifier -
Go to START | 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)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. 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*** IMPORTANT - PLEASE READ:

- 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.

Let us know how it goes.

[Advertisements]

uTorrent is already gone. Thanks again for recommending its removal.

Memory test went great. No problems detected. I also ran the verifier at the recommended settings, restarted, and nothing happened except a normal startup into Windows. I assume that's a good result?

There have also been no further warnings about ASP.NET 4.0.


I don't understand this part of your message:

- 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

What is the status screen?
Does this mean that the verifier must be continually running?

Edited by kushiro, 15 October 2013 - 02:27 PM.

[kushiro]

uTorrent is already gone. Thanks again for recommending its removal.

Memory test went great. No problems detected. I also ran the verifier at the recommended settings, restarted, and nothing happened except a normal startup into Windows. I assume that's a good result?

There have also been no further warnings about ASP.NET 4.0.


I don't understand this part of your message:

- 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

What is the status screen?
Does this mean that the verifier must be continually running?

Edited by kushiro, 15 October 2013 - 02:27 PM.

[phillpower2]

You are welcome and good to see you have made progress

I don't understand this part of your message:

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
The screen can sometimes appear as if the system has frozen when it has not - even when the screen is blank, check the HDD activity LED if this happens as a blinking HDD LED is a sign that Driver Verifier is still running.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use
It is possible for Driver Verifier to enable/disable minidumps and so you must sure that they are enabled.

Keep us posted how things go.

JFYI: Driver Verifier can sometimes run for a day or more

[kushiro]

OK. How will I know when it's done?

[phillpower2]

OK. How will I know when it's done?

An example screenshot of one of my own computers is attached below;

[kushiro]

That never appeared. After a while the Application just disappeared from the Task Manager, so I assumed it had finished its run.

[phillpower2]

That never appeared. After a while the Application just disappeared from the Task Manager, so I assumed it had finished its run.

No driver conflicts then, how is the computer behaving now.

[kushiro]

Everything seems to be humming along, which is troublesome, because of how I am used to random crashes (of Windows Explorer, Firefox) and things that "stop working" (Catalyst Control, Superfetch Service, etc.).

But right now no complaints.

I bought a new video card, though, so in a few days it could all go so very wrong.

[phillpower2]

Thanks for the update

I suggest that you use the computer as it is currently set up for a few days to see if it remains stable, any problems meanwhile let us know.