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, system stalls, and system reboots during gaming


  • Please log in to reply
6 replies to this topic

#1 add27

add27

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:43 PM

Posted 02 July 2012 - 07:48 PM

A few months previous, I installed a m5a97 asus motherboard along with some RAM and a new HDD. Crashing problems have continued to occur over the months since then. I have reinstalled windows 7 multiple times and attempted to test many of the components and updated most of the drivers. I know that my PCI bus, ATI I/O communications processor SMBus controller, and AsMedia XHCI controllers are out of date (according to driver detective), but I'm not sure how to update those as I have previously updated the BIOS and chipsets for the mobo.

Most frequently problems occur when gaming. In some cases the screen will freeze, and the system will lock up. This freezing will either require a manaul reboot, but often it does so of its own accord. Other games(TF2), however, have caused the screen to either scramble such that the display shows multiple angles cut together. There's often also an audible screech of static accompanying this disruption. After I close the program, other programs begin crashing (mumble, chrome,) and almost nothing will open properly.


I have tested the ram sticks both separately and together. In both cases, it has gone through 3 passes of memtest. I used prime95 to test the cpu, cleaned the heatsink after the temps were high, performed the prime test again, and observed reasonable temps. The video card that was in the system previously was removed and replaced with a 7850. Any help is appreciated.

Below is the zip file I was asked to submit:

http://www.mediafire.com/file/x76zyhtpya5bk7c/Windows7_Vista_jcgriff2.zip

BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:09:43 AM

Posted 02 July 2012 - 10:30 PM

I can find very little info pertaining to the system crashes/BSODs.

Crash dumps are apparently not being created: The reason is not clear, as the system settings are configured to record and save the dumps. It will therefore be necessary for you to record and post details that you see on-screen of the BSOD error messages.

Please disable "automatic restart on system failure":

It does seem likely that there may be a serious hardware issue and the system is unable to record and save the crash dumps. I would like to know whether or not you actually do get to see a BSOD error message at all.

Edited by AustrAlien, 02 July 2012 - 10:34 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 add27

add27
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:43 PM

Posted 05 July 2012 - 02:50 PM

ill upload the report again later, but i'm not convinced its recording in the dump. several times the bsod seems to stall before it says the dump is complete. recently, i've gotten the error codes

0x00000007F
0x00000003B (0x00000000C0000005, 0xFFFFF80002CCF3E6, 0xFFFFF880079765E0, 0x0000000000000000)

and

this just happened Physical memory dump FAILED at 0xC0000001

#4 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:09:43 AM

Posted 05 July 2012 - 03:30 PM

Clearly, the system is in fact BSODing and you are seeing the error messages.
  • That's a start.

Physical memory dump FAILED at 0xC0000001

Clearly there is also a problem with the dump failing!
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 add27

add27
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:43 PM

Posted 08 July 2012 - 05:32 PM

Not sure if this error is in the dump files is there. Sometimes it still isn't BSODing and just restarts, or it BSODs but doesn't complete the dump.

0x0000003D (0xFFFFF880b4E60D0, 0x0000000000000000, 0x0000000000000000, 0xFFFFF8800108EC94)

amd_sata.sys - address FFFFF8800108EC94 base at FFFFF88001082000

(Does the above have to do with my xhci sata drivers? I tried to update those, but something didn't work correctly.)


New Dumps:
http://www.mediafire.com/?xrzla79la0fqu68

#6 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:09:43 AM

Posted 10 July 2012 - 05:03 AM

Sorry about the delay: I've been kept busy, and unfortunately you ended up on the back-burner ... and now the day has got away from me.

I will do my best for you tomorrow ... but I can tell you now that I am having some trouble attempting to pinpoint a possible culprit or even get a clear idea of where to go from here.

Two minidumps were collected, one on each of the 6th and 7th of July:
  • 070612-15787-01.dmp
  • 070712-17425-01.dmp

========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\add27_BC\Windows7_Vista_jcgriff2 (2)\070712-17425-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 8 05:46:21.303 2012 (UTC + 10:00)
System Uptime: 0 days 21:15:10.864
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
UNEXPECTED_KERNEL_MODE_TRAP (7f)
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff880048907f2
BUGCHECK_STR: 0x7f_8
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
STACK_TEXT:
fffff800`00ba4d28 fffff800`02c89769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02c87c32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`048907f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00fff800`00b9cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdppm!C1Halt+0x2
FAILURE_BUCKET_ID: X64_0x7f_8_amdppm!C1Halt+2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`048907f2
BiosVersion = 1208
BiosReleaseDate = 04/18/2012
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = M5A97
BaseBoardVersion = Rev 1.xx
................................................................
Loading Dump File [C:\CactusIsland\add27_BC\Windows7_Vista_jcgriff2 (2)\070612-15787-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 7 04:32:28.576 2012 (UTC + 10:00)
System Uptime: 0 days 5:50:24.137
Probably caused by : memory_corruption ( nt!MiCheckForConflictingVadExistence+1d )
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002d0444d, Address of the instruction which caused the bugcheck
Arg3: fffff8800af6c020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!MiCheckForConflictingVadExistence+1d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d0444d fffff880`0af6c020 00000000`00000000
................................................................

Edited by AustrAlien, 10 July 2012 - 05:08 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:09:43 AM

Posted 11 July 2012 - 06:24 AM

One possible culprit, and something you don't mention having tested already, is the hard drive. Let's start there: I would like you to test the hard drive and also provide me with a Speccy report so that I can get a look at the S.M.A.R.T data for the HDD.

Please Publish a Snapshot using Speccy, and post a link to it in this thread.

This is a convenient and accurate way of providing us with details of your computer specifications.

From the msinfo32 report:
Model	ST2000DL 003-9VT166 SATA Disk Device
Test a Seagate manufactured hard disk drive using SeaTools for DOS run from a bootable CD.

:step1: Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO
[/list]
:step2: Burn the downloaded .ISO image to a CD using the appropriate burning software.
  • If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
      Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image

    When the CD has been burned and verified as successful, it will be bootable.

:step3: Boot from the CD.
  • (You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)
  • From Basic tests on the Main Menu, run the Short test and then the Long test.

    (The long test will take some considerable time to complete.)
    The results will be shown as either a PASS or FAIL.
    There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
[/list]Note: You may wish to view the following ...
Please let us know the results of the tests.
==============================================

Edit to add FYI: these may prove useful to you later ?

While I am looking at these links I will post them here now in case I forget later:

Edited by AustrAlien, 11 July 2012 - 06:42 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users