vgbraymond
Extraordinary Member
- Joined
- May 19, 2013
- Messages
- 2
- Thread Author
-
- #1
I have generated all the files according to Link Removed
I have problem uploading an attachment, so please follow my google drive link to the zipped file. The zip file should be downloadable by clicking File>Download
Link Removed
Please help. Thanks.
Raymond
I have problem uploading an attachment, so please follow my google drive link to the zipped file. The zip file should be downloadable by clicking File>Download
Link Removed
Please help. Thanks.
Raymond
Solution
Only 121 Windows Updates installed. Most systems have160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
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:
All of the memory dumps blame networking components. Most of the...
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.
All of the memory dumps blame networking components. Most of the...
- Joined
- Mar 22, 2010
- Messages
- 3,046
Only 121 Windows Updates installed. Most systems have160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
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:
All of the memory dumps blame networking components. Most of the stack text's list involvement of your Kaspersky software. Please:
- download a fresh copy of the latest, Win7 compatible version of Kaspersky from their website
- un-install the current version from your system (make sure you remove EVERYTHING if it asks)
- install the freshly downloaded version
- update the freshly installed version IMMEDIATELY
- perform a full system scan to ensure that nothing has slipped through
- monitor for further BSOD's
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! :
SABI.sys Thu May 28 02:38:02 2009 (4A1E314A)
SAMSUNG Kernel Driver
Link Removed
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
Link Removed
klfltdev.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
Link Removed
Link Removed
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.
All of the memory dumps blame networking components. Most of the stack text's list involvement of your Kaspersky software. Please:
- download a fresh copy of the latest, Win7 compatible version of Kaspersky from their website
- un-install the current version from your system (make sure you remove EVERYTHING if it asks)
- install the freshly downloaded version
- update the freshly installed version IMMEDIATELY
- perform a full system scan to ensure that nothing has slipped through
- monitor for further BSOD's
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! :
SABI.sys Thu May 28 02:38:02 2009 (4A1E314A)
SAMSUNG Kernel Driver
Link Removed
Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Sun May 19 08:47:25.787 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051913-8829-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]1 days 13:00:59.427[/B]
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by :[B]tdx.sys ( tdx+3675 )[/B]
BugCheck [B]A, {18000000400, 2, 1, fffff80001ef0622}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000018000000400, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001ef0622, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_tdx+3675[/B]
CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: [B]2394[/B]
BIOS Version P03ABI.005.120927.dg
BIOS Release Date 09/27/2012
Manufacturer SAMSUNG ELECTRONICS CO., LTD.
Product Name 550P5C/550P7C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu May 9 11:45:54.400 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050913-8642-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:01:14.040[/B]
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by :[B]tdx.sys ( tdx+3675 )[/B]
BugCheck [B]A, {18000000400, 2, 1, fffff80001eb1622}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000018000000400, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001eb1622, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_tdx+3675[/B]
CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: [B]2394[/B]
BIOS Version P03ABI.005.120927.dg
BIOS Release Date 09/27/2012
Manufacturer SAMSUNG ELECTRONICS CO., LTD.
Product Name 550P5C/550P7C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu May 9 11:44:18.209 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050913-8502-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 15:24:53.849[/B]
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by :[B]tdx.sys ( tdx+3675 )[/B]
BugCheck [B]A, {18000000400, 2, 1, fffff80001ef5622}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000018000000400, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001ef5622, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_tdx+3675[/B]
CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: [B]2394[/B]
BIOS Version P03ABI.005.120927.dg
BIOS Release Date 09/27/2012
Manufacturer SAMSUNG ELECTRONICS CO., LTD.
Product Name 550P5C/550P7C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May 7 10:34:45.584 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050713-8455-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 1:15:00.224[/B]
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by :[B]tdx.sys ( tdx+3675 )[/B]
BugCheck [B]D1, {20, 2, 0, fffff88001a3d45e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001a3d45e, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xD1_tdx+3675[/B]
CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: [B]2394[/B]
BIOS Version P03ABI.005.120927.dg
BIOS Release Date 09/27/2012
Manufacturer SAMSUNG ELECTRONICS CO., LTD.
Product Name 550P5C/550P7C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May 7 09:19:27.083 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050713-8221-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 1:48:28.612[/B]
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by :[B]tdx.sys ( tdx+3675 )[/B]
BugCheck [B]D1, {20, 2, 0, fffff88001c3d45e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001c3d45e, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xD1_tdx+3675[/B]
CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: [B]2394[/B]
BIOS Version P03ABI.005.120927.dg
BIOS Release Date 09/27/2012
Manufacturer SAMSUNG ELECTRONICS CO., LTD.
Product Name 550P5C/550P7C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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 May 19 08:47:25.787 2013 (UTC - 4:00)**************************
[B]SABI.sys Thu May 28 02:38:02 2009 (4A1E314A)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
klfltdev.sys Thu Sep 3 08:23:27 2009 (4A9FB53F)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
klim6.sys Thu Sep 1 08:28:14 2011 (4E5F7A5E)
PxHlpa64.sys Mon Oct 17 10:29:34 2011 (4E9C3BCE)
HECIx64.sys Wed Nov 9 19:52:25 2011 (4EBB2049)
Rt64win7.sys Wed Nov 23 10:00:40 2011 (4ECD0A98)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
btmaux.sys Wed Nov 30 02:09:32 2011 (4ED5D6AC)
btmhsf.sys Wed Nov 30 02:10:31 2011 (4ED5D6E7)
NETwNs64.sys Fri Dec 2 01:50:55 2011 (4ED8754F)
AMPPAL.sys Mon Dec 5 12:22:54 2011 (4EDCFDEE)
IntcDAud.sys Tue Dec 6 06:23:07 2011 (4EDDFB1B)
iusb3hub.sys Thu Jan 5 06:54:43 2012 (4F058F83)
iusb3xhc.sys Thu Jan 5 06:54:45 2012 (4F058F85)
iBtFltCoex.sys Tue Feb 14 15:38:54 2012 (4F3AC65E)
igdkmd64.sys Mon Mar 26 22:09:46 2012 (4F71216A)
excsd.sys Fri Mar 30 15:52:41 2012 (4F760F09)
excfs.sys Fri Mar 30 15:53:05 2012 (4F760F21)
nvlddmkm.sys Mon May 28 02:43:59 2012 (4FC31EAF)
nvpciflt.sys Mon May 28 02:44:57 2012 (4FC31EE9)
kl1.sys Tue Jun 19 09:27:15 2012 (4FE07E33)
RTKVHD64.sys Tue Aug 28 07:35:57 2012 (503CAD1D)
klif.sys Mon Sep 3 04:01:09 2012 (504463C5)
000.fcl Fri Nov 23 04:17:29 2012 (50AF3F29)
[/FONT]
Link Removed
klfltdev.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
Link Removed
Link Removed
Similar threads
- Solved
- Replies
- 1
- Views
- 4K