BSOD with Buzz sound

KaanNeedsHelp · 22 Aug 2017

So the BSOD started with my R9 280x graphs card whenever i play games or stress the pc it started to crash with that weird buzzing sound

Then i tried to RMA the r9 280x but failed; they said overheating damaged the card perm.

So i switched back to my old ATI HD6510 card after like 6 months it crashed today again after a long use

I'll leave minidumps and MEMORY.DMP files as attachments. Hope you can help...
Now i believe problem may not be the graphs card fault Thanks

Code:

XML view of an Critical Error Event 41
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 

  <EventID>41</EventID> 

  <Version>5</Version> 

  <Level>1</Level> 

  <Task>63</Task> 

  <Opcode>0</Opcode> 

  <Keywords>0x8000400000000002</Keywords> 

  <TimeCreated SystemTime="2017-08-22T14:34:17.554093900Z" /> 

  <EventRecordID>4415</EventRecordID> 

  <Correlation /> 

  <Execution ProcessID="4" ThreadID="8" /> 

  <Channel>System</Channel> 

  <Computer>KAAN-PC</Computer> 

  <Security UserID="S-1-5-18" /> 

  </System>


- <EventData>
  <Data Name="BugcheckCode">0</Data> 

  <Data Name="BugcheckParameter1">0x0</Data> 

  <Data Name="BugcheckParameter2">0x0</Data> 

  <Data Name="BugcheckParameter3">0x0</Data> 

  <Data Name="BugcheckParameter4">0x0</Data> 

  <Data Name="SleepInProgress">0</Data> 

  <Data Name="PowerButtonTimestamp">0</Data> 

  <Data Name="BootAppStatus">0</Data> 

  <Data Name="Checkpoint">0</Data> 

  <Data Name="ConnectedStandbyInProgress">false</Data> 

  <Data Name="SystemSleepTransitionsToOn">0</Data> 

  <Data Name="CsEntryScenarioInstanceId">0</Data> 

  <Data Name="BugcheckInfoFromEFI">true</Data> 

  </EventData>


  </Event>

Attachment 149987

BSODHunter · 23 Aug 2017

Attention:

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

KaanNeedsHelp · 23 Aug 2017

Adding required zip file.

Attachment 150165

BSODHunter · 24 Aug 2017

Hi,

1) U should start with testing your RAM. Please also check if the RAM modules are correctly seated.

Diagnostic Test

RAM TEST

Run MemTest86+ V5.01 to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ V5.01 needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

More Info here: https://answers.microsoft.com/en-us/...f-ecc7b7ff6461

Make a photo of the result and post it.

2) There where GPU errors detected a month ago, maybe this was with the old GPU:

Code:

2017-07-07 12:12:48  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-07 12:14:11  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-08 00:27:32  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-09 15:15:42  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-13 15:19:52  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-19 14:15:03  Warning: Display driver amdkmdap stopped responding and has successfully recovered.   
2017-07-25 17:08:06  Warning: Display driver amdkmdap stopped responding and has successfully recovered.

Please uninstall & reinstall GPU driver using DDU:

Display Driver Uninstaller: How to use
Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.

3) After reinstalling the GPU driver u should verify that the GPU has no Problems. Please use Furmark and monitoring tool for this to check temperatures and stability:

Diagnostic Test

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Take a Screenshot and post it here.

Speccy
Speccy gives you detailed information on every piece of hardware in your computer.

HWiNFO64
Hardware Info (HWiNFO) is a powerful system information utility designed especially for detection of hardware.

4) Next step should be checking all of your Harddisks because there are errors too on Harddisk3:

Code:

2017-07-04 21:31:22  Warning: An error was detected on device \Device\Harddisk3\DR8 during a paging operation.   
2017-07-04 21:31:22  Warning: An error was detected on device \Device\Harddisk3\DR8 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
2017-08-19 19:21:05  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Diagnostic Test

HDD TESTS

Run HDTune to check health and scan for errors.

Note

It may take some time, but look for signs of any errors or failure.

You can also run a disk or health check using CrystalDiskInfo or chkdsk. Refer to the tutorial for details of how to do this.

Take Screenshots of it and post it here.

5) Have a look on the Osbase idisplay application. Its shown in one of the bsod dumps:

Code:

0x00000139:    KERNEL_SECURITY_CHECK_FAILURE (7.07.2017 11:03:15) [Windows 10] 
 
CAUSED BY:     memory_corruption     
               ddkmd.sys [22.04.2017] * OSBASE WDDM Software driver * => http://osbase.com/idisplay/ 
 
PROCESS:       System

Please remove driver + software for testing purposes to see if the system runs stable