trying to use update KB980182 gives code 800736B3?!?!?!

Artonox · 05 Apr 2010

o ok, would it delete my files? or go fresh install? because i hope not D: i installed loads of stuff already D:

how did it come to this?!

Tews · 05 Apr 2010

Doing a repair install will not affect any of your programs or documents...

Artonox · 05 Apr 2010

GAH! just used my upgrade disk to repair install. Spent 3 hours+ as the comp does the repair, and one last restart makes it have the BSOD. Then it says update not successful and reverts me back to the old w7. omg, do i start again, or get another disk (same as buy another which im not doing D: ).
why does this seem so tedious?! D:

EDIT: gonna try again, so will return in another 2-3 hours

Flavius · 05 Apr 2010

Artonox said:

GAH! just used my upgrade disk to repair install. Spent 3 hours+ as the comp does the repair, and one last restart makes it have the BSOD.

Independly from results pack the whole C:\Windows\Minidump folder and attache to post.

Artonox · 05 Apr 2010

Attachment 65304
here it is flavius. I really want to thank you some more for helping me by giving you more rep, but it seems i have already given you enough. So here is a virtual thanks instead :)

btw the same bsod happened. It had happened when W7 setup was transferring the programs and files (the last main step) at around 60% when it wanted to restart. When restarting, during loading up W7 again, the BSOD happened and restarted again, prompting the "failure"

Flavius · 05 Apr 2010

Debugged dump files:

Code:

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


Loading Dump File [G:\Downloads_anoth\Artonox\Minidump\040110-28796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*G:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Thu Apr  1 16:27:43.159 2010 (GMT+2)
System Uptime: 0 days 2:09:55.424
Loading Kernel Symbols
..................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000047, fffff80002f077f8, bc00, 10}

Probably caused by : ntkrnlmp.exe ( nt!RtlRaiseStatus+18 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000047, The exception code that was not handled
Arg2: fffff80002f077f8, The address that the exception occurred at
Arg3: 000000000000bc00, Parameter 0 of the exception
Arg4: 0000000000000010, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - Podj

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`02f077f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

EXCEPTION_PARAMETER1:  000000000000bc00

EXCEPTION_PARAMETER2:  0000000000000010

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee6a3a to fffff88002cba7f2

STACK_TEXT:  
fffff800`04524c98 fffff800`02ee6a3a : 00000000`0020f420 fffffa80`051d10a8 fffff800`0305fc40 00000000`00000001 : 0xfffff880`02cba7f2
fffff800`04524ca0 fffff800`02ee16cc : fffff800`03051e80 fffff800`00000000 00000000`00000000 fffffa80`0432f0a0 : nt!PoIdle+0x53a
fffff800`04524d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!RtlRaiseStatus+18
fffff800`02f077f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

SYMBOL_NAME:  nt!RtlRaiseStatus+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_nt!RtlRaiseStatus+18

BUCKET_ID:  X64_0x1E_nt!RtlRaiseStatus+18

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000047, The exception code that was not handled
Arg2: fffff80002f077f8, The address that the exception occurred at
Arg3: 000000000000bc00, Parameter 0 of the exception
Arg4: 0000000000000010, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - Podj

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`02f077f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

EXCEPTION_PARAMETER1:  000000000000bc00

EXCEPTION_PARAMETER2:  0000000000000010

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee6a3a to fffff88002cba7f2

STACK_TEXT:  
fffff800`04524c98 fffff800`02ee6a3a : 00000000`0020f420 fffffa80`051d10a8 fffff800`0305fc40 00000000`00000001 : 0xfffff880`02cba7f2
fffff800`04524ca0 fffff800`02ee16cc : fffff800`03051e80 fffff800`00000000 00000000`00000000 fffffa80`0432f0a0 : nt!PoIdle+0x53a
fffff800`04524d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!RtlRaiseStatus+18
fffff800`02f077f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

SYMBOL_NAME:  nt!RtlRaiseStatus+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_nt!RtlRaiseStatus+18

BUCKET_ID:  X64_0x1E_nt!RtlRaiseStatus+18

Followup: MachineOwner
---------

and original BSOD image:

Code:

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: 

KMODE_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000001e (0xffffffffc0000047, 0xfffff80002f077f8, 0x000000000000bc00, 
0x0000000000000010)

***  - Address 0x0000000000000000 base at 0x0000000000000000 DateStamp 
0x00000000

Probably it is any driver/hardware issue although what I read it would be stricly issues with system drivers too, and in this case the only solution is to reinstall OS

First check your drivers,hardware and BIOS as below links suggest in your case

Windows Blue Screen Of Death error: STOP: 0x0000001E - Windows Registry Solution
How to Troubleshoot a STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message
How to fix stop 0x0000001E error

If really nothing help you can try reinstall OS but please note clean install can solve that is not hardware/3p drivers problem