Bug Check -way over my head

[crippledman]

Recently my computer will reboot on its own, even when it is idle. It doesn't happen a lot, but I am concerned about it. I went to the Event Viewer and it seems to be a Bug Check. I googled the debugging message which I didn't understand. I only learned about how over my head problems with dump files are.     My computer has a i7-2600 CPU, 8 gigs of ram, AMD Radeon HD 6770 1 gig ram video card and running Windows 7 Home Premium.

This is the message from the Event Viewer:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000406f8, 0xfffff88004ab3ec3). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010712-16348-01.

I will appreciate any help I can get in locating the problem causing the computer to reboot. By the way the only memory dump I could find in Windows was minidump and it won't let me access it.

Thank you,
Bill

[Allan]

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

[crippledman]

Thank you Allan for responding. Below is the BSOD.txt:

==================================================
Dump File         : 010812-29796-01.dmp
Crash Time        : 1/8/2012 4:00:33 AM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000406f8
Parameter 4       : fffff880`0580838c
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+838c
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010812-29796-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,312
==================================================

==================================================
Dump File         : 010712-16348-01.dmp
Crash Time        : 1/7/2012 2:48:51 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000406f8
Parameter 4       : fffff880`04ab3ec3
Caused By Driver  : atikmdag.sys
Caused By Address : atikmdag.sys+4eec3
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010712-16348-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,312
==================================================

==================================================
Dump File         : 010612-23758-01.dmp
Crash Time        : 1/6/2012 6:21:35 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000406f8
Parameter 4       : fffff880`05914ec3
Caused By Driver  : atikmdag.sys
Caused By Address : atikmdag.sys+4eec3
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010612-23758-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,376
==================================================

==================================================
Dump File         : 010612-32151-01.dmp
Crash Time        : 1/6/2012 2:42:26 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000406f8
Parameter 4       : fffff880`062c113b
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+313b
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010612-32151-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,376
==================================================

==================================================
Dump File         : 010612-30716-01.dmp
Crash Time        : 1/6/2012 2:17:56 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000406f8
Parameter 4       : fffff880`05909e8b
Caused By Driver  : atikmdag.sys
Caused By Address : atikmdag.sys+61e8b
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010612-30716-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,376
==================================================

[patio]

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

Courtesy MSDN.

DLoad and run MemTest...let it run at least an hour.
Any errors at all and you have a bad stik of RAM.
No errors then we need to lookat/test other hardware components.

[crippledman]

I ran the MemTest and it passed with no errors. I connected a new wireless router about the same time this started happening. It seems to be working great, but could this be part of the problem? The router is a Cisco Linksys E-4200 and the firmware has been updated.

Thanks

[Allan]

The errors point to an issue with the display driver and/or direct-x. Download the latest driver for your system from the ATI website (assuming it's a desktop system) and the latest direct-x release. Then UNINSTALL the current ATI driver and the Catalyst Control Center (http://support.amd.com/us/kbarticles/Pages/GPU57RemoveOldGraphicsDrivers.aspx). Reboot. Then reinstall the new driver (and control center, if you so choose) as well as direct-x.

[crippledman]

Well Allan,  I have done what you have told me to so I guess I may have to wait a few days to know for sure whether drivers were the problem. I ran the dxdiag and it showed no problems. If I have any problems I will be back, otherwise I will check back in a few days to update you and close this post as resolved! In the mean time, thank you so much for your patience and advise. You provide a great service and it is very much appreciated.

[Allan]

Please do post back and let us know. Obviously something caused the problem and there are other diagnostic steps we can take if needed. But there is no doubt your blue screen error messages above clearly point to the display driver and direct-x. Good luck.

[crippledman]

Well, I left for awhile and came back to see that the computer had rebooted again. The below are a couple of the last items in the Event Viewer at the time of shut down or reboot. I don't know if these will help you or not.

Error
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin,  Source:  Kernel-EventTracing,, Event ID: 3,
Catagory: Session

Message:  Session "ReadyBoot" stopped due to the following error: 0xC0000188


Warning
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin,  Source:  Kernel-EventTracing,  Event ID: 4,
Catagory: Logging

The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

Thank you.

[patio]

Who else uses this PC ? ?
Someone has been foolin around with readyboost...which is a snake oil approach of using a USB stik to increase performance...
Somehow they have buggered it and it's causing these errors...that is if MemTest gave you a clean bill of health...

[BC_Programmer]

Who else uses this PC ? ?
Someone has been foolin around with readyboost...which is a snake oil approach of using a USB stik to increase performance...
Somehow they have buggered it and it's causing these errors...that is if MemTest gave you a clean bill of health...

ReadyBoot, not ReadyBoost.

[crippledman]

While you guys were posting my computer rebooted again. It reboots too fast to read the comments on the blue screen. Anyway, below is the message I received when the computer started back up tell me the computer had recovered from a quick shut down.

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   1033

Additional information about the problem:
  BCCode:   7f
  BCP1:   0000000000000008
  BCP2:   0000000080050031
  BCP3:   00000000000406F8
  BCP4:   FFFFF88006380033
  OS Version:   6_1_7601
  Service Pack:   1_0
  Product:   768_1

Files that help describe the problem:
  C:\Windows\Minidump\010812-16224-01.dmp
  C:\Users\Bill\AppData\Local\Temp\WER-30482-0.sysdata.xml

[crippledman]

I rebooted into safe mode and checked the Device Manager. It showed on my network adapters that my wi-fi was enabled and my Ethernet was disabled, which is the opposite of what I wanted. I enabled the Ethernet and disable the wi-fi as I am connected by an Ethernet cable. Could this be the problem, or part of it?

[Allan]

Please run the blue screen viewer again (just post the two or three newest events). Thank you.

[patio]

ReadyBoot, not ReadyBoost.

Whooops...sorry.