Windows 10: Blue spinning pin wheel, program not responding?

The torture for both myself and the ram are over, 14 hours, 8 passes and no errors, hopefully ok... More soon.

 

Is the latest Whocrashed Analysis what we were looking for?

 

Below.

I didn't get what you meant here, what do mean mismatched (different SKU)?



[/QUOTE]

 

memtest86+ version 5.01: 8 passes, 0 errors, 16 GB RAM = Pass.
The crash dump test is to produce a dump file.
Whocrashed indicated that it was set up but did not find a dump file.
There is a link to click on in the whocrashed linked for some troubleshooting steps.
In post #48 are the steps to reset the paging file.
These steps were put on hold when the memtest86+ version 5.01 was started.
The RAM comment was not applicable as the RAM is matched and passed the memtest86+ testing.
So unless the RAM is a false negative, which is less likely with 8 passes, the RAM moving forward should be OK.
Was chkdsk /x /f /r ran on D:? Was chkdsk /x /f /r ran on drive E? and HD Tune on drive E? Please post the results on indicate the posts with the results.
What was done with Malwarebytes registry residuals? Please create a ticket for this so that it is taken care of before working on the rotating blue circle.

In step #48 the paging file will disappear > reboot > reappear with automatic manage > reboot.
Then a new whocrashed test is to be performed to see if a dump file can be created.

Have all of the important files been backed up to another drive or to the cloud?
Has a backed up image been made and is the backed up image up to date?
Has a brand new restore point been made?

For Windows driver verifier there are 3 methods to turn off or recover from using the tool.
The tool is designed to repetitively produce BSOD.
Each time there is a BSOD with the automatic restart off you should see a BSOD window.
For every BSOD make sure that the the % number always rises to 100% before rebooting so that there is sufficient time to create a dump file. There should be a bugcheck displayed and sometimes there is a driver in the form *.sys. If you see the driver please record it and post it into the thread.

After each BSOD in order to turn Windows driver verifier off or to recover you will use the Windows advanced troubleshooting menu. On the menu there will be 3 options to use and they should always be used in order. Advanced to the next step only if the prior method failed to turn off or recover from using the tool.
1) startup settings > click restart > select #6 enable safe mode with command prompt > type:
verifier /reset
2) command prompt > Administrator: X:\Windows\system32\cmd.exe > X:\Sources> type:
verifier /bootmode resetonbootfail
3) system restore
Often if system restore is clicked the dump file disappears so this method should be avoided as little progress is made in the troubleshooting.

The tool will be used for 48 hours. After the last BSOD the tool will be used for an additional 36 hours.

Sometimes the computer can become sluggish or the boots can be very slow during the use of the tool. If this happens communicate the problem into the thread and the test settings can be modified.

After each BSOD the tool will be turned off and you will return to the desktop. On the desktop run Whocrashed analyze and run the beta log collector to post a new zip into the thread. If you are able to identify the misbehaving driver you can update it and then restart Windows driver verifier to find the next misbehaving driver. Drivers can be replaced as soon as they are uninstalled or at the end after all misbehaving drivers have been uninstalled. The end result should be the same.

Use this link for the test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use this link for the methods to turn off and recover from using the tool:
BSOD Crashes and Debugging - Windows 10 Forums

 

In Whocrashed when you click tools - crash dump test there is a "Crash" button that will manually crash the computer. I'm guessing this will create a dump file we want but I don't recall you asking me to hit that button...

I did the paging file reset steps that you asked but it doesn't seem to have made any difference to the way you've asked Who crashed to be run...

chkdsk /x /f /r has not been run on D: or E: nor HD Tune on E: (External storage)

I have not done anything about Malwarebyte's residuals, I think a registry clean was the only option or contacting Malwarebyte's correct? I will submit a ticket asap. Perhaps the cleanup tool run from safe mode may work?

My normal Macrium backups are working each day but I can create a full image at any time... Does Driver Verifier have the potential to make a mess? Should I backup each time before using the tool?

I still have not uninstalled AI Suite or MSI Afterburner. Please let me know which things to proceed with in order of importance.

 

Initially do you want me to set up and run Driver Verifier exactly as the Ten forums tutorial say's to?

Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

 

1) Run HD Tune and chkdsk /x /f /r on all partitions/drives and post images/results into the thread
2) Submit a ticket to Malwarebytes for the residual files after using the uninstall tool
3) The Whocrashed was downloaded and installed to perform the crash dump test. To perform the crash dump test: above analyze click on tools > click crash dump test > type: ACCEPT > after the crash click analyze > post the whocrashed analyze report into the thread and run the beta log collector to post a new zip into the thread
4) AI Suite and MSI Afterburner should be uninstalled during the troubleshooting process and can be reinstalled after the troubleshooting has been completed with a week of no BSOD.
5) Make sure that there is no overclocking during the troubleshooting process.
6) After all of the above steps you can perform an updated Macium image, a brand new restore point and then turn on Windows driver verifier.
7) For the test settings please use the Microsoft link with approximately 19 tests. If there are major problems with sluggishness or boot then you will move to the Ten Forums 3 tests and increase the number of tests to make sure that all tests are performed during the 48 hour period.
7) For each dump run the beta log collector and post a new zip into the thread.

 

I think I've got that but what's this part - "Use this link for the methods to turn off and recover from using the tool"

When does this bit come in?

The Whocrashed instructions are not clear. After typing ACCEPT do I click the Crash! button or go straight to back to Analyze button in the main screen instead?

 

After typing ACCEPT click crash to create the BSOD. Then wait for it to run to 100%. Then look for the bugcheck and the driver to get familiar with the layout. The misbehaving driver may display dead or deaddead. Then reboot > reopen whocrashed > click analyze > post the whocrashed report into the thread and run the beta log collector.
If there is a deaddead analyze report then find the memory.dmp and post it into the thread using a zip.

 

I forced the crash and got the 0xdeaddead but on re-analyzing in Whocrashed I'm still getting "No valid crash dumps have been found on your computer"

Why are the dumps not being created?

 

That is part of the troubleshooting.
Please post the whocrashed analyze result and run the beta log collector and post a new zip into the thread.

 

More tomorrow, thanks for hanging in there. *Smile


M-MAXIMUSXHERO (2018-04-03 23 28)

 

After the in place up grade repair the logs now display the failures messages to produce the dumps.
Code: Event[1396]: Log Name: System Source: volmgr Date: 2018-04-03T21:58:54.858 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: M-MaximusXHero Description: Dump file creation failed due to error during dump creation.[/quote]
Code: Event[1397]: Log Name: System Source: volmgr Date: 2018-04-03T21:58:54.858 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: M-MaximusXHero Description: Crash dump initialization failed![/quote]

 

chkdsk /x /f /r on D: is looking for bad clusters with an ETA of 1 hr 50. Is there not a faster method?

Edit: I think D: is stuck on is looking for bad clusters.