New
#81
Yes, I did... but I wasn't sure how to verify what results came of it.
I followed these instructions:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
WHEA_UNCORRECTABLE_ERROR - Random reboots and 0x124 error
-
-
New #82
@zbook is there anything you can recommend I do next?
- I hope to redo my CPU heatsink tonight or tomorrow then retry Prime95
- I haven't been able to figure out what those mouse/keyboard yellow triangles are and not sure I will
- I still need to reach out to Focusrite, but I'm not quite sure what to ask them now that I'm not getting BSODs (since 10/26)
- I resolved the Windows Start Menu issue by creating a second admin account, logging out of that, then logging back into my main account and it worked just fine (as was suggested in many threads on fixing the Windows Start Menu)
If you have other items you'd like me to address while my machine is on (need it on now for work), please let me know.
Thanks!
-
New #83
With your recent use of Windows driver verifier you could test the Focusrite driver or wait to see if there are any bsod related problems.
The device manager and msinfo32 indicated that there are problem devices.
Standard PS/2 Keyboard ACPI\PNP0303\0 This device is not present, is not working properly, or does not have all its drivers installed.Microsoft PS/2 Mouse ACPI\PNP0F03\0 This device is not present, is not working properly, or does not have all its drivers installed.
And they appear to be the device is not present.
It's unclear with the troubleshooting steps that you have already done why the yellow triangles were not fixed.
The CPU heat problem needs follow up and we'll await the test results.
-
New #84
Driver Verifier lead to a BSOD... it happened overnight while I was asleep. Latest dm_log_collection attached below:
Attachment 161778
Please have a look...! I appreciate it, again!
-
New #85
The Windbg has commands that are not working during this Windows upgrade period.
On some BSOD the commands may work and others they don't so the more the dumps maybe there may be some useful information.
With the commands that are working the BSOD indicated bugcheck A.
No definitive misbehaving driver was identified.
Download and install each:
Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed
Create a new restore point.
If you have not already made a backup image please use Macrium and place the backup image onto another drive or into the cloud.
Macrium Software | Macrium Reflect Free
Turn on Windows driver verifier with the settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Post new zips into the thread with new BSOD:
BSOD Crashes and Debugging - Windows 10 Forums
-
New #86
Attachment 161826
Running the Macrium Reflect Image backup of my C drive now.
How would you like me to use WhoCrashed?
I already have BlueScreenViewer available ... what can I post to show you?
As to Driver Verifier -- I ran this last night, which is what gave me the latest Minidump. How will these differ from the ones I posted this morning?
Thanks for explaining.
diznanl
-
New #87
With the windbg working suboptimally during this upgrade period having these additional tools may be useful:
1) bluescreenview
2) whocrashed
3) startup and recovery settings with automatic restart un-checked so that you have time to view the BSOD windows. Windows driver verifier will typically display the bugcheck driver verifier detected violation and sometimes the misbehaving driver may be displayed in the form *.sys
In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery > click settings > under system failure > un-check automatic restart
4) For whocrashed above analyze click on tools > crash dump test > type: ACCEPT
5) Click analyze > look for dead in the results
-
New #88
Hi diznanl,
I have looked at your most recent BSOD crash dump - as @zbook points out this was not a 0x124 hardware error and was not triggered by the Driver Verifier so it is pointing to something else on your system. The stack shows that there were a lot of network related activities and while it is unlikely to be the ndis.sys windows driver it could be due to the driver associated with your network card.
Intel(R) Ethernet Connection (2) I219-V - current driver is c:\windows\system32\drivers\e1d65x64.sys (ver 12.15.23.7) dated: Tue Jul 26 17:48:21 2016
If you can find a more recent driver either from Intel or your motherboard manufacturer I would suggest you update it.
-
-
New #89
Thanks... I found this driver on Intel's website and installed it:
Download Intel® Network Adapter Driver for Windows® 10
Attachment 161830
-
New #90
Backup Complete:
Attachment 161831
I'll now go through the steps mentioned:
- startup and recovery settings with automatic restart un-checked so that you have time to view the BSOD windows.....
- In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery > click settings > under system failure > un-check automatic restart
- For whocrashed above analyze click on tools > crash dump test > type: ACCEPT
- Click analyze > look for dead in the results
Quote
Related Discussions
