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

Computer freezes randomly, always forced to hard restart


  • Please log in to reply
6 replies to this topic

#1 huntu

huntu

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 26 January 2018 - 11:23 PM

I've been having some problems with my computer for the past year where it would just freeze randomly. At first, it happened mostly in Rainbow Six: Siege. Now, however, it happens anytime. Just tonight, it froze a few times. It happens when I'm playing a game, exploring a webpage, or on any application. I've tried testing the RAM and reseating it, but it has no effect. 

 

In addition to random crashes, I often get BSODS, which range from bad pool header to many other error codes. Most of the time, they are all different errors.

 

This has been happening to me nonstop and I honestly don't think I can handle it anymore. I was playing PUBG earlier today and it froze while I was doing absolutely nothing other than talking to someone on my team. No action was taking place. 

 

I would highly appreciate anyone's help for fixing this problem. 

 

Specs:
​- FX-6300

- R9 270x 4GB

- 16GB DDR3 1600 RAM


Edited by huntu, 26 January 2018 - 11:23 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:36 AM

Posted 27 January 2018 - 07:02 AM

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 


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.

#3 huntu

huntu
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 27 January 2018 - 12:32 PM

Thanks for the reply, I've attached the BSOD Collection App .ZIP file.

 

Here is the Speccy link: http://speccy.piriform.com/results/GZlQn7uVjeizbECOpVyqgBO

Attached Files



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:36 AM

Posted 27 January 2018 - 03:54 PM

Your UEFI/BIOS (version 2701) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

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.
 

AMD OverDrive (AODDriver2.sys or AODDriver4.1) 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.

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.

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, etc) 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.

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.


Update chipset drivers to the latest, W10 compatible version available from the Asus support website for your model motherboard.

Check to see if there's a separate USB update for AMD - as that's the one that concerns me here.

 

Please uninstall MalwareBytes.  Once we've finished troubleshooting, feel free to download and install a fresh copy.

 

Beyond that, not much in the way of errors to see.  I did find a number of Live Kernel Events in the WER section of the MSINFO32 report.
When the number of Live Kernel Events significantly exceed the number of BSOD events there, I tend to wonder if it's a hardware problem.

As such, please start with these free hardware diagnostics:

 

Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
Please run ALL of the tests and let us know the results.
FYI - These are the tests and what we usually see for the reports:

1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
  - A - simtek.org memtest
  - B - Video memory stress test
  - C - Artifact Locator
  - D - OCCT - 4 built in tests for CPU, GPU, PSU
  - E - Video Memory Stress Test
7 - CPU tests:  run at least one test on your CPU and let us know the result.

 

You may also want to run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

If there's a low level driver problem (which sometimes acts like a hardware problem), this may help us find it.

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sun Jan 21 20:00:28.236 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012118-8875-01.dmp]
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:32:10.006
Probably caused by :memory_corruption
BugCheck 3B, {80000003, ffff9582941d1842, fffffc0845a917c0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 0000000080000003, Exception code that caused the bugcheck
Arg2: ffff9582941d1842, Address of the instruction which caused the bugcheck
Arg3: fffffc0845a917c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  remoting_host.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  2701
  BIOS Release Date             03/24/2016
  Manufacturer                  To be filled by O.E.M.
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             M5A97 LE R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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:

**************************Sun Jan 21 20:00:28.236 2018 (UTC - 5:00)**************************
amd_sata.sys                Wed Apr 11 10:40:24 2012 (4F8597D8)
amd_xata.sys                Wed Apr 11 10:40:27 2012 (4F8597DB)
usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
AODDriver2.sys              Tue Oct 29 20:58:36 2013 (527059BC)
ssdevfactory.sys            Thu Sep 24 21:12:39 2015 (56049F87)
wdcsam64.sys                Fri Oct  9 16:31:13 2015 (56182411)
bdfwfpf.sys                 Tue Feb  9 07:12:25 2016 (56B9D7A9)
trufos.sys                  Wed Jun 15 05:43:22 2016 (5761233A)
AtihdWT6.sys                Sun Jul 24 15:51:39 2016 (57951C4B)
sshid.sys                   Mon Dec 19 12:43:41 2016 (58581C4D)
rt640x64.sys                Thu Dec 22 21:52:09 2016 (585C9159)
mbae64.sys                  Wed Jan 11 12:08:00 2017 (58766670)
gzflt.sys                   Tue May  2 12:00:53 2017 (5908AD35)
avc3.sys                    Tue Aug 22 11:26:28 2017 (599C4D24)
farflt.sys                  Tue Sep  5 19:44:07 2017 (59AF36C7)
mwac.sys                    Thu Sep  7 12:04:14 2017 (59B16DFE)
atc.sys                     Wed Sep 13 10:55:19 2017 (59B946D7)
edrsensor.sys               Tue Sep 19 08:21:18 2017 (59C10BBE)
atikmpag.sys                Fri Sep 22 16:26:46 2017 (59C57206)
atikmdag.sys                Fri Sep 22 16:47:40 2017 (59C576EC)
mbam.sys                    Thu Oct 12 11:23:13 2017 (59DF88E1)
mbamswissarmy.sys           Fri Oct 13 14:58:51 2017 (59E10CEB)
BEDaisy.sys                 Tue Nov  7 21:53:13 2017 (5A027199)
MbamChameleon.sys           Tue Nov 28 23:17:27 2017 (5A1E34D7)


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=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
http://www.carrona.org/drivers/driver.php?id=trufos.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=farflt.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
atc.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.
edrsensor.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=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=mbamswissarmy.sys
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
http://www.carrona.org/drivers/driver.php?id=MbamChameleon.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.

#5 huntu

huntu
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 27 January 2018 - 06:11 PM

Haven't finished everything, so I'll just give an update on what I am doing here.

 

1. I looked into updating my BIOS, but for some reason the latest update is even older than what is currently on it. Version 2603 from 2015/07/24 is the latest BIOS update.

2. I have the latest Windows Updates installed.

3. I uninstalled AMD Overdrive because I never use it.

4. I uninstalled all the AMD/ATI stuff, and then I reinstalled the drivers using your instructions.

5. I am not overclocking.

6. I am unable to find any up to date chipset drivers. Perhaps I am looking at the wrong webpage? My motherboard is an ASUS M5A97 R2.0. Also, I am confused on what you mean by "separate USB update for AMD".

7. I've uninstalled MBytes.

 

I am currently in the process of downloading and running the tests from the carrona website you gave me.

 

I noticed from your post that the Analysis text has "MEMORY_CORRUPTION_LARGE" as a failure bucket ID. Is this anything significant?



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:36 AM

Posted 28 January 2018 - 02:26 PM

Your motherboard isn't supported by Asus for W10.  As such, they don't offer W10 drivers - which may give you compatibility issues.
Unfortunately, the test for compatibility issues is to try out the original OS and see if that works without trouble.

 

You may be able to find generic chipset updates at the AMD site, but I'm not able to locate them right now.

This might work - but I accept no responsibility if it messes up your system (I'm not familar w/AMD chipsets).
If you want a 2nd opinon - please post over in the Windows 10 forum or the Internal Hardware forum.

 

The failure bucket is important - but it's not necessarily going to tell us what's going on.

In this case, the MEMORY_CORRUPTION_LARGE is often seen with hardware problems - but not often enough for us to say for certain that it's a hardware issue (so it could also be software).

 

If we presume it's a hardware problem - then here's the procedure I suggest to prove that it's hardware:

 

My suggested way to diagnose a hardware problem (3 steps):

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [:(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

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.

#7 huntu

huntu
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 30 January 2018 - 07:59 PM

Okay, so I haven't tried your tests, but I think I understand the problem. According to PCPartPicker, my motherboard is not compatible with my CPU. I think I will either get a new motherboard or possibly upgrade to a different CPU + motherboard combo.

 

Thanks for your help, I highly appreciate it.






2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users