Navigation section

Windows 7 Random BSOD when Playing FarCry 3

K

Karol3

New Member
Joined
Dec 8, 2012
Messages
40
I got a random BSOD when playing Far Cry 3 several times, I want to know if its a random BSOD or if something is going on, the required zip file is attached with the windows 7 diagnostic tool logs, rammon and SPD screen shot.

Thank you.


Link Removed


EDIT: Please use the attachedments in the "inline" the other one is just the Windows 7 Diagnostic without the Rammon and SPD screen shot.


Specs:

i7 3770k stock
Asus P8z77 Deluxe Mobo
16gb Corsair Vengeance Blue 1600mhz
Samsung 830 SSD OS Drive
PNY 570GTX stock
650W Antec PSU
 


Attachments

Solution
usasma
We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than...
Click to expand...
Sort by date Sort by votes
We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
Click to expand...

Only 126 Windows Updates installed. Most systems have 150 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

You have 5 hard drives. What is the make/model/wattage and age of your Power Supply?

One of the BSOD's blames your USB 3.0 driver:
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
ASMedia USB 3.0 Hub driver
Link Removed
Click to expand...
Please replace the driver by:
- download a fresh copy of the driver from the motherboard manufacturer's website
- un-install the current drivers
- install the freshly downloaded drivers

The rest of the BSOD's are STOP 0x116 errors. Please follow these troubleshooting steps: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ctac32k.sys Wed Jul 2 04:38:22 2008 (486B3E7E)
Creative Audio Driver
Link Removed

AiChargerPlus.sys Wed Apr 18 21:17:35 2012 (4F8F67AF)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed



Analysis:
The following is for informational purposes only.
Code: 
[font=lucida console]**************************Mon Apr  8 07:52:11.797 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040813-12604-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:15:52.624[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1392b0 )[/B]
BugCheck [B]116, {fffffa8016e383a0, fffff88006d9b2b0, 0, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8016e383a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006d9b2b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr  2 13:48:50.636 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040213-12168-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 6:03:37.464[/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 [B]9F, {3, fffffa80124decd0, fffff80000b9c3d8, fffffa8018322010}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80124decd0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8018322010, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar 29 13:24:01.518 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032913-12885-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 3:18:18.345[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+9336ac )[/B]
BugCheck [B]116, {fffffa80139e0190, fffff880075706ac, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80139e0190, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880075706ac, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 14:33:45.309 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-12292-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:08:49.136[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa8018d42010, fffff88007602adc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8018d42010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007602adc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 14:23:24.086 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-12760-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:59:24.914[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa8018c77010, fffff88007547adc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8018c77010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007547adc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 13:23:05.485 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-12417-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:06:12.312[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa8017ace4e0, fffff88007536adc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8017ace4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007536adc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 13:13:02.504 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-12604-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 5:08:49.331[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa8018928350, fffff88007571adc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8018928350, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007571adc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3518[/B]
  BIOS Version                  0603
  BIOS Release Date             02/03/2012
  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]**************************Mon Apr  8 07:52:11.797 2013 (UTC - 4:00)**************************
[COLOR=RED][B]ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
ICCWDT.sys                  Wed Aug 18 04:27:45 2010 (4C6B9981)
bcmvwl64.sys                Mon Nov 22 08:58:19 2010 (4CEA76FB)
SmartDefragDriver.sys       Fri Nov 26 04:29:40 2010 (4CEF7E04)
btwl2cap.sys                Fri Feb 11 20:06:04 2011 (4D55DCFC)
btwdpan.sys                 Mon May 16 10:58:06 2011 (4DD13B7E)
btwavdt.sys                 Thu Jun 23 10:53:33 2011 (4E03536D)
btwrchid.sys                Thu Jun 23 10:56:51 2011 (4E035433)
btwaudio.sys                Wed Jul  6 18:39:13 2011 (4E14E411)
SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)
BCM42RLY.sys                Tue Jul 19 23:22:48 2011 (4E264A08)
e1c62x64.sys                Wed Jul 20 12:37:53 2011 (4E270461)
SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
mvxxmm.sys                  Mon Sep 19 07:31:37 2011 (4E772819)
mvs91xx.sys                 Mon Sep 19 07:31:51 2011 (4E772827)
mv91cons.sys                Mon Sep 19 07:36:08 2011 (4E772928)
ASUSFILTER.sys              Tue Sep 20 11:46:33 2011 (4E78B559)
btwampfl.sys                Tue Sep 20 13:14:26 2011 (4E78C9F2)
Rt64win7.sys                Tue Sep 27 10:50:33 2011 (4E81E2B9)
bcbtums.sys                 Tue Oct 18 14:37:25 2011 (4E9DC765)
asmtxhci.sys                Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 23:00:32 2011 (4EB203D0)
iaStor.sys                  Tue Nov 29 22:39:19 2011 (4ED5A567)
asahci64.sys                Thu Jan  5 00:08:19 2012 (4F053043)
iusb3hub.sys                Thu Jan  5 06:54:43 2012 (4F058F83)
iusb3xhc.sys                Thu Jan  5 06:54:45 2012 (4F058F85)
iusb3hcs.sys                Thu Jan  5 06:56:40 2012 (4F058FF8)
[COLOR=RED][B]AiChargerPlus.sys           Wed Apr 18 21:17:35 2012 (4F8F67AF)[/B][/COLOR]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
ndisrd.sys                  Wed May 30 23:03:33 2012 (4FC6DF85)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
SCDEmu.SYS                  Fri Aug 17 00:19:38 2012 (502DC65A)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
LGSHidFilt.Sys              Wed Aug 22 18:27:24 2012 (50355CCC)
emupia2k.sys                Tue Oct 30 04:17:39 2012 (508F8D23)
ctsfm2k.sys                 Tue Oct 30 04:17:48 2012 (508F8D2C)
ctoss2k.sys                 Tue Oct 30 04:18:10 2012 (508F8D42)
ha20x22k.sys                Tue Oct 30 04:21:18 2012 (508F8DFE)
ctaud2k.sys                 Tue Oct 30 04:22:05 2012 (508F8E2D)
ctprxy2k.sys                Tue Oct 30 04:22:11 2012 (508F8E33)
CTHWIUT.SYS                 Tue Oct 30 04:23:01 2012 (508F8E65)
CTEXFIFX.SYS                Tue Oct 30 04:23:42 2012 (508F8E8E)
CT20XUT.SYS                 Tue Oct 30 04:23:48 2012 (508F8E94)
HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
dump_iaStorA.sys            Mon Nov 19 15:09:40 2012 (50AA9204)
iaStorA.sys                 Mon Nov 19 15:09:40 2012 (50AA9204)
iaStorF.sys                 Mon Nov 19 15:09:43 2012 (50AA9207)
nvhda64v.sys                Wed Dec 19 00:41:41 2012 (50D15395)
aswRvrt.sys                 Wed Mar  6 18:21:43 2013 (5137CF87)
aswFsBlk.SYS                Wed Mar  6 18:22:01 2013 (5137CF99)
aswMonFlt.sys               Wed Mar  6 18:22:08 2013 (5137CFA0)
aswTdi.SYS                  Wed Mar  6 18:22:10 2013 (5137CFA2)
aswrdr2.sys                 Wed Mar  6 18:22:24 2013 (5137CFB0)
aswSP.SYS                   Wed Mar  6 18:23:05 2013 (5137CFD9)
aswSnx.SYS                  Wed Mar  6 18:23:10 2013 (5137CFDE)
nvlddmkm.sys                Thu Mar 14 21:37:00 2013 (51427B3C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar 29 13:24:01.518 2013 (UTC - 4:00)**************************
nvlddmkm.sys                Thu Mar 14 03:29:32 2013 (51417C5C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 14:33:45.309 2013 (UTC - 4:00)**************************
bcmwl664.sys                Wed Oct 26 22:45:09 2011 (4EA8C5B5)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
aswRvrt.sys                 Thu Feb 28 03:25:36 2013 (512F1480)
aswVmm.sys                  Thu Feb 28 03:25:39 2013 (512F1483)
aswFsBlk.SYS                Thu Feb 28 03:25:47 2013 (512F148B)
aswMonFlt.sys               Thu Feb 28 03:25:53 2013 (512F1491)
aswTdi.SYS                  Thu Feb 28 03:25:58 2013 (512F1496)
aswrdr2.sys                 Thu Feb 28 03:26:09 2013 (512F14A1)
aswSP.SYS                   Thu Feb 28 03:26:55 2013 (512F14CF)
aswSnx.SYS                  Thu Feb 28 03:27:00 2013 (512F14D4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 13:13:02.504 2013 (UTC - 4:00)**************************
mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswRvrt.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.
Link Removed
Link Removed
Link Removed
aswrdr2.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.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswRvrt.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.
aswVmm.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.
Link Removed
Link Removed
Link Removed
aswrdr2.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.
Link Removed
Link Removed
Link Removed
 


Upvote 0 Downvote
Solution
Hi thank you for the speedy reply.

My PSU is a two year old Antec 650watt Model EA-650, I didn't see a serial number.

I have updated the ASMedia USB 3.0 Hub driver to the latest version from here Link Removed

I tried to update the creative drivers but I seam to have the latest version already based on the auto update program and their official website. The AI charger driver is connected to the ASUS AI SUITE II so i have disabled it through the program so it will not run anymore.


As for the STOP errors I did have a filthy gpu because there is construction in my house and it did have over heating a week back. I will update the gpu drivers once new ones come out.
 


Upvote 0 Downvote
PSU specs look OK to me - as long as you don't have a bunch of other stuff attached to the system.

Creative drivers may be a problem, but let's wait and see what happens before blaming them.

If the driver still loads, I would suggest uninstalling the AI charger driver rather than disabling it
If it doesn't load, then it should be OK (we haven't seen a lot of problems with this particular driver recently).

If you have the latest video drivers you may want to uninstall them and then install a fresh copy (to help rule out any corruption of the existing driver installation)

Then we wait to see if the BSOD's have stopped......
 


Upvote 0 Downvote
the driver does not load it is disabled, if there are more bsods i will post back here.
 


Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

G
  • Solved
Getting BSOD when playing Battlefield 2042 on wondows 11 beta
Replies
4
Views
7K
sophiakaile49
sophiakaile49
joelb
  • Solved
Windows 10 BsoD when playing games with bluetooth controller
Replies
1
Views
1K
kemical
kemical
A
  • Question Question
Windows 8 Win 8.1 Random BSOD When Playing
Replies
15
Views
4K
AleXu224
A
KxKrucify
  • Solved
Windows 8 Always get BSOD when playing certain games
Replies
7
Views
2K
KxKrucify
KxKrucify
R
  • Solved
Windows 7 BSOD when playing games or doing nothing! :D
2 3
Replies
52
Views
6K
kemical
kemical
Back
Top