Navigation section

Windows 7 Randomly happen while playing

rjnm

rjnm

New Member
Joined
Apr 28, 2013
Messages
8
Hi, i need some help here with this BSOD, it started a month ago with apparently no reason, now, sometimes it happens and others i just can play for hours with no crash.

What i would like to know if possible is if this crash is due to the graphic card, mobo or what!


Thanks in advance!
 


Attachments

Solution
usasma
Daemon Tools is the most likely problem here. Please:
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here...
Click to expand...
Click to expand...
Sort by date Sort by votes
Please provide this information so we can provide a complete analysis: Link Removed

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Click to expand...

Please also un-install the wireless USB XBox controller and physically remove the device from the system. These devices are known to cause BSOD's and there are no known driver updates for them.

Please follow these steps to troubleshoot the BSOD's: http://www.sysnative.com/forums/bso...-video-tdr-timeout-0x116-0x117.html#post29532

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! :

SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
Samsung printer driver
Link Removed

hotcore3.sys Mon Jan 21 08:33:19 2008 (47949F1F)
HotBackup by Paragon Software Group.
Link Removed




Analysis:
The following is for informational purposes only.
Code: 
[FONT=lucida console]**************************Fri Apr 26 18:49:31.030 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-19624-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:05:16.920[/B]
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :[B]nvkflt.sys ( nvkflt+31704 )[/B]
BugCheck [B]116, {fffffa80074c3010, fffff88004c82704, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80074c3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004c82704, 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_nvkflt.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2192[/B]
  BIOS Version                  A12
  BIOS Release Date             08/20/2012
  Manufacturer                  Alienware
  Product Name                  M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr 23 18:24:47.582 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042313-15022-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 17:53:19.457[/B]
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :[B]nvkflt.sys ( nvkflt+31704 )[/B]
BugCheck [B]116, {fffffa80102b21c0, fffff88000c31704, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80102b21c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88000c31704, 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_nvkflt.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2192[/B]
  BIOS Version                  A12
  BIOS Release Date             08/20/2012
  Manufacturer                  Alienware
  Product Name                  M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Apr 20 02:29:09.585 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042013-23197-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]4 days 7:41:06.475[/B]
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :[B]nvkflt.sys ( nvkflt+31704 )[/B]
BugCheck [B]116, {fffffa800eb5b3e0, fffff880041bc704, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa800eb5b3e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880041bc704, 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_nvkflt.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2192[/B]
  BIOS Version                  A12
  BIOS Release Date             08/20/2012
  Manufacturer                  Alienware
  Product Name                  M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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 Apr 26 18:49:31.030 2013 (UTC - 4:00)**************************
[COLOR=RED][B]SSPORT.sys                  Thu Aug 11 19:07:32 2005 (42FBDA34)[/B][/COLOR]
[COLOR=RED][B]hotcore3.sys                Mon Jan 21 08:33:19 2008 (47949F1F)[/B][/COLOR]
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]a1sv6adv.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B][/COLOR]
SynTP.sys                   Thu Aug  6 21:18:18 2009 (4A7B80DA)
[COLOR=RED][B]sptd.sys                    Sun Oct 11 16:55:14 2009 (4AD24632)[/B][/COLOR]
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iaStorV.sys                 Thu Jun 10 20:46:19 2010 (4C11875B)
btwampfl.sys                Mon Jul 12 21:41:18 2010 (4C3BC43E)
Accelern.sys                Fri Aug 20 14:04:57 2010 (4C6EC3C9)
stdcfltn.sys                Fri Aug 20 14:05:01 2010 (4C6EC3CD)
iaStor.sys                  Mon Sep 13 21:23:32 2010 (4C8ECE94)
L1C62x64.sys                Mon Sep 27 02:36:23 2010 (4CA03B67)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
CtClsFlt.sys                Wed Jan 19 22:20:46 2011 (4D37AA0E)
[COLOR=RED][B]nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)[/B][/COLOR]
Ak27x64.sys                 Tue Feb 22 11:29:32 2011 (4D63E46C)
bflwfx64.sys                Thu Mar 10 10:08:25 2011 (4D78E969)
stwrt64.sys                 Thu Mar 17 04:21:47 2011 (4D81C49B)
RtsPStor.sys                Thu Mar 24 04:04:09 2011 (4D8AFAF9)
nvBridge.kmd                Sun Jun 26 18:06:57 2011 (4E07AD81)
igdkmd64.sys                Wed Sep 26 15:49:04 2012 (50635C30)
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)
nvpciflt.sys                Thu Mar 14 21:37:25 2013 (51427B55)
nvkflt.sys                  Thu Mar 14 21:37:36 2013 (51427B60)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr 23 18:24:47.582 2013 (UTC - 4:00)**************************
[COLOR=RED][B]aos03fh1.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B][/COLOR]
[COLOR=RED][B]xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)[/B][/COLOR]
nvoclk64.sys                Tue Sep 15 17:59:25 2009 (4AB00E3D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Apr 20 02:29:09.585 2013 (UTC - 4:00)**************************
[COLOR=RED][B]a2q8iwxa.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B][/COLOR]
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
a1sv6adv.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
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
aos03fh1.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
a2q8iwxa.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.
 


Last edited:
Upvote 0 Downvote
Hello!! thanks, i bought an SSD drive so made a fresh install of W7, no problem until i install daemon tools, then two crashes, just can't believe it!..
BTW, i'm attaching the info you requested.
 


Attachments

Upvote 0 Downvote
Daemon Tools is the most likely problem here. Please:
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Click to expand...
Click to expand...

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is all controllers, not just the one that the SSD is attached to.
Click to expand...

These devices don't have drivers installed:
Not Available ACPI\SMO8800\1 The drivers for this device are not installed.

Not Available ACPI\CPL0002\2&DABA3FF&2 The drivers for this device are not installed.
Click to expand...
The first one is the ST Microelectronics Free Fall Sensor (also known as a Drop Sensor). The second one is the COMPAL Embedded System Control (I was unable to find a download for Win7 at Dell, but did find this link at Lenovo: Link Removed )

This is in addition to the stuff that I posted in my first post - copied here:

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help


Please also un-install the wireless USB Link Removed controller and physically remove the device from the system. These devices are known to cause BSOD's and there are no known driver updates for them.

Please follow these steps to troubleshoot the BSOD's: http://www.sysnative.com/forums/bsod...html#post29532

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! :

SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
Samsung printer driver
Link Removed

hotcore3.sys Mon Jan 21 08:33:19 2008 (47949F1F)
HotBackup by Paragon Software Group.
Link Removed




Analysis:
The following is for informational purposes only.
Code:
**************************Fri Apr 26 18:49:31.030 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-19624-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 0:05:16.920
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :nvkflt.sys ( nvkflt+31704 )
BugCheck 116, {fffffa80074c3010, fffff88004c82704, ffffffffc000009a, 4}
BugCheck Info: Link Removed
Arguments:
Arg1: fffffa80074c3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004c82704, 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: X64_0x116_IMAGE_nvkflt.sys
CPUID: "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2192
BIOS Version A12
BIOS Release Date 08/20/2012
Manufacturer Alienware
Product Name M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr 23 18:24:47.582 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042313-15022-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 17:53:19.457
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :nvkflt.sys ( nvkflt+31704 )
BugCheck 116, {fffffa80102b21c0, fffff88000c31704, ffffffffc000009a, 4}
BugCheck Info: Link Removed
Arguments:
Arg1: fffffa80102b21c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88000c31704, 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: X64_0x116_IMAGE_nvkflt.sys
CPUID: "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2192
BIOS Version A12
BIOS Release Date 08/20/2012
Manufacturer Alienware
Product Name M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Apr 20 02:29:09.585 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042013-23197-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:4 days 7:41:06.475
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by :nvkflt.sys ( nvkflt+31704 )
BugCheck 116, {fffffa800eb5b3e0, fffff880041bc704, ffffffffc000009a, 4}
BugCheck Info: Link Removed
Arguments:
Arg1: fffffa800eb5b3e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880041bc704, 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: X64_0x116_IMAGE_nvkflt.sys
CPUID: "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2192
BIOS Version A12
BIOS Release Date 08/20/2012
Manufacturer Alienware
Product Name M17xR3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:
**************************Fri Apr 26 18:49:31.030 2013 (UTC - 4:00)**************************
SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
hotcore3.sys Mon Jan 21 08:33:19 2008 (47949F1F)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
a1sv6adv.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
SynTP.sys Thu Aug 6 21:18:18 2009 (4A7B80DA)
sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iaStorV.sys Thu Jun 10 20:46:19 2010 (4C11875B)
btwampfl.sys Mon Jul 12 21:41:18 2010 (4C3BC43E)
Accelern.sys Fri Aug 20 14:04:57 2010 (4C6EC3C9)
stdcfltn.sys Fri Aug 20 14:05:01 2010 (4C6EC3CD)
iaStor.sys Mon Sep 13 21:23:32 2010 (4C8ECE94)
L1C62x64.sys Mon Sep 27 02:36:23 2010 (4CA03B67)
IntcDAud.sys Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys Tue Oct 19 19:33:43 2010 (4CBE2AD7)
CtClsFlt.sys Wed Jan 19 22:20:46 2011 (4D37AA0E)
nusb3hub.sys Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys Thu Feb 10 00:52:33 2011 (4D537D21)
Ak27x64.sys Tue Feb 22 11:29:32 2011 (4D63E46C)
bflwfx64.sys Thu Mar 10 10:08:25 2011 (4D78E969)
stwrt64.sys Thu Mar 17 04:21:47 2011 (4D81C49B)
RtsPStor.sys Thu Mar 24 04:04:09 2011 (4D8AFAF9)
nvBridge.kmd Sun Jun 26 18:06:57 2011 (4E07AD81)
igdkmd64.sys Wed Sep 26 15:49:04 2012 (50635C30)
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)
nvpciflt.sys Thu Mar 14 21:37:25 2013 (51427B55)
nvkflt.sys Thu Mar 14 21:37:36 2013 (51427B60)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr 23 18:24:47.582 2013 (UTC - 4:00)**************************
aos03fh1.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
xusb21.sys Thu Aug 13 18:10:17 2009 (4A848F49)
nvoclk64.sys Tue Sep 15 17:59:25 2009 (4AB00E3D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Apr 20 02:29:09.585 2013 (UTC - 4:00)**************************
a2q8iwxa.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
Link Removed
Link Removed
Link Removed
Link Removed
a1sv6adv.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
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
aos03fh1.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
a2q8iwxa.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.
 


Upvote 0 Downvote
Solution
no luck, BSOD keep coming, i guess it's a hardware problem :S
 


Upvote 0 Downvote
I'm still not certain if it's hardware or software. Did you finish all the recommended steps from my previous post? If not, which one's were completed? Also, please let us know if there were any difficulties with any of the things that you tried.

Please zip up and upload the contents of the C:\Windows\Minidump folder so we can have a look at the latest memory dumps.

You can run the video tests at this link to see if it's the video hardware: Link Removed
 


Upvote 0 Downvote
Applied the graphic memory test, and the result was BSOD :S the same one i've seen while playing...

usasma, i really appreciate your help, thank you!
 


Upvote 0 Downvote
The next step is to try another video card. I don't know anything about replacing these cards in Alienware systems - so I'd suggest visiting the graphics forums for more expert assistance: Link Removed

If you do purchase a new video card, please get it from a place that will let you return it for your money back. That way if that isn't the problem, you won't be out the money for testing it.

Good luck!
 


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