Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD, freezing issues


  • Please log in to reply
2 replies to this topic

#1 KelThuzad0398

KelThuzad0398

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:35 AM

Posted 16 September 2016 - 08:15 AM

I've had freezing issues with a custom-built computer ending in a BSOD this morning. The freezes usually happen while playing a game called Warframe, and the BSOD happened while starting the game. Two of the computer freezes happened yesterday. The freezing stops the sound and requires a restart. I thought it was an issue with overheating, but I'm not sure how to check that and temperature programs were reporting 110+ which I think is a broken sensor.

 

Custom built computer

Windows 7 x64 OEM

Nearly a year old desktop, hardware and OS

Sapphire Raedon R7 260X
AMD Athlon X4 860K Kaveri Quad-Core 3.7 GHz Socket FM2+ 95W AD860KXBJABOX Desktop Processor
EVGA 500 B1 100-B1-0500-KR 80+ BRONZE 500W
Deepcore Tesseract case
G.SKILL Ares Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 2133 X2 (16 GB RAM)
Seagate Desktop HDD ST1000DM003 1TB 64MB Cache
5 fans (2 intake, 3 exhaust)

 

Attached is the PERFMON, Sysnative File Collection, and a report of the bluescreen from Bluescreenview.

 

The overheating is from a different forum post, this post is to address the blue screen.

http://www.bleepingcomputer.com/forums/t/626741/computer-freezing-possibly-overheating/

Attached Files



BC AdBot (Login to Remove)

 


#2 KelThuzad0398

KelThuzad0398
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:35 AM

Posted 17 September 2016 - 11:10 AM

After 24 hours of running the driver verifier, no further BSODs or freezes have occurred. The verifier status is attached below.

Attached Files



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:35 AM

Posted 18 September 2016 - 04:56 AM

Cneck the temps by placing your hand near (BUT DO NOT TOUCH) the devices in question.

If it feels as if you'll be burned - then the temp in the sensor is correct.

BE VERY, VERY CAREFUL doing this - as I've gotten 2nd degree burns doing this!!!!

 

If it's an overheating issue, it likely involves your graphics card.

Please check the cooling of the graphics card, to include that the fan is working, that the cooler is free of dirt/dust, that the cooler is firmly attached to the GPU, and that the power plugs are firmly seated.

 

Also, monitor your system's temperatures with this free tool: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php )

In addition, FurMark should have a temp indicator - so when you run it you can watch the temps.

When you first start the system in the morning, start Furmark also - and watch what the temps do.

 

Here's the analysis from the reports.

 

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.
NOTE:  Lot's of Windows Update failures in the WER section of the MSINFO32 report

 

The WER section of the MSINFO32 report shows several BSOD's blaming your ATI video

In addition to checking it for overheating, be sure that you update to the latest, W7 compatible video drivers

 

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Windows systems.
[quote]NOTE:  these symptoms were from the previous release of OverDrive.  The new release uses the same driver name, but is dated from 4 November 2013.
[quote]
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLYhttp://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install".  Reboot for changes to take affect.

Sometimes the entry will remain in Device Manager even though you've removed it.  So, open up Device Manager and check for the AODDriver4.2.0 (it may have another number).  Right click on it and select "Uninstall".  If it asks to remove software, put a check in the box.  Then click on OK.
[/quote]
Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.



Also, please uninstall your wireless XBox controller.  It's xusb21.sys driver is known to cause BSOD's in some Windows systems.

Test to see if that helps to stop the BSOD's.

There is no updated driver for this device, so if it is causing the BSOD's your only recourse is to update to the new hardware that uses the xus22.sys driver (in other words, buy new stuff).

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Fri Sep 16 08:32:35.020 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091616-20919-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.23539.amd64fre.win7sp1_ldr.160902-0600
System Uptime:0 days 17:36:23.518
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )
BugCheck 100000EA, {fffffa800dfc3060, 0, 0, 0}
BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
Arguments:
Arg1: fffffa800dfc3060, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
BUGCHECK_STR:  0xEA
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
PROCESS_NAME:  HWMonitor.exe
FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
  BIOS Version                  F7
  BIOS Release Date             11/25/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 23 08:12:16.563 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\082316-18564-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.23455.amd64fre.win7sp1_ldr.160516-0600
System Uptime:2 days 9:03:11.672
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!TraceDxgkFunctionProfiler+d7f )
BugCheck 100000EA, {fffffa800f3a5a80, 0, 0, 0}
BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
Arguments:
Arg1: fffffa800f3a5a80, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
BUGCHECK_STR:  0xEA
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
  BIOS Version                  F7
  BIOS Release Date             11/25/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 12 20:48:35.700 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091215-14242-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600
System Uptime:2 days 16:27:46.199
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :atikmdag.sys ( atikmdag+28710 )
BugCheck 18, {fffffa800cd5ca40, fffffa8010f97500, 1, 1}
BugCheck Info: REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa800cd5ca40, Object type of the object whose reference count is being lowered
Arg2: fffffa8010f97500, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000001, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object?s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.
BUGCHECK_STR:  0x18
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: X64_0x18_CORRUPT_REF_COUNT_atikmdag+28710
  BIOS Version                  F7
  BIOS Release Date             11/25/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler




3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Fri Sep 16 08:32:35.020 2016 (UTC - 4:00)**************************
amdxata.sys                  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dc3d.sys                     Wed May 18 04:07:24 2011 (4DD37E3C)
SASKUTIL64.SYS               Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS               Thu Jul 21 19:03:00 2011 (4E28B024)
usbfilter.sys                Mon Feb 17 01:23:43 2014 (5301AAEF)
LHidEqd.Sys                  Tue Mar 18 20:20:53 2014 (5328E2E5)
LEqdUsb.Sys                  Tue Mar 18 20:20:55 2014 (5328E2E7)
LHidFilt.Sys                 Tue Mar 18 20:21:03 2014 (5328E2EF)
LMouFilt.Sys                 Tue Mar 18 20:21:03 2014 (5328E2EF)
RTKVHD64.sys                 Tue Jun 10 08:20:20 2014 (5396F804)
Rt64win7.sys                 Tue Jun 17 07:59:14 2014 (53A02D92)
amd_sata.sys                 Sun Mar 29 22:38:26 2015 (5518B722)
amd_xata.sys                 Sun Mar 29 22:38:28 2015 (5518B724)
MpFilter.sys                 Fri Oct 30 02:29:35 2015 (56330E4F)
amdhub30.sys                 Thu Jan 14 02:37:05 2016 (56975021)
amdxhc.sys                   Thu Jan 14 02:37:07 2016 (56975023)
cpuz139_x64.sys              Wed Jan 27 04:18:15 2016 (56A88B57)
AtihdW76.sys                 Wed Mar 30 01:00:37 2016 (56FB5D75)
WirelessKeyboardFilter.sys   Sat Jun 25 03:13:14 2016 (576E2F0A)
ALSysIO64.sys                Wed Jul  6 12:47:33 2016 (577D3625)
atikmpag.sys                 Wed Sep  7 10:00:50 2016 (57D01D92)
amdacpksd.sys                Wed Sep  7 10:18:53 2016 (57D021CD)
atikmdag.sys                 Wed Sep  7 11:10:40 2016 (57D02DF0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 23 08:12:16.563 2016 (UTC - 4:00)**************************
speedfan.sys                 Sat Dec 29 15:59:35 2012 (50DF59B7)
WirelessKeyboardFilter.sys   Wed Mar 16 03:48:01 2016 (56E90FB1)
atikmpag.sys                 Mon Jul 18 16:32:52 2016 (578D3CF4)
amdacpksd.sys                Mon Jul 18 16:50:52 2016 (578D412C)
atikmdag.sys                 Mon Jul 18 17:41:41 2016 (578D4D15)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 12 20:48:35.700 2015 (UTC - 4:00)**************************
amdhub30.sys                 Tue May 28 04:09:12 2013 (51A46628)
amdxhc.sys                   Tue May 28 04:09:14 2013 (51A4662A)
AODDriver2.sys               Tue Feb 11 06:06:52 2014 (52FA044C)
mbam.sys                     Wed Sep  3 13:50:25 2014 (540754E1)
amd_sata.sys                 Tue Sep 23 04:26:37 2014 (54212EBD)
amd_xata.sys                 Tue Sep 23 04:26:40 2014 (54212EC0)
MpFilter.sys                 Thu Feb 26 19:21:20 2015 (54EFB880)
AtihdW76.sys                 Mon Jul  6 21:23:25 2015 (559B2A0D)
atikmpag.sys                 Wed Jul 15 21:13:26 2015 (55A70536)
amdacpksd.sys                Wed Jul 15 21:23:04 2015 (55A70778)
atikmdag.sys                 Wed Jul 15 21:37:09 2015 (55A70AC5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 16 03:18:45.912 2015 (UTC - 4:00)**************************
xusb21.sys                   Thu Aug 13 18:10:17 2009 (4A848F49)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug  3 17:16:45.341 2015 (UTC - 4:00)**************************
amdhub30.sys                 Wed Jan 21 02:17:15 2015 (54BF527B)
amdxhc.sys                   Wed Jan 21 02:17:16 2015 (54BF527C)
AtihdW76.sys                 Mon May 18 12:48:42 2015 (555A17EA)
atikmpag.sys                 Mon Jun 22 21:10:51 2015 (5588B21B)
amdacpksd.sys                Mon Jun 22 21:20:23 2015 (5588B457)
atikmdag.sys                 Mon Jun 22 21:34:51 2015 (5588B7BB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug  1 00:27:00.090 2015 (UTC - 4:00)**************************
MBAMSwissArmy.sys            Mon Apr 13 15:29:19 2015 (552C190F)


http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS
http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=amdhub30.sys
http://www.carrona.org/drivers/driver.php?id=amdxhc.sys
cpuz139_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
WirelessKeyboardFilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
WirelessKeyboardFilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=amdhub30.sys
http://www.carrona.org/drivers/driver.php?id=amdxhc.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=amdhub30.sys
http://www.carrona.org/drivers/driver.php?id=amdxhc.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys




 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users