Windows 7 BSOD when starting certain games. Help appreciated!

R3DW1NG5

New Member
Joined
Nov 2, 2012
Messages
6
I have tried several different things to fix this issue. I completely checked my ram with a ram checking program. I have never really had a problem with my computer except for at certain times. Whenever I try to play Darkness II, Duke Nukem Forever, or COD MW3, the wonderful BSOD pops up. All of my info is attached. Thank you very much!
 


Attachments

Solution
Everything is good now. I flashed the bios for the motherboard to the newest that is available. Apparently, by default, the motherboard I have doesn't have firmware that completely supports AMD FX chipsets. As soon as I saw that online, I flashed the bios and now I no longer have BSOD issues. Thank you.
Not all reports that are needed have been uploaded. Please follow the instructions here: Link Removed

Please un-install the Western Digital software as it dates from 2008

Please
- download a fresh set of the following drivers
- un-install the current drivers (both the Linksys stuff and the ASMedia stuff)
- then install the freshly downloaded drivers (they are blamed in one of the memory dumps):
ae1000w7.sys Fri Jan 15 03:15:48 2010 (4B502434)
Linksys AE1000 High-Performance Wireless-N Adapter
Link Removed

asmtxhci.sys Wed Jun 1 22:27:46 2011 (4DE6F522)
Asmedia USB 3.0 driver
Link Removed

asmthub3.sys Wed Jun 1 22:27:58 2011 (4DE6F52E)
ASMedia USB 3.0 Hub driver
Link Removed

Just FYI - Win7 doesn't like wireless USB network devices. Here's my rant on the subject:
I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Fri Nov  2 16:21:19.129 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110212-20997-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:07:50.393[/B]
BugCheck Code: [B]BugCheck 101, {21, 0, fffff880009b3180, 4}[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck Info: [B]CLOCK_WATCHDOG_TIMEOUT (101)[/B]
Arguments: 
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE[/B]
  BIOS Version                  0801   
  BIOS Release Date             11/18/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 05:22:42.621 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110212-18595-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:13:02.885[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8005f0a060, fffff80000b9c3d8, fffffa80089a2010}[/B]
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by :[B]asmthub3.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005f0a060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80089a2010, The blocked IRP
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x9F_3_ae1000w7_IMAGE_asmthub3.sys[/B]
  BIOS Version                  0801   
  BIOS Release Date             11/18/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Fri Nov  2 16:21:19.129 2012 (UTC - 4:00)**************************
[B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B]
[B]ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)[/B]
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
AtiPcie.sys                 Mon Aug 24 04:25:26 2009 (4A924E76)
ae1000w7.sys                Fri Jan 15 03:15:48 2010 (4B502434)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmtxhci.sys                Wed Jun  1 22:27:46 2011 (4DE6F522)
asmthub3.sys                Wed Jun  1 22:27:58 2011 (4DE6F52E)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
RTKVHD64.sys                Tue Jun 28 07:09:04 2011 (4E09B650)
nvhda64v.sys                Thu Jul  7 12:21:14 2011 (4E15DCFA)
nvlddmkm.sys                Sat Oct 15 02:07:55 2011 (4E99233B)
SCDEmu.SYS                  Fri Aug 17 00:19:38 2012 (502DC65A)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
[/font]
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
 


I have installed the drivers and I am still unfortunately having issues. I personally hate wireless devices with my desktop, however I am stuck in a dorm that only has wifi at the moment :( And the Western Digital software is my external hard drive....Should that even be an issue?
 


Please zip up and upload the contents of C:\Windows\Minidump with your next post.

Get a wireless card that goes inside the desktop - that way you won't have to use the wireless USB device.
The cards inside the desktop aren't as problematic as the USB one's. You'll be looking for a PCI or PCIe card (depending on the available slots on your motherboard).

The Western Digital software isn't needed to use your external hard drive. As for it being an issue - yes, we see these older drivers from Western Digital causing BSOD's on Win7 systems. If there is some particular task that you do with the Western Digital software, let us know and we can suggest free alternatives that work (IMO) as well or even better.
 


Everything is good now. I flashed the bios for the motherboard to the newest that is available. Apparently, by default, the motherboard I have doesn't have firmware that completely supports AMD FX chipsets. As soon as I saw that online, I flashed the bios and now I no longer have BSOD issues. Thank you.
 


Solution
I'm glad to hear that you've fixed it. Thanks for letting us know!
 


Back
Top