chance

New Member
Joined
Nov 2, 2014
Messages
4
Hey, I have a fairly old gaming computer, and it has been pretty good so far aside from a few minor hiccups. Recently, it crashed while I was playing a game of Dota 2, and it was unable to turn back on. I thought my power supply died, so I left it for a bit until I could repair it. A couple of days later, I hit the power button without hope, and it turned on. I assumed it had overheated, but didn't understand why it would take 2 days to turn back on. I resumed my typical computer-gaming and misc. fairly uninterrupted, until it crashes again without warning. Again, it wouldn't turn back on for the same 2 days. I turned it back on those 2 days later, and I have restrained from playing games for its own sake. I turned it off manually yesterday to see if it would turn back on, and it didn't, so I waited another 2 days for it to turn on again, and here I am now. I think its goes without saying that this is immensely troubling to me, and I obviously am not the most tech-savvy, however I suspect it is something to do with my hardware. I'm asking for tips for identifying the issue exactly, and why it's doing this. It may be worth noting I used a Windows 7 desktop gadget to identify how much ram I had been using during the second crash, and it said I was using 77% of my 16gbs of ram while idle, this has never occured before. My computer becomes very loud when I play games now, which I don't plan on doing until this is resolved.
Any help would be appreciated, and I would also appreciate instructions on how obtain any further information I may be needed to give to help my situation, again, I'm not the most tech-savvy.
Thanks.
 


Solution
Hello and welcome to the forum.
Perhaps, if it's crashing, it may be generating a blue screen with associated dump files which might help diagnose the issue.
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
...
Hello and welcome to the forum.
Perhaps, if it's crashing, it may be generating a blue screen with associated dump files which might help diagnose the issue.
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then……Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.

Additionally scan it with https://www.malwarebytes.org/mwb-download/
AND
Consider using some compressed air to free the heat sink and cooling fans from dust and debris
 


Solution
Hello and welcome to the forum.
Perhaps, if it's crashing, it may be generating a blue screen with associated dump files which might help diagnose the issue.
First make sure your machine is configured properly to facilitate the collection of .dmp files.


Then……Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.

Additionally scan it with https://www.malwarebytes.org/mwb-download/
AND
Consider using some compressed air to free the heat sink and cooling fans from dust and debris

I appreciate the reply and simplified instructions, I've attached the .dmp files
 


Attachments

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1c, 2, 0, fffff88001436cea}

*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Probably caused by : RTL8192su.sys ( RTL8192su+f9ac )

Followup: MachineOwner
Hi,
out of the four dump files sent 2 blamed USB3 drivers and two were the same as the above which is blaming a Realtek Wireless Network driver.
Looking through your system drivers and bios I see most date from 2012:
BiosVersion = 0902
BiosReleaseDate = 12/07/2011
please update to latest version making sure I have the correct motherboard and download page:
http://www.asus.com/uk/Motherboards/M5A97_EVO/HelpDesk_Download/

asmthub3.sys Thu Nov 08 17:36:35 2012: Asmedia ASM1042 USB 3 drivers please update (site is french click 'Telecharger'):
Link Removed

atikmdag.sys Wed Dec 19 20:38:55 2012: AMD GPU driver please update:
Link Removed

avgidsdrivera.sys Mon Oct 22 11:47:11 2012: AVG needs updating but this AV app is known for causing the odd issue. If bsod continues after updating try removing and installing MSE as it's ultra stable:
http://windows.microsoft.com/en-GB/windows/security-essentials-download

dtsoftbus01.sys Fri Jan 13 13:45:46 2012: Daemon Tools BSOD issues with Windows 7 please remove.

Rt64win7.sys Tue Aug 23 14:55:41 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet: Please update:
Link Removed

RTKVHD64.sys Tue May 22 11:19:20 2012: Realtek High Definition Audio Function Driver please update:
Link Removed

RTL8192su.sys Thu Aug 20 04:00:10 2009: Realtek RTL8192SU Wireless LAN 802.11n USB 2.0 Network Adapter Driver please update to most recent driver (2012):
Link Removed

Post any new dump files.
 


I turned off automatic power-down, and have had since little issues. My computer even shut down on its own for automatic updates that required a restart, and it booted up again without issue. However, I recently lost power for a few minutes, and it would not turn back on for the usual 2 days. I've attached the crash files as usual. It works fine when it's on, but something seems to be stopping it from turning on.
 


Attachments

Update! After another brief loss of power, the computer again wouldn't turn on. I figured I'd try to find the wire connecting the power button and the motherboard, and I did. I unplugged the wire to the motherboard and plugged it back in, and it turned back on. At least now I know how to turn it on without waiting two days.
Also, this popup has been occurring for a couple of weeks upon startup, I don't know if it's relevant to the issue I'm experiencing, and come to think of it again I should probably attach it to see with the pros if it is in fact relevant. Thanks again!
 


Attachments

  • Capture3.webp
    Capture3.webp
    11.3 KB · Views: 316
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1c, 2, 0, fffff88001436cea}

*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Probably caused by : RTL8192su.sys ( RTL8192su+f9ac )

Followup: MachineOwner
You have exactly the same dump files as before and I notice neither did you update any of the drivers I posted above. I'd try the bios first as this has many stability updates:
Link Removed
 


Back
Top