How to Fix Windows Update Errors?: Solution to Error: Computer crashing with Blue Screen of Death.

Computer crashing with Blue Screen of Death.

System Information (local)

computer name: RICHARD-GATEWAY
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4294967295 total
VM: 2147352576, free: 1976414208

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.

On Tue 11/23/2010 2:53:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112210-27565-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003D73CD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 11/23/2010 2:53:54 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ksecdd.sys(ksecdd+0x21A3)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003D73CD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module.
Your system configuration may be incorrect.
Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Mon 11/22/2010 2:43:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26988-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003F4C620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 11/22/2010 2:38:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880080DC620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 11/22/2010 2:35:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26395-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880080FE620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 11/22/2010 2:24:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26114-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003F4C620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 11/22/2010 2:19:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88007D1BCD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 11/21/2010 5:49:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-26925-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880082D0CD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 11:47:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-25615-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880055BECD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 5:26:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-25490-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88007D31CD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 4:34:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-73694-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88007EF0620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 4:29:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-27097-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880055DA620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 4:24:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-26410-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880086E2620, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 4:20:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-26722-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004764CD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 11/20/2010 4:12:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112010-26800-01.dmp
This was probably caused by the following module: ntoskrnl.exe(nt+0x70740)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880080FECD0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver which cannot be identified at this time.

Conclusion

51 crash dumps have been found and analyzed.
Only 15 are included in this report.
Read the topic
general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module.
Nonetheless it's suggested you look for updates for the products that these drivers
belong to and regularly visit Windows update or enable automatic updates for Windows.
In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help
you investigate this further.

Keys to the Problem Computer crashing with Blue Screen of Death.

Download Error Fixer for Free Now

Hi,
All the Bug_Checks are 1E 0x0000001E and the indicated CAUSE are Windows components
which means something else drove them into fault.
See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueScreens - top 3 answers (+1 other).
http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

---------------------------------------------------------------------------------------------
Remove ALL power and reseat all the cards, memory, and cables (both ends when possible) -
actually remove and replace - do not just snug.
Make sure the BIOS, low level chipset drivers,
and major device drivers are all up to date by check manually at the makers' sites.
Those are
for a PC and about all that can be done for a laptop is reseat the memory and clear the vents.
Many Bluescreens are caused by BIOS, low level chipset drivers, and other major device drivers
which are not the most current even though the computer is new.
Check manually for updates
using the methods for updates as indicated in the troubleshooter linked above and/or the methods
below (which are the same).

BCCode: 1E 0x0000001E <-- read this link
http://www.faultwire.com/solutions-fatal_error/Check-to-be-sure-you-have-adequate-disk-space-0x0000001E-*1045.html?order=date

---------------------------------------------------------------------------------------------

References to Vista also apply to Windows 7.

This is my generic how to for proper driver updates : (Check for BIOS and driver updates.)

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
For each driver in the list, additional useful information is displayed: load address of the driver,
description, version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model
of your video adapter - double click - Driver's tab - write down the version info.
Now click UPdate
Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions.
(Look for
BIOS, Chipset and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually
shows up.
This is because some drivers rollback before the latest is installed (sound drivers
particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as
needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

If you update drivers manually then it is a good idea to disable Driver Installations in Windows
Updates, this leaves Windows Updates ON however it will not install drivers which will usually be
older and cause issues.
If Updates suggests a new driver then HIDE it (Right Click on it) and then
go look for new ones manually if you wish.

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

==========================================

Memory tests do not catch all errors such as mismatched memory (possible even for sticks
that appear to be identical) and when faster memory is placed in system behind slower memory.
So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
a problem.
To test RAM check here - let it run 4+ hours or so.
<-- best method
www.memtest.org

For the Vista/Windows 7 Memory Diagnostic Tool

Start - type in Search box -> Memory - find Memory Diagnostics tool at top of list - Right Click -
RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
Tool
http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/
How to Run the Memory Diagnostics Tool in Windows 7
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

Hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.