- Thread Author
-
- #1
I've tried removing AVG using their removal tools and instructions. I've tried fully removing my video and mobo drivers with driver sweeper and installing the latest GPU and Motherboard drivers and flashed the latest Motherboard BIOS. I've scoured forum after forum and seen similar issues and tried countless solutions. I haven't seen someone with my -exact- problem and -exact- spec/error reports so I'm caving lol. I build and maintain PC's as a hobby and I like to solve problems on my own know-how but I am at wits end with this BSOD.
Quick specs:
Windows 7 Ultimate 64-bit
8 gigs DDR3 Gskil
AMD Phenom II X4 955 Denab
Nvidia GeForce GTS 250 (x2 SLI)
Asus M4N75TD nForce 740a
Malwarebytes Antimalware
All other info, including that, in attachment. Thank you!
Quick specs:
Windows 7 Ultimate 64-bit
8 gigs DDR3 Gskil
AMD Phenom II X4 955 Denab
Nvidia GeForce GTS 250 (x2 SLI)
Asus M4N75TD nForce 740a
Malwarebytes Antimalware
All other info, including that, in attachment. Thank you!
Attachments
Solution
4 (in a row) of your latest ones point to svchost.exe and ks.sys. ks.sys is a Microsoft Windows Kernel CSA library file.
In only one occasion in this and last month did i see a different file, also a major windows executable. All of these however were 3B.
"This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code."
Has this been the exact same problem to the point of your first BSOD (10/11/11), because your first BSOD was a fatal one.
By what im seeing (and i am not a pro at kernal AT ALL) ks.sys is trying to reference unexisting memory. And from the stack, im seeing that it is mainly zeroing-out on a code says deletion. It looks almost as...
In only one occasion in this and last month did i see a different file, also a major windows executable. All of these however were 3B.
"This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code."
Has this been the exact same problem to the point of your first BSOD (10/11/11), because your first BSOD was a fatal one.
By what im seeing (and i am not a pro at kernal AT ALL) ks.sys is trying to reference unexisting memory. And from the stack, im seeing that it is mainly zeroing-out on a code says deletion. It looks almost as...
- Joined
- Mar 22, 2010
- Messages
- 3,046
Sometimes this takes a while. Please be patient and we'll continue to work on this.
This set of dumps has a distinctive pattern (actually a lack of a pattern):
There are 10 memory dumps
There are 5 different BSOD error codes
There are 5 different causes blamed
Although there are still signs of some troublesome drivers, this is looking more and more like a hardware problem (which the lack of a pattern sometimes indicates).
In particular, 7 or 8 of the memory dumps seem to have video components associated with them (So I'd suspect video issues as being most likely).
I would remove one of the video cards and test the system with only 1 card. Then, once the BSOD's are finished, you can put the other card back in and see how it works.
I can't recall if I mentioned an issue with the Asus M4 series of motherboards that I've heard of occasionally. The Auto function for memory in the BIOS isn't always reliable. It's suggested that you get the settings/timings/voltages for your RAM from the RAM manufacturer - and then put those values into the BIOS manually (in other words - DO NOT use the "Auto" setting for memory).
Please run the free diagnostics from here: Link Removed
As time permits, also run these free diagnostics (just to be sure): Link Removed - Invalid URL
Analysis:
The following is for informational purposes only.
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.
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
This set of dumps has a distinctive pattern (actually a lack of a pattern):
There are 10 memory dumps
There are 5 different BSOD error codes
There are 5 different causes blamed
Although there are still signs of some troublesome drivers, this is looking more and more like a hardware problem (which the lack of a pattern sometimes indicates).
In particular, 7 or 8 of the memory dumps seem to have video components associated with them (So I'd suspect video issues as being most likely).
I would remove one of the video cards and test the system with only 1 card. Then, once the BSOD's are finished, you can put the other card back in and see how it works.
I can't recall if I mentioned an issue with the Asus M4 series of motherboards that I've heard of occasionally. The Auto function for memory in the BIOS isn't always reliable. It's suggested that you get the settings/timings/voltages for your RAM from the RAM manufacturer - and then put those values into the BIOS manually (in other words - DO NOT use the "Auto" setting for memory).
Please run the free diagnostics from here: Link Removed
As time permits, also run these free diagnostics (just to be sure): Link Removed - Invalid URL
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sun Oct 28 10:34:26.165 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102812-29094-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 8:25:03.773[/B]
BugCheck Code: [B]BugCheck 50, {ffffffff000151d0, 8, ffffffff000151d0, 5}[/B]
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
Probably caused by :[B]ks.sys ( ks!KspClose+fc )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
Arguments:
Arg1: ffffffff000151d0, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffffff000151d0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_BAD_IP_ks!KspClose+fc[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 27 17:25:46.886 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102712-28766-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 6:49:01.494[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff8800fdb9a05, fffff880085e3f30, 0}[/B]
Probably caused by :[B]ks.sys ( ks!KspClose+ed )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800fdb9a05, Address of the instruction which caused the bugcheck
Arg3: fffff880085e3f30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_ks!KspClose+ed[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 26 09:53:18.767 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102612-28672-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 20:34:53.984[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa80082caa00, fffff80000b9c518, fffffa80094bb2a0}[/B]
*** ERROR: Module load completed but symbols could not be loaded for usbccgp.sys
Probably caused by :[B]usbccgp.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: fffffa80082caa00, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80094bb2a0, The blocked IRP
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x9F_3_dgmbx2_IMAGE_usbccgp.sys[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct 25 12:22:35.598 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102512-29172-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:44:15.831[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff880045cda05, fffff8800719d4a0, 0}[/B]
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
Probably caused by :[B]ks.sys ( ks!KspClose+ed )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880045cda05, Address of the instruction which caused the bugcheck
Arg3: fffff8800719d4a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_ks!KspClose+ed[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 14:53:58.752 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-28782-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:06:16.970[/B]
BugCheck Code: [B]BugCheck 116, {fffffa800948b4e0, fffff8800f220a88, 0, 2}[/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+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments:
Arg1: fffffa800948b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f220a88, 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.
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 14:06:37.185 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-31325-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:44.450[/B]
BugCheck Code: [B]BugCheck C4, {f6, 100, fffffa800a73bb30, fffff8800c63a206}[/B]
*** WARNING: Unable to verify timestamp for RTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTCore64.sys
Probably caused by :[B]RTCore64.sys ( RTCore64+1206 )[/B]
BugCheck Info: [B]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000100, Handle value being referenced.
Arg3: fffffa800a73bb30, Address of the current process.
Arg4: fffff8800c63a206, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR: 0xc4_f6
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]EVGAPrecision.[/B]
FAILURE_BUCKET_ID: [B]X64_0xc4_f6_VRF_RTCore64+1206[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 13:32:54.079 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-29967-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:13:15.296[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, 476134, fffff880053f0490, 0}[/B]
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
Probably caused by :[B]ks.sys ( ks!KspClose+fc )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000476134, Address of the instruction which caused the bugcheck
Arg3: fffff880053f0490, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_ks!KspClose+fc[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 12:17:19.193 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-30591-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:09:04.410[/B]
BugCheck Code: [B]BugCheck 116, {fffffa800971e010, fffff8800f17fa88, 0, 2}[/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+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments:
Arg1: fffffa800971e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f17fa88, 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.
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 11:06:39.523 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-29312-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:29:15.019[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, 44e648, fffff8800c0e2f20, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 000000000044e648, Address of the instruction which caused the bugcheck
Arg3: fffff8800c0e2f20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!KiSystemServiceHandler+7c[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 19 11:49:52.832 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101912-31184-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]2 days 0:12:04.049[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff8800fdc2a05, fffff8800d9cbf30, 0}[/B]
Probably caused by :[B]ks.sys ( ks!KspClose+ed )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800fdc2a05, Address of the instruction which caused the bugcheck
Arg3: fffff8800d9cbf30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_ks!KspClose+ed[/B]
BIOS Version 1501
BIOS Release Date 11/22/2010
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]**************************Sun Oct 28 10:34:26.165 2012 (UTC - 4:00)**************************
ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys Mon Aug 3 03:03:16 2009 (4A768BB4)
nvoclk64.sys Tue Sep 15 17:59:25 2009 (4AB00E3D)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvsmu.sys Mon Mar 22 21:29:19 2010 (4BA8196F)
viahduaa.sys Wed Aug 4 03:51:53 2010 (4C591C19)
nvmf6264.sys Thu Aug 12 07:46:06 2010 (4C63DEFE)
Tpkd.sys Thu Sep 30 16:49:13 2010 (4CA4F7C9)
dgmbx2.sys Fri Feb 11 18:02:20 2011 (4D55BFFC)
speedfan.sys Fri Mar 18 12:08:46 2011 (4D83838E)
easytthr.sys Sun May 22 07:44:02 2011 (4DD8F702)
pneteth.sys Tue Jul 19 11:34:59 2011 (4E25A423)
GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1)
mbam.sys Mon Aug 20 12:49:41 2012 (50326AA5)
MpFilter.sys Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys Tue Oct 2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 14:53:58.752 2012 (UTC - 4:00)**************************
cpuz135_x64.sys Tue Nov 9 08:33:36 2010 (4CD94DB0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 14:06:37.185 2012 (UTC - 4:00)**************************
[B]RTCore64.sys Tue Sep 6 08:24:50 2011 (4E661112)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 13:32:54.079 2012 (UTC - 4:00)**************************
MAC607.sys Mon Sep 13 10:59:15 2010 (4C8E3C43)
dgmbx2fu.sys Fri Feb 11 18:02:48 2011 (4D55C018)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Similar threads
- Replies
- 6
- Views
- 2K
- Replies
- 4
- Views
- 3K
- Solved
- Replies
- 1
- Views
- 1K
- Solved
- Replies
- 20
- Views
- 13K
- Solved
- Replies
- 3
- Views
- 7K