Update wont download the update

Dudex · 02 Sep 2010

ok, that sounds sweet

Dudex · 02 Sep 2010

BTW that anti virus you said I should innstall wont update either :S

Flavius · 02 Sep 2010

I have bad news for you.Even rainstall OS does not solve your problems pernamently.You seem have issues with RAM

Code:

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


Loading Dump File [G:\Folder1\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*G:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03292e50
Debug session time: Wed Sep  1 15:26:51.102 2010 (GMT+2)
System Uptime: 0 days 1:21:14.177
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 59b4, 2, 59b2}

PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000059b4, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000059b2, 0

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

PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details

BUGCHECK_STR:  0x4E_99

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800031552bc to fffff800030c5600

STACK_TEXT:  
fffff880`0bec0f28 fffff800`031552bc : 00000000`0000004e 00000000`00000099 00000000`000059b4 00000000`00000002 : nt!KeBugCheckEx
fffff880`0bec0f30 fffff800`03137925 : 00000000`00000000 fffff680`002ecc20 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0bec0f70 fffff800`03099b43 : fffffa80`0a25e060 fffff700`0005820c 0000007f`fffffff8 fffff8a0`0b1ecbf8 : nt! ?? ::FNODOBFM::`string'+0x3226c
fffff880`0bec1000 fffff800`030985a2 : fffffa80`0a25e060 fffffa80`00000000 fffff880`0005563c fffff800`0000002b : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0bec18b0 fffff800`033abc4f : fffff8a0`0c393530 fffff880`0bec1c20 00000000`00000000 fffffa80`09b3f780 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0bec1900 fffff800`033844d1 : 00000000`20010000 00000000`00000001 00000000`fd27d000 fffffa80`087c11f0 : nt!PspExitThread+0x92f
fffff880`0bec19c0 fffff800`030a20e3 : fffff900`c22fbce0 00000000`00000000 fffff900`79747355 fffff900`00000029 : nt!PsExitSpecialApc+0x1d
fffff880`0bec19f0 fffff800`030a2520 : 00000000`31f9fe08 fffff880`0bec1a70 fffff800`033845dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0bec1a70 fffff800`030c48f7 : fffff880`0bec1ca0 fffff800`030d15fa 00000000`0000002a 00000000`73532450 : nt!KiInitiateUserApc+0x70
fffff880`0bec1bb0 00000000`73532dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`31e9f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73532dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`031552bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000059b4, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000059b2, 0

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

PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details

BUGCHECK_STR:  0x4E_99

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800031552bc to fffff800030c5600

STACK_TEXT:  
fffff880`0bec0f28 fffff800`031552bc : 00000000`0000004e 00000000`00000099 00000000`000059b4 00000000`00000002 : nt!KeBugCheckEx
fffff880`0bec0f30 fffff800`03137925 : 00000000`00000000 fffff680`002ecc20 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0bec0f70 fffff800`03099b43 : fffffa80`0a25e060 fffff700`0005820c 0000007f`fffffff8 fffff8a0`0b1ecbf8 : nt! ?? ::FNODOBFM::`string'+0x3226c
fffff880`0bec1000 fffff800`030985a2 : fffffa80`0a25e060 fffffa80`00000000 fffff880`0005563c fffff800`0000002b : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0bec18b0 fffff800`033abc4f : fffff8a0`0c393530 fffff880`0bec1c20 00000000`00000000 fffffa80`09b3f780 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0bec1900 fffff800`033844d1 : 00000000`20010000 00000000`00000001 00000000`fd27d000 fffffa80`087c11f0 : nt!PspExitThread+0x92f
fffff880`0bec19c0 fffff800`030a20e3 : fffff900`c22fbce0 00000000`00000000 fffff900`79747355 fffff900`00000029 : nt!PsExitSpecialApc+0x1d
fffff880`0bec19f0 fffff800`030a2520 : 00000000`31f9fe08 fffff880`0bec1a70 fffff800`033845dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0bec1a70 fffff800`030c48f7 : fffff880`0bec1ca0 fffff800`030d15fa 00000000`0000002a 00000000`73532450 : nt!KiInitiateUserApc+0x70
fffff880`0bec1bb0 00000000`73532dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`31e9f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73532dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`031552bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

I suggest diagnose your RAM by using Memtest Memtest86+ - Advanced Memory Diagnostic Tool,and make another thread in "Crashes and debugging" section to ask for further help

Dudex · 02 Sep 2010

How should I use this program for?

Flavius · 02 Sep 2010

Dudex said:

How should I use this program for?

You have to download *.iso and burn it to any DVD ,boot this DVD and scan. I suggest read manual before.

Dudex · 02 Sep 2010

Too bad I still dont have any CDs xD