Windows 10: GPU Related BSOD

Hi,

I am getting some weird BSODs or freezes.

One of them occurs randomly when i open up GPU-Z, i have tried to see if anyone else suffer from this, and apparently no one does.
For me it's just, i can open it 40 times, and one of them might cause a total freeze. Think i had this issue with my old card as well.

Now the other issues is that i get BSOD when i Play at rare occassions.
Latest i got when Driver Verifier was on, though not caused by that, but in a Game not during Windows boot.

I want to blame the AMD Crimson drivers which i always had more issues with than latest Catalyst.
But as no one else has this issues, and my card always act weird sometimes, i am am starting to think it's something else causing the problems, not the Crimson drivers alone.

My GPU is: R9 380
Got latest current driver: 16.3.0
For what it's worth it did a Memtest86 test during the night some week ago, it was when my CPU was overclocked though (which it's not now as i want to focus on the GPU issue).
Memtest86 ran for 8:03:03 hours, 6 Pass, 8 GB, no errors.

:)

 

BSOD new GPU related? May it be software?

I just got an new issue. I just restarted my PC after freeze. It did freeze in freaking windows desktop... it is really not cool. Could it be caused by system, or only by bad hardware?

 

BSOD new GPU related? May it be software?

If you want help with the problem see the prior post to post the files for troubleshooting.

In order to evaluate the BSOD and computer environment certain files are needed for the troubleshooting.

These files include: msinfo32, dxdiag, drivers, installed, uninstalled, hosts, startup, mini dumps, event viewer, etc.

The default language first must be in English so that the files can be scanned and read.

This administrative command prompt will automatically collect the files and place them on the desktop. Once the files are on the desktop please use one drive or drop box to post share links into the thread.

Copy and past the whole command at one time:

copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery
/v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg
export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP
GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

There is one additional file that can be found using file explorer search: C:\Windows\MEMORY.DMP

Please post this file into the thread too with a one drive or drop box share link for troubleshooting.

 

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
Code: <ActivePartialProductKey>T83GX</ActivePartialProductKey> <ActiveProductKeyPid2>00331-10000-00001-AA717</ActiveProductKeyPid2> <OSVersion>10.0.10586.2.00010100.0.0.048</OSVersion> <ProductName>Windows 10 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>10586.th2_release_sec.160422-1850</BuildLab> <TimeZone>W. Europe Standard Time(GMT+02:00)</TimeZone> <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>03612-03311-000-000001-03-1033-10586.0000-1002016</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>05426-00206-271-091417-03-1033-9200.0000-3332015</ActiveVolumeCustomerPid> <OfflineInstallationId>478416578229153729541522505317249529233985674641085020669688720</OfflineInstallationId> <DomainJoined>false</DomainJoined>[/quote] Forum rules

 

Ah got same answer elsewhere before this, i didn't get an answer why my copy was counterfeit though.
Will have to look into this.

Any recommendations where to buy it cheap haha;P?

 

No recommendation, in most cases you're being ripped off when you buy a copy on a site like Amazon.

 

Ah, that's too bad, will have to keep my eyes open for some discount, they cost a fortune where i'm from*Sad

 

Okay now i activated Windows 10*Smile

should i use dm_logger or BSODInspector?

 

Doesn't matter a lot *Smile

Did you perform a clean installation to remove the modifications?

 

I did not, i however did install Windows 10 on a partition and try to open GPU-Z a lot, and it froze there as well (basically only had the latest GPU driver installed, nothing else).

Confused what the problem is for that, here is a thread i asked about it as well: GPU-Z AMD 380 can cause PC Freeze very rarely. | TechPowerUp Forums

Though, the other crashes i have had (Special Pool errors) Are NOT from GPU-Z, those are with Driver Verifier on, and i think it's caused by using the GPU (gaming etc) and AMD VCE (OBS Studio) at the same time, though it's not easily reproduced, but it has occurred with those two working both times. I have done few tests with both separately but nothing happened, but as i said it's not easily reproducible so that doesn't mean it doesn't happen.

I did remove AutoKMS which i guess is the modification you talk about*Smile

 

AutoKMS is an executable that brings the modifications for activation, removal of it does NOT remove the modifications.

 

Ah i see.

Well i got a temporary Windows 10 on the same Drive i can shift to for testing, it's hard for me to reset as i got ton of data i need to organize etc.
But as said, GPU-Z still crashes, I would assume that the other crashes would as well, but that i haven't confirmed.
Would like to first solve the GPU-Z crash which has haunted me, then move on to the other things*Smile

 

FYI, I would advice that you seek for assistance on 1 forum at a time to prevent suggestions colliding against each other causing more problems where some users would blame volunteers that they made things worse because of suggestion colliding, I speak of experience as I've been blamed for such a thing while my suggestion was the solution.

 

Ah, i see.

Well thanks for mentioning it will keep it in mind.
My reason for contacting there first was, well they made GPU-Z.

But then i got more BSOD so i asked here and another place (which i will close to focus on this one).

 

Okay so well, what do we do?;P