Computer Freezes With Loud Buzzing Noise

Toggle sidebar Toggle sidebar
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560
Before I begin, I've looked at other threads with no solution so just to start out, the buzzing noise is coming through my headphones connected into the computer, not the computer itself.

Ok, so I just built myself a 650 dollar gaming pc, yesterday and I've been having some issues with it. I've never overclocked it and it runs fine when I'm not doing anything intensive, like playing Watch Dogs. So when I launch a game, it doesn't do it right away, but 5 minutes into me playing the game, the whole screen freezes and their is a loud buzzing noise in my headset. It's sort of like a blue screen of death only without the blue screen. All my drivers are up to date and all the fans are working inside the computer. I started out with Windows 8.1 and it happened all the time, so I eventually downgraded to Windows 7 and it still does it, so I don't think its an OS issue.

My Computer Specs:
CPU: AMD Fx-6300 3.5GHz 6-Core Processor
Motherboard: MSI 970A-G43 ATX AM3+
Ram: Crucial Ballistix Sport 4GB DDR3-1600
Storage: Sandisk Ultra Plus 128 GB SSD and Seagate Barracuda 1 TB HDD
Graphics Card: MSI Radeon R9 270x 2GB Twin Frozr
Power Supply: Corsair Builder 500w 80+ Bronse
Wireless Card: TP-Link TL-WN781ND

The computer is well cooled but I'm wondering if the stock CPU cooler is tending to make the cpu overheat or something. I can hear it clearly running as fast as it can (sounds like a dying cat, but that aint relavant) when I play an intensive game. I hope I've provided enough information to find out the problem, because I haven't been able to enjoy my new, fast pc because of all this mess!
 
Solution
J
yep, it will not fix the problem but help isolate the cause down to the graphic system/power.
(or malware drivers in you addons to your browser)

lots of problems with the various oem AMD overclocked versions of cards.
cards fail at the overclocked memory rates, but work if you underclock them, the drivers fail at the overclocked rates but.
just lots of various problems with them. The last time I got a overclocked AMD card it took a year before I was able to use the overclock without a lot of driver problems. By that time new better card had come out. I now don't get the overclocked versions but look for better cooling solutions and just don't have the problems.

Sort by date Sort by votes
Shaun o

Shaun o

Illustrious
Oct 7, 2007
6,113
1
41,960
So the game freezes ect, no blue screen, or exit out of the current game your playing. just a loud static scraping sound.
Does it go Du Du Du Du Du by any chance when it goes down and then freeze. ?
Does it only do this when playing a game, or any game.
But not when using the internet, playing music or videos on You tube ect.?
Is it random amount of time where it crashes or after a set time of using or playing a game.?
If you can answer all of these Might be able to pin the problem down.


 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


Yes the game freezes, no blue screen, no exit ability. It has done it before when I watch videos on youtube or do anything that uses a lot of resources. It's pretty much a random amount of time and never comes exactly at a certain time.
 
Upvote 0 Downvote
JobCreator

JobCreator

Honorable
Apr 18, 2013
1,077
0
11,660
You may find that sometimes it stops and you'll get a Windows message on your taskbar saying "The graphics driver has crashed and has recovered." I can promise you it's not the video card or the drivers. I struggled with this problem for months on my home PC and until I replaced the motherboard, it never stopped. I replaced the video card, still happened. I replaced the processor (mostly because I wanted an upgrade) and it never stopped. I upgraded my RAM in the process as well and that didn't fix it. I ended up getting a new motherboard and everything quit. It's the motherboard.
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


I just got this new computer and wanted to have some fun with it but since it crashes and you said to RMA it, I was wondering how long it would take to get my motherboard back if I sent in on Tuesday express shipping.
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


Yea No Luck
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


So are you absolutely sure its my motherboard? Because I mean, the chipset heat sink is pretty small. So maybe I should just replace the heat sink and see what happens? Or should I just send it in and it continues not to work just get another heat sink. Also, can you even "upgrade" a motherboards heat sink? Or what you get is what you get.
 
Upvote 0 Downvote
JobCreator

JobCreator

Honorable
Apr 18, 2013
1,077
0
11,660
Well, the choice is yours, young Jedi. But, I'm 99.999% positive it's the motherboard. You can try to replace parts one by one, but you're going to end up rebuilding the entire machine to no avail. The sooner you get a replacement, the sooner you can enjoy your rig. You don't HAVE to take my advice. I mean, if anyone else wants to chime in here, feel free. I'm just telling you that I had the exact same issue with a 970A board and until I replaced it, the problem never stopped.
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


Ok, I think I'm gonna take your advice cause I can see you know your stuff. When I get it back and it works I'll make sure to pm you a big thanks!
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


I just received my new MSI Motherboard Replacement in the mail and it still crashes. So either I got another crappy motherboard from msi or its not the motherboard. Do you have any of solutions?
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


Is there a way I could test my graphics card for the errors then?? Like what kind of software could I use. I've been able to stress test my GPU before and my computer never crashed by the way.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
when a system locks up as you describe, it is locked up in the graphic driver code.
I have had this happen to my system many times and it was not caused by the motherboard.

to figure out the problem, you have to do the following:
1. Set your system to do a kernel dump rather than a minidump
2. enable verifie.exe debugging flags to force the system to save certain data structures
3. set a registry key to allow you to force a memory dump via the keyboard.

next time the system locks up, you hit some keys on your keyboard and a memory dump is created that contains the state of your machine. You can post the memory dump and someone can look at it with the windows debugger as to why it was locked up.

most of the time it is just a stupid driver problem.

info on force a memory dump:
http://www.sevenforums.com/bsod-help-support/174768-force-memory-dump.html
how to use verifier.exe
http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


Ok, so I did everything you said, According to the Crash Dump, it says there is an error from ATITool64.sys and the symbol name is ATITool64+6192
*Edit: I removed the ATI Tool driver but the problem consists. Any other solutions?
Here's the crash dump file:

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Dean Mysliwiec\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`0304d890
Debug session time: Thu Sep 18 14:31:16.736 2014 (UTC - 6:00)
System Uptime: 0 days 0:00:09.672
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
...............
Loading User Symbols


************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D6, {fffff98001485000, 0, fffff8800459a192, 0}

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool64.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ATITool64.sys ( ATITool64+6192 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98001485000, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8800459a192, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80002e0a000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 46b9f272

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffff98001485000

FAULTING_IP:
ATITool64+6192
fffff880`0459a192 66833800 cmp word ptr [rax],0

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD6

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff80002efdbf0 to fffff80002e7fbc0

STACK_TEXT:
fffff880`0317e888 fffff800`02efdbf0 : 00000000`00000050 fffff980`01485000 00000000`00000000 fffff880`0317e9f0 : nt!KeBugCheckEx
fffff880`0317e890 fffff800`02e7dcee : 00000000`00000000 fffff980`01485000 00000000`00000000 fffff980`01484ff0 : nt!wcsncat_s+0x2d7f8
fffff880`0317e9f0 fffff880`0459a192 : 00000001`0000000a 00000040`00000000 ffff0001`0000000c 00000098`00000011 : nt!KeSynchronizeExecution+0x28be
fffff880`0317eb80 fffff880`04598bf2 : 00000000`000000b0 fffff800`0331da55 fffff8a0`0072ad50 00000000`00000000 : ATITool64+0x6192
fffff880`0317f050 fffff880`04598b0b : fffff880`0317f0b0 fffff880`0317f0b0 fffff8a0`0072ae00 00000000`000000b0 : ATITool64+0x4bf2
fffff880`0317f0b0 fffff880`04595da3 : 000a541e`00000000 fffffa80`05d342e0 fffff880`045952f0 fffff980`01484ff0 : ATITool64+0x4b0b
fffff880`0317f0f0 fffff800`02f81d45 : fffff880`0317f720 fffff880`0317f6e8 00000000`00000000 fffff880`0317f5c4 : ATITool64+0x1da3
fffff880`0317f5a0 fffff800`032663f5 : 00000000`00000000 fffffa80`05d34b40 00000000`00000002 fffffa80`0461d3c0 : nt!DbgSetDebugFilterState+0x1885
fffff880`0317f5e0 fffff800`0326d941 : fffffa80`0461d3c0 fffffa80`0461d3c0 00000000`00000000 00000000`00000000 : nt!EtwEnableTrace+0x12e5
fffff880`0317f660 fffff800`0326eed2 : fffffa80`0461dd90 fffffa80`0461d3c0 00000000`00000002 fffffa80`0461d690 : nt!ExCreateCallback+0x2981
fffff880`0317f810 fffff800`0326f36c : fffff800`03081700 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExCreateCallback+0x3f12
fffff880`0317fa80 fffff800`02f82802 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!ExCreateCallback+0x43ac
fffff880`0317fad0 fffff800`02e89261 : fffff800`02f82500 fffff800`03176c01 fffffa80`039f4000 5c8b4800`063d7c8c : nt!DbgSetDebugFilterState+0x2342
fffff880`0317fb70 fffff800`0311b73a : 05058d48`38ec8348 fffffa80`039f4040 00000000`00000080 fffffa80`039e1040 : nt!KeReleaseInStackQueuedSpinLock+0x2f1
fffff880`0317fc00 fffff800`02e708e6 : fffff880`009b3180 fffffa80`039f4040 fffff880`009be040 c5870f00`010000ff : nt!PsCreateSystemThread+0x1e6
fffff880`0317fc40 00000000`00000000 : fffff880`03180000 fffff880`0317a000 fffff880`0317e8a0 00000000`00000000 : nt!KeInitializeSemaphore+0x25a


STACK_COMMAND: kb

FOLLOWUP_IP:
ATITool64+6192
fffff880`0459a192 66833800 cmp word ptr [rax],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ATITool64+6192

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ATITool64

IMAGE_NAME: ATITool64.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
---------

 
Upvote 0 Downvote
PIEapple

PIEapple

Reputable
Jul 8, 2014
691
1
5,360


This link will help you slove this problem.
http://www.sevenforums.com/bsod-help-support/277992-bsod-playing-wow-error-0x0000007e-error-0x000000d6.html
 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


I removed it but the problem continues. It's gotten worse too. It doesn't just do it when playing games but I can't install any origin games without it freezing when it says "downloading", I can't watch youtube videos without it crashing, and I can't even view a simple pdf without it crashing.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
turn off hardware acceleration in your browser and in your adobe software viewer.
until you get the problem worked out.
-you need to put the actual memory .dmp file on a cloud server



 
Upvote 0 Downvote
xfiremadex

xfiremadex

Reputable
Aug 29, 2014
33
0
4,560


So when I turn off hardware acceleration, it's gonna supposeably stop the lock ups in my browser, but I really need a solution for all the lock ups. I guess I'm gonna have to call up a computer repair man to come fix my pc.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
yep, it will not fix the problem but help isolate the cause down to the graphic system/power.
(or malware drivers in you addons to your browser)

lots of problems with the various oem AMD overclocked versions of cards.
cards fail at the overclocked memory rates, but work if you underclock them, the drivers fail at the overclocked rates but.
just lots of various problems with them. The last time I got a overclocked AMD card it took a year before I was able to use the overclock without a lot of driver problems. By that time new better card had come out. I now don't get the overclocked versions but look for better cooling solutions and just don't have the problems.



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom