N
Nadav###
Guest
I've been experiencing for the past three months several BSOD with the error written in the title.
They have occured about once a week, maybe a little less.
I copied here the windbg report of the dump file.
I haven't made any changes to my computer sense I bought it two years ago.
[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013021-20453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`5e600000 PsLoadedModuleList = 0xfffff805`5f22a2f0
Debug session time: Sat Jan 30 23:07:04.811 2021 (UTC + 2:00)
System Uptime: 12 days 6:24:11.798
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff805`5e9f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc86`cc6943a0=000000000000007e
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Could not open dump file [C:\WINDOWS\MEMORY.DMP], Win32 error 0n2
"The system cannot find the file specified."
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80568958f4b, The address that the exception occurred at
Arg3: fffffc86cc695398, Exception Record Address
Arg4: fffffc86cc694bd0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-08E8QFM
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 70407
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80568958f4b
BUGCHECK_P3: fffffc86cc695398
BUGCHECK_P4: fffffc86cc694bd0
EXCEPTION_RECORD: fffffc86cc695398 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.exr 0xfffffc86cc695398)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]ExceptionAddress: fffff80568958f4b (dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x0000000000000067)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffc86cc694bd0 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.cxr 0xfffffc86cc694bd0)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=ffffb48ef0e59b00 rbx=ffffd680f92b8810 rcx=0000000000000000
rdx=0000000038c0081b rsi=54530a0d33203a58 rdi=7665643a6d6f632d
rip=fffff80568958f4b rsp=fffffc86cc6955d0 rbp=54530a0d33204a58
r8=ffffb48ef0e59b80 r9=0000000000001000 r10=fffff80566b21210
r11=fffffc86cc6956a0 r12=0000000000000000 r13=fffffc86cc695a40
r14=0000000000000000 r15=ffffd680fd1f5b30
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x67:
fffff805`68958f4b 48397720 cmp qword ptr [rdi+20h],rsi ds:002b:7665643a`6d6f634d=????????????????
Resetting default scope
BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8055f2fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8055f20f330: Unable to get Flags value from nt!KdVersionBlock
fffff8055f20f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffffc86`cc6955d0 fffff805`68958dab : 00000000`00001000 00000000`00001000 ffffd680`f92b8810 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x67
fffffc86`cc695600 fffff805`68943603 : ffffd680`fd1f5b30 ffffd680`fd1f5b30 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::UnlockAllocation+0x4b
fffffc86`cc695640 fffff805`68943547 : fffffc86`cc6957c0 ffffb48e`f90d8000 ffffd680`fc577f10 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::UnlockAllocation+0x73
fffffc86`cc695680 fffff805`68945b5a : ffffd680`fc577f10 ffffb48e`f90d8000 ffffb48e`f90d8000 00000000`00000000 : dxgmms2!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x73
fffffc86`cc6956c0 fffff805`6896a148 : ffffb48e`f90d8000 ffffb48e`f90e1c10 ffffb48e`f90d8000 ffffb48e`f90d8000 : dxgmms2!VIDMM_GLOBAL:
rocessDeferredCommand+0xa2a
fffffc86`cc695900 fffff805`689743d9 : ffffd680`ea765a00 ffffb48e`f72bf000 00000000`00000000 00000000`06e11a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
fffffc86`cc695ae0 fffff805`5e917e25 : ffffb48e`f72bf080 fffff805`689743d0 ffffd680`ea765a00 000fa4ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
fffffc86`cc695b10 fffff805`5e9fcdd8 : ffff9580`83f00180 ffffb48e`f72bf080 fffff805`5e917dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffc86`cc695b60 00000000`00000000 : fffffc86`cc696000 fffffc86`cc68f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+67
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]dxgmms2
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1134
STACK_COMMAND: .cxr 0xfffffc86cc694bd0 ; kb
BUCKET_ID_FUNC_OFFSET: 67
FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5ebeed9f-8a8f-bda7-945b-9e103337f3e7}
Followup: MachineOwner
---------
4: kd> lmvm dxgmms2
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Browse full module list
[/COLOR][COLOR=rgba(30, 30, 30, 1)]start end module name
fffff805`688e0000 fffff805`689c2000 [/COLOR][COLOR=rgba(0, 0, 255, 1)]dxgmms2[/COLOR][COLOR=rgba(30, 30, 30, 1)] # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4F4591A3CD26C1371ED129CB93006E321\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\E725F6E7e2000\dxgmms2.sys
Image path: \SystemRoot\System32\drivers\dxgmms2.sys
Image name: dxgmms2.sys
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Browse all global symbols[/COLOR][COLOR=rgba(30, 30, 30, 1)] [/COLOR][COLOR=rgba(0, 0, 255, 1)]functions[/COLOR][COLOR=rgba(30, 30, 30, 1)] [/COLOR][COLOR=rgba(0, 0, 255, 1)]data
[/COLOR][COLOR=rgba(30, 30, 30, 1)] Image was built with /Brepro flag.
Timestamp: E725F6E7 (This is a reproducible build file hash, not a timestamp)
CheckSum: 000EA5AE
ImageSize: 000E2000
File version: 10.0.19041.1134
Product version: 10.0.19041.1134
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.1134
FileVersion: 10.0.19041.1134 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
[/COLOR]
Continue reading...
They have occured about once a week, maybe a little less.
I copied here the windbg report of the dump file.
I haven't made any changes to my computer sense I bought it two years ago.
[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013021-20453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`5e600000 PsLoadedModuleList = 0xfffff805`5f22a2f0
Debug session time: Sat Jan 30 23:07:04.811 2021 (UTC + 2:00)
System Uptime: 12 days 6:24:11.798
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff805`5e9f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc86`cc6943a0=000000000000007e
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Could not open dump file [C:\WINDOWS\MEMORY.DMP], Win32 error 0n2
"The system cannot find the file specified."
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80568958f4b, The address that the exception occurred at
Arg3: fffffc86cc695398, Exception Record Address
Arg4: fffffc86cc694bd0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-08E8QFM
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 70407
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80568958f4b
BUGCHECK_P3: fffffc86cc695398
BUGCHECK_P4: fffffc86cc694bd0
EXCEPTION_RECORD: fffffc86cc695398 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.exr 0xfffffc86cc695398)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]ExceptionAddress: fffff80568958f4b (dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x0000000000000067)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffc86cc694bd0 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.cxr 0xfffffc86cc694bd0)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=ffffb48ef0e59b00 rbx=ffffd680f92b8810 rcx=0000000000000000
rdx=0000000038c0081b rsi=54530a0d33203a58 rdi=7665643a6d6f632d
rip=fffff80568958f4b rsp=fffffc86cc6955d0 rbp=54530a0d33204a58
r8=ffffb48ef0e59b80 r9=0000000000001000 r10=fffff80566b21210
r11=fffffc86cc6956a0 r12=0000000000000000 r13=fffffc86cc695a40
r14=0000000000000000 r15=ffffd680fd1f5b30
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x67:
fffff805`68958f4b 48397720 cmp qword ptr [rdi+20h],rsi ds:002b:7665643a`6d6f634d=????????????????
Resetting default scope
BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8055f2fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8055f20f330: Unable to get Flags value from nt!KdVersionBlock
fffff8055f20f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffffc86`cc6955d0 fffff805`68958dab : 00000000`00001000 00000000`00001000 ffffd680`f92b8810 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+0x67
fffffc86`cc695600 fffff805`68943603 : ffffd680`fd1f5b30 ffffd680`fd1f5b30 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::UnlockAllocation+0x4b
fffffc86`cc695640 fffff805`68943547 : fffffc86`cc6957c0 ffffb48e`f90d8000 ffffd680`fc577f10 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::UnlockAllocation+0x73
fffffc86`cc695680 fffff805`68945b5a : ffffd680`fc577f10 ffffb48e`f90d8000 ffffb48e`f90d8000 00000000`00000000 : dxgmms2!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x73
fffffc86`cc6956c0 fffff805`6896a148 : ffffb48e`f90d8000 ffffb48e`f90e1c10 ffffb48e`f90d8000 ffffb48e`f90d8000 : dxgmms2!VIDMM_GLOBAL:
rocessDeferredCommand+0xa2afffffc86`cc695900 fffff805`689743d9 : ffffd680`ea765a00 ffffb48e`f72bf000 00000000`00000000 00000000`06e11a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
fffffc86`cc695ae0 fffff805`5e917e25 : ffffb48e`f72bf080 fffff805`689743d0 ffffd680`ea765a00 000fa4ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
fffffc86`cc695b10 fffff805`5e9fcdd8 : ffff9580`83f00180 ffffb48e`f72bf080 fffff805`5e917dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffc86`cc695b60 00000000`00000000 : fffffc86`cc696000 fffffc86`cc68f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock+67
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]dxgmms2
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1134
STACK_COMMAND: .cxr 0xfffffc86cc694bd0 ; kb
BUCKET_ID_FUNC_OFFSET: 67
FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Unlock
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5ebeed9f-8a8f-bda7-945b-9e103337f3e7}
Followup: MachineOwner
---------
4: kd> lmvm dxgmms2
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Browse full module list
[/COLOR][COLOR=rgba(30, 30, 30, 1)]start end module name
fffff805`688e0000 fffff805`689c2000 [/COLOR][COLOR=rgba(0, 0, 255, 1)]dxgmms2[/COLOR][COLOR=rgba(30, 30, 30, 1)] # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4F4591A3CD26C1371ED129CB93006E321\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\E725F6E7e2000\dxgmms2.sys
Image path: \SystemRoot\System32\drivers\dxgmms2.sys
Image name: dxgmms2.sys
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Browse all global symbols[/COLOR][COLOR=rgba(30, 30, 30, 1)] [/COLOR][COLOR=rgba(0, 0, 255, 1)]functions[/COLOR][COLOR=rgba(30, 30, 30, 1)] [/COLOR][COLOR=rgba(0, 0, 255, 1)]data
[/COLOR][COLOR=rgba(30, 30, 30, 1)] Image was built with /Brepro flag.
Timestamp: E725F6E7 (This is a reproducible build file hash, not a timestamp)
CheckSum: 000EA5AE
ImageSize: 000E2000
File version: 10.0.19041.1134
Product version: 10.0.19041.1134
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.1134
FileVersion: 10.0.19041.1134 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
[/COLOR]
Continue reading...