windows update crash when downloading

i have vista home premium 64bit sp1, think it started when activating windows update, i didnt want to install an active control, chose another method thats when i got blue screen system shutdown and i see this irql not less or equal..

windows update wasnt able to find any updates, so i went back to activating windows installed the active control, now im able to check for updates.

only thing is when i try installing the updates, it just tries to install but nothing is installing, then blue screen shutdown, how can i get the updates to install? appreaciate any help..

irql not less or equal

Click to expand...

This commands mean unindetefied conflict with drivers or hardware

We need more details to diagnose.Pack the whole C:\Windows\Minidump folder and attache to post

Flavius said:

irql not less or equal

Click to expand...

This commands mean unindetefied conflict with drivers or hardware

We need more details to diagnose.Pack the whole C:\Windows\Minidump folder and attache to post

Click to expand...

ok its attached to original post

violation009 said:

Flavius said:

irql not less or equal

Click to expand...

This commands mean unindetefied conflict with drivers or hardware

We need more details to diagnose.Pack the whole C:\Windows\Minidump folder and attache to post

Click to expand...

ok its attached to original post

Click to expand...

V

Im in the process of taking a quick look at the dumps. One thing immediately caught my eye. there are drivers from as far back as 2004. What version are you running? sp1?

ken

AsIO Thu Oct 14 05:53:21 2004 (416E4C91)

zigzag3143 said:

violation009 said:

Flavius said:

This commands mean unindetefied conflict with drivers or hardware

We need more details to diagnose.Pack the whole C:\Windows\Minidump folder and attache to post

Click to expand...

ok its attached to original post

Click to expand...

V

Im in the process of taking a quick look at the dumps. One thing immediately caught my eye. there are drivers from as far back as 2004. What version are you running? sp1?

ken

AsIO Thu Oct 14 05:53:21 2004 (416E4C91)

Click to expand...

home premimum vista 64 bit, sp1

violation

I have something I would like you to check

go into start>cpanel>system cpanel>advanced settings>performance settings>DEP. what is the dep currently set to?


Ken

zigzag3143 said:

violation

I have something I would like you to check

go into start>cpanel>system cpanel>advanced settings>performance settings>DEP. what is the dep currently set to?


Ken

Click to expand...

its set to: turn on dep for essential windows programs and services only

This is stricly hardware issues - two examples from from your files -almost all says

"probably caused by ntoskrnl.exe" ->this is equivalent trouble with hardware

Probably caused by : ntoskrnl.exe ( nt+fb978 )

Click to expand...

+

Probably caused by : hardware ( dxgkrnl+45e2e )

Click to expand...

To diagnose everything PSU,motherboard,video card...

this is what i got from the link

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\Minidump\Mini100809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`01c59000 PsLoadedModuleList = 0xfffff800`01e1edb0
Debug session time: Thu Oct 8 19:44:34.890 2009 (GMT-7)
System Uptime: 0 days 0:07:58.734
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffb40fc008adb, 0, fffff80001d54978, 7}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+fb978 )
Followup: MachineOwner
---------

is there a program to download that can diagnose the problem, pardon me if you posted it already..

There is not perfect tool for all everything although there are couple good benchmarks for example Everest Lavalys - Comprehensive IT Security and Management neverless to diagnose motherboard you have to open system unit -you have to check capacitors,make sure you don't have any leaks,to diagnose PSU usually is used multimeter - exactly how to do I don't know I'm not hardware expert
In VistaDVD you have already tool to diagnose RAM http://www.vistax64.com/tutorials/65361-memory-diagnostics-tool.html -use it
Here you are tools to diagnose hard disks Bootable Hard Drive Diagnostics - Vox
neverless to check cables you need open system unit as well.Maybe somebody experience in hardware give you better advices...

Read this advice too:http://usasma.vox.com/

thx for the help, memory diagnostic didnt find anything, ill try the others, one question is it a good idea to check for mouse, monitor, keyboard newer 64 bit drivers even though they work properly

violation009 said:

thx for the help, memory diagnostic didnt find anything, ill try the others, one question is it a good idea to check for mouse, monitor, keyboard newer 64 bit drivers even though they work properly

Click to expand...

Monitor,keyboard.mouse and any other external devices you can neglect.This issue can only cause any component in system unit.Hard to say precise what exactly it is.

i did another memeory diag test, standard didnt turn up anything so i did extensive, and it said hardware problems detected, so im guessing maybe its the ram, whats my next step?

If you have 2 or more memory modules you have to diagnose each one module separetly

Maybe these links will be useful:
Using MemTest86+ To Diagnose RAM Problems | RyanTAdams.com
How to diagnose faulty RAM: Insight - Software - ZDNet Australia