Tech Support banner

Status
Not open for further replies.
1 - 20 of 42 Posts

·
Registered
Joined
·
430 Posts
Discussion Starter #1
Okay so far I was able to download the file. I run the app and a cmd box opens with nothing in it. After that the computer crashes. What is suppose to happen? I am not seeing any files in my document.

I don't understand what is happening.:cry:
This is the Ryzen rig I am having problems with.:hide:

Also I ran the driver verification ... how long is that suppose to run? Will it stop when the computer is shutdown?:huh:
 

·
Registered
Joined
·
430 Posts
Discussion Starter #2
Okay I was able to get it to run in safe mode ...

I could not copy and paste the result so I hope the attach zip file is what you need.
 

Attachments

·
Registered
Joined
·
430 Posts
Discussion Starter #4
My specs are listed in my sig. This is a new build by me this month. I had to reinstall windows more than once. It is the Ryzen rig that is crashing.
 

·
Registered
Joined
·
430 Posts
Discussion Starter #5
I tested the memory and they tested good. I tried to run the dos seagate program, but it could not see the drive. It's a seagate. Maybe because it's 4 tb?
 

·
Registered
Joined
·
430 Posts
Discussion Starter #6
Downloaded and installed Sea Tools for Win. Ran basic tests and the drive passed. I can't do any further test without backing up the files and I can't do that because I don't have an external drive to put them on. So far memory and drive cleared.

My notification sounds are a few seconds after the box appears. Something is up with that, and it takes longer to boot up than a much slower computer I have. Don't understand that.:nonono: I'll run comodo and malwarebyte to see if there is a problem on that end. Still don't know if that driver verifier did anything, but I did run it.:4-dontkno
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,370 Posts
Hi. . .

I ran all of the dumps and the 3rd party drivers named must be updated or removed.

Code:
[font=lucida console]
BugCheck 1000007E, {ffffffffc0000005, fffff88007016e26, fffff88002586808, fffff88002586070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88004a16e26, fffff8800bac6808, fffff8800bac6070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88007017e26, fffff88002571808, fffff88002571070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {fffff8000000fb0f, 8, fffff8000000fb0f, 0}
Probably caused by : athurx.sys ( athurx+9f3bb )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88003630501, 7fefd7905f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88003662501, 7fefcf505f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88001808501, 7fefd9d05f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff880046f5501, 7fefdcc05f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9805f41efc0, fffff9805f41e228, 694040, 23}
Probably caused by : amdxhc31.sys ( amdxhc31+23c39 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
The first is your Atheros wifi driver - https://www.sysnative.com/drivers/driver.php?id=athurx.sys

cmdguard.sys - uninstall COMODO. Driver verifier flagged this driver.

amdxhc31.sys - this appears to be an AMD chipset driver. Go to your system manufacturer's site.

Regards. . .

jcgriff2

`
 

·
Registered
Joined
·
430 Posts
Discussion Starter #9
Okay ...it looks like comodo was installed twice ... the internet security essentials and the anti-virus. That probably why comodo was a problem ... I competely uninstalled both. I tried to reinstall the security essentials, but for some reason a got an error during download, so I downloaded and installed the latest comodo anti-virus.

I went to the link for the wifi adapter, and downloaded the driver from the TP-Link site. It was not listed at the other two sites. I uninstalled the driver I was using and tried to install the driver I got from the site, but it claimed it could not find the adapter:nonono:, so I had to use the driver I had to get the adapter to function again. I tried to update it through the device manager, but it stated it had the latest driver. Is there something else I can do?

Do I have to uninstall the AMD chipset drivers or can I just run the driver that was at the site. There are some microsoft hotfixes that came with it would I install those first? If I uninstall the drivers I will not be able to use the usb mouse until I reinstall the drivers.:hide:
 

·
Registered
Joined
·
430 Posts
Discussion Starter #10
I uninstalled comodo, and I updated the driver for the chipset. I was unable to find another driver for the wifi ... don't know what to do about that. The system is still crashing.:facepalm:
 

·
Windows Specialist, Microsoft Support, BSOD Kernel
Joined
·
588 Posts
EDIT: I know you already ran driver verifier, but please run it again.


Please run driver verifier using the following settings for 48 hours.
  • Special Pool
  • Force IRQL checking
  • Pool Tracking
  • Deadlock Detection
  • Security Checks
  • Miscellaneous Checks
  • Power framework delay fuzzing
  • DDI compliance checking

Warning: driver verifier could cause boot issues and/or performance issues.
  • Make sure that you have recovery media, if needed you can create it.
  • Configure a restore point (see step 1 in the driver verifier link) prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)
  1. In normal mode open an administrator command prompt and enter the below command
  2. In safe mode open an administrator command prompt and enter the below command
  3. On 3 boot failures, you'll boot automatically to the recovery options,
    • click Troubleshoot
    • go to the advanced options
    • choose command prompt
    • enter the below command
  4. Boot with the recovery media, see above 4 steps in option 3.
  5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier
Code:
verifier /reset


Crashed when running driver verifier
  1. Reset driver verifier
  2. Boot in normal mode if necessary
  3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs


Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.

The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

Code:
verifier /query
If the command gives a result similar to this, it means driver verifier is running.


 

·
Registered
Joined
·
430 Posts
Discussion Starter #15
I'm not sure I'm doing the verifier right. I followed the reset instructions the best I could. I been having it run to put the 48 hours in ... that will be tomorrow evening. The system did crash, sometime during the time it was running, but it rebooted itself. I did the query in the cmd prompt and it looks like it is still running.

I used the AV removal tool and comodo was completely removed. Thank you for that link.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,370 Posts
I'm not sure I'm doing the verifier right. I followed the reset instructions the best I could. I been having it run to put the 48 hours in ... that will be tomorrow evening. The system did crash, sometime during the time it was running, but it rebooted itself. I did the query in the cmd prompt and it looks like it is still running..
If the system restarted, it means that you likely encountered a BSOD.

Please get the dump file. The filename of a dump contains the date.

Press the WIN + X keys. Select "Command Prompt Admin".

Type or paste the following line into the CMD screen -

Code:
[font=lucida console]md "%userprofile%\desktop\minidump" & copy %windir%\minidump "%userprofile%\desktop\minidump" & %systemroot%\explorer.exe /e,"%userprofile%\desktop\minidump"
[/font]
This is what the entire line looks like - be sure to copy it from the above CODEbox - VERY IMPORTANT.

md "%userprofile%\desktop\minidump" & copy %windir%
\minidump "%userprofile%\desktop\minidump" & %systemroot%
\explorer.exe /e,"%userprofile%\desktop\minidump"
Windows Explorer will open to the Desktop \minidump folder. Zip up that entire folder and attach to your next post.

I used the AV removal tool and comodo was completely removed. Thank you for that link.
You're welcome.

Removal tools are very important to use.

Regards. . .

jcgriff2

`
 

·
Registered
Joined
·
430 Posts
Discussion Starter #17
The computer crashed a whole lot during the 48 hours. It would reboot itself each time and it looks like the verifier continued to run.
 

Attachments

·
Registered
Joined
·
430 Posts
Discussion Starter #18
Instructions state to bump the thread if no response in 48 hours.:nonono::cry:
 

·
Windows Specialist, Microsoft Support, BSOD Kernel
Joined
·
588 Posts
There are some microsoft hotfixes that came with it would I install those first? If I uninstall the drivers I will not be able to use the usb mouse until I reinstall the drivers
You will have to install those hotfixes first, Gigabyte support page mentions installing them is a requirement to be able to install the chipset updates successfully.


I've looked into the last 10 dumps, although they're not a result of driver verifier they look to be caused by the AMD chipset drivers.
 

·
Registered
Joined
·
430 Posts
Discussion Starter #20
I saw that about installing the fixes first. I did installed the hotfixes first. I did not uninstall the old chipset drivers. The new drivers saw the old and replace them. Should I uninstall everything and start again? It would mean using the ps/2 mouse and keyboard because there will be no drivers for the usb.
 
1 - 20 of 42 Posts
Status
Not open for further replies.
Top