Repeated BSOD error 0x0000001e, even after factory reset

tom982 · 11 May 2013

Hello sharona, welcome to SevenForums!

Your CBS log is full of these errors:

Code:

2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-8_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-8_neutral_LDR, PinDeployment: amd64_37224d96bac02a81db2c1bbc5a4dc5c5_31bf3856ad364e35_6.1.7601.21955_none_037c66e7a1aaa1be
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-9_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-9_neutral_LDR, PinDeployment: amd64_37224d96bac02a81db2c1bbc5a4dc5c5_31bf3856ad364e35_6.1.7601.21955_none_037c66e7a1aaa1be
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-10_neutral_GDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_3_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-10_neutral_GDR, PinDeployment: amd64_0f6a5890f2462677e89a731272fc9df6_31bf3856ad364e35_6.1.7601.17803_none_b52104fc57258dc5
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-11_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-11_neutral_LDR, PinDeployment: amd64_828c828ba1301920cfec67715d332824_31bf3856ad364e35_6.1.7601.21955_none_07de7c85b25bc951
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-12_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-12_neutral_LDR, PinDeployment: amd64_828c828ba1301920cfec67715d332824_31bf3856ad364e35_6.1.7601.21955_none_07de7c85b25bc951
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-13_neutral_GDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-13_neutral_GDR, PinDeployment: amd64_df3631507aa1e1c47ce09b0b9b60f0da_31bf3856ad364e35_6.1.7601.17803_none_7e13fcd971672a60
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-14_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-14_neutral_LDR, PinDeployment: amd64_a34c2c419323e45ae11d1d0fe135dc29_31bf3856ad364e35_6.1.7601.21955_none_c279556db85528dd
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-15_neutral_LDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-15_neutral_LDR, PinDeployment: amd64_a34c2c419323e45ae11d1d0fe135dc29_31bf3856ad364e35_6.1.7601.21955_none_c279556db85528dd
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-16_neutral_GDR
2013-05-10 20:59:27, Info                  CBS    Exec: Staging Package: Package_4_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-16_neutral_GDR, PinDeployment: amd64_ae134c06004c902885aa054886bde6a4_31bf3856ad364e35_6.1.7601.17803_none_84cc34d7fde1cf86
2013-05-10 20:59:27, Info                  CBS    Exec: This is a PSF Package.  Job has been saved and we are returning to client.
2013-05-10 20:59:27, Info                  CSI    00000014@2013/5/11:01:59:27.833 CSI Transaction @0x2baad0 destroyed
2013-05-10 20:59:27, Info                  CBS    Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.
2013-05-10 20:59:27, Info                  CBS    Perf: Stage chain complete.
2013-05-10 20:59:27, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-05-10 20:59:27, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-05-10 20:59:27, Info                  CBS    WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-05-10 20:59:28, Info                  CBS    Reboot mark refs: 0
2013-05-10 20:59:28, Info                  CBS    Enabling LKG boot option
2013-05-10 20:59:28, Info                  CBS    Restored system sleep block state: 0x80000000
2013-05-10 20:59:28, Info                  CBS    Exec: Processing complete.  Session: 30297579_713265650, Package: Package_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3 [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

Which, by themselves, aren't very informative but they do cover issues which may be reported in other logs. Would you mind uploading all of the following logs please:

C:\Windows\winsxs\poqexec.log
C:\Windows\Inf\setupapi.app.txt
C:\Windows\Inf\setupapi.dev.txt
C:\Windows\Logs\DPX\setupact.txt
C:\Windows\Logs\DPX\setuperr.txt

Tom

sharona · 11 May 2013

Hi, Tom! Thanks so much for joining Dave to help me out! I'm attaching a zip of those requested logs. Hope this helps.

tom982 · 11 May 2013

Hi Sharona,

Thanks for the logs! Though they also have a few errors in them, I don't think they're of concern and they appear to be perfectly normal.

Can you run this FixIt in aggressive mode please: http://go.microsoft.com/?linkid=9767...pointid=MATSKB

This will reset your Windows Update components, among a few other things.

After doing this, I would like you to download and install the System Update Readiness Tool (SURT): Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2013] from Official Microsoft Download Centre

Keep it in a convenient location as it's a fairly large file and we may well need it again. When it finishes installing, post the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

sharona · 11 May 2013

Tom, I've uploaded the requested log after performing the steps you gave me.

I will say, that, unrelated to log posting, I did get another BSOD (1e) in the interim. It looks like it was the Security Process Loader again. Saw it had a yellow triangle, again. Uninstalled, restarted the computer. Didn't see it in Device Manager, so I did a Scan for Hardware changes. It popped back up, no triangle. So far, no errors, but I can post the new dmp file, if you guys want to take a look. (I didn't want to upload something unnecessary.)

Northernsoul55 · 11 May 2013

Yes Sharona, please post up the new log :)

thanks

Dave

sharona · 11 May 2013

Gladly, Dave! Here you go!

koolkat77 · 11 May 2013

Was windows reinstalled on this laptop? Status of warranty?

nusb3xhc.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

nusb3hub.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

Have you checked for overheating issues?

Heat:
-Only use the laptop on a hard surface with nothing blocking any of the vents.
-Use a laptop cooling pad if possible
-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

Temperature

For monitoring heat of the system, use Speccy or HWMonitor:
Speccy System Information
HWMonitor

Hard Drive/Storage

Make sure the hard drive isn't running out of space. Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

Tip

Do this test overnight.

Please run these tests and report back the results

~~1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker~~
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

BSOD BUGCHECK SUMMARY

Code:

Debug session time: Sat May 11 18:54:13.510 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051113-41402-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
System Uptime: 0 days 0:21:31.930
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d2d )
BugCheck 1E, {ffffffffc0000005, fffffa8004b4fbb0, 0, 7efa8000}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa8004b4fbb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa8000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+48d2d
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 07:41:56.455 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-40825-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
System Uptime: 0 days 0:06:01.501
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BugCheck 1E, {ffffffffc0000005, fffff80002eb632f, 0, 7efa0000}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002eb632f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa0000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 07:29:47.735 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-45848-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
System Uptime: 0 days 0:04:04.156
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+1e3 )
BugCheck A, {0, 2, 0, fffff80002edc525}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002edc525, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEvent+1e3
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 07:25:22.226 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-38797-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
System Uptime: 0 days 0:03:05.647
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BugCheck A, {2000000dc, 2, 1, fffff80002ec5045}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 00000002000000dc, 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: fffff80002ec5045, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 02:01:43.729 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-29109-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
System Uptime: 0 days 0:02:22.150
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BugCheck A, {dc, 2, 1, fffff80002ecbab5}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 00000000000000dc, 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: fffff80002ecbab5, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 01:59:03.393 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-30903-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
System Uptime: 0 days 0:01:57.814
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BugCheck 1E, {ffffffffc0000005, fffff80002ec5f6b, 0, 7efa0000}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ec5f6b, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa0000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  netsession_win
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A11
BiosReleaseDate = 08/03/2012
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 3550
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 10 00:45:20.068 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050913-29718-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
System Uptime: 0 days 0:09:50.114
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )
BugCheck 1E, {ffffffffc0000005, fffffa80063cdbb0, 0, 7efa8000}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80063cdbb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa8000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  csc.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+4977d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu May  9 05:04:31.205 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\050813-20779-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
System Uptime: 0 days 0:02:54.626
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+1e3 )
BugCheck A, {0, 2, 0, fffff80002ed5d75}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ed5d75, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEvent+1e3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Code:

***   3rd PARTY DRIVER LIST   *** 
AMPPAL.sys                  Mon Aug  8 20:32:06 2011 (4E3FF366)
Accelern.sys                Mon Dec 13 23:33:51 2010 (4D0658FF)
Apfiltr.sys                 Thu May 12 21:28:31 2011 (4DCBFC9F)
CtClsFlt.sys                Thu Jan 20 09:20:46 2011 (4D37AA0E)
HECIx64.sys                 Wed Oct 20 05:33:43 2010 (4CBE2AD7)
HECIx64.sys                 Tue Sep 21 22:59:04 2010 (4C98E458)
IntcDAud.sys                Fri Oct 15 14:28:17 2010 (4CB810A1)
MpFilter.sys                Thu Nov  1 04:43:06 2012 (5091A97A)
NETwNs64.sys                Thu Aug  4 06:28:26 2011 (4E39E7AA)
PxHlpa64.sys                Wed Oct 21 00:08:42 2009 (4ADDFCAA)
Rt64win7.sys                Mon Mar  4 13:25:55 2013 (51344C83)
Rt64win7.sys                Mon Oct 25 15:33:07 2010 (4CC54ED3)
Sftfslh.sys                 Thu Dec  3 06:55:48 2009 (4B170C94)
Sftplaylh.sys               Thu Dec  3 06:55:40 2009 (4B170C8C)
Sftredirlh.sys              Thu Dec  3 06:55:52 2009 (4B170C98)
Sftvollh.sys                Thu Dec  3 06:55:23 2009 (4B170C7B)
TurboB.sys                  Tue Nov 30 05:02:31 2010 (4CF43107)
amdxata.sys                 Fri Mar 19 22:18:18 2010 (4BA3A3CA)
btmaud.sys                  Thu May 19 03:11:44 2011 (4DD43610)
btmaux.sys                  Thu May 19 03:11:49 2011 (4DD43615)
btmhsf.sys                  Tue Jul 12 21:45:04 2011 (4E1C6C00)
iBtFltCoex.sys              Wed Jul 20 07:54:03 2011 (4E26353B)
iaStor.sys                  Sat Nov  6 13:44:52 2010 (4CD50774)
igdkmd64.sys                Mon Apr 11 00:50:59 2011 (4DA1FC13)
igdkmd64.sys                Thu Dec 13 06:42:26 2012 (50C92472)
intelppm.sys                Tue Jul 14 05:19:25 2009 (4A5BC0FD)
iwdbus.sys                  Thu Mar 10 05:43:23 2011 (4D78109B)
nusb3hub.sys                Fri Dec 10 10:50:35 2010 (4D01B19B)
nusb3xhc.sys                Fri Dec 10 10:50:35 2010 (4D01B19B)
stdcfltn.sys                Sat Aug 21 00:05:01 2010 (4C6EC3CD)
stwrt64.sys                 Thu Sep  8 16:48:44 2011 (4E689D8C)

Northernsoul55 · 11 May 2013

Thanks KK.

And just to add please remove the program Freefall Protection from your system.
This is affecting the performance of your HDD I suspect?

Also I would suggest to Free up the startup/Disable Startup Programs:
Click on the Start button
Type “msconfig" (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus / essential items.
Apply > OK
Click the "Services" tab, click the "Hide All Microsoft Services" box, then click Disable All.
Click OK, then restart the computer.

Cheers

Dave

sharona · 11 May 2013

Thanks so much, KoolKat and Dave! I haven't finished all the steps yet, but I had some questions.

Re: those USB drivers. I went to Device Manager and tried to update them, they said they were already up-to-date. I can go try and get manual upgrades, but I wasn't sure if the best thing to do was to Uninstall them and the Renesas USB Controller Program they're connect to? I wanted to make sure I was clear on the best way to tackle them.

Do not know if this machine's under warranty or not. Re: Windows, I have done a factory reset. Not a clean reinstall from an iso, but the reset image did require me to set up Win7. I was worried this was a hardware issue causing all the errors, and didn't want to do a clean install only to start all over again trying to fix the issue, so that's when I came to the forum.

Also, question about Memtest: the first time I ran it, it ran for 13 passes, error-free, and was after the system was warm for a few hours. So, should I just go and do the 8-10 passes for the cooled off variable?

Dave, I can't see FreeFall in CP's uninstall programs, but I did see it in a Run search. Do I need to find an uninstaller for it?

I have not been able to see any indication of overheating, even after tests. (Ended up going with Speccy.)

I ran the Hard Drive diagnostic for WD and it passed.

Chkdsk was fine, though the same 1e BSOD came up immediately after the test. (Will post those logs later.)

I'm about to do a clean startup right now. I've attached the requested screencap of Crystal Disk.
Attachment 267655

Thanks again, guys!

Northernsoul55 · 11 May 2013

If you free the start up as Post

18 then you will be able to disable
FreeFall along with any other unneeded startup items

(Ill let KK answer your other questions :))

cheers

Dave