BSOD IN Windows 7 64-bit
i have a recurring probolem of the blue screen and computer either shutting down or rebooting...
can someone do a bug check analysis of my dump files i have uploaded and here is the link to the dump files....
http://cid-4d6796ec26fa8ce6.skydrive.live.com/redir.aspx?resid=4D6796EC26FA8CE6!1388
thanks in advance
May 26th, 2011 1:56am
i have a recurring probolem of the blue screen and computer either shutting down or rebooting...
can someone do a bug check analysis of my dump files i have uploaded and here is the link to the dump files....
http://cid-4d6796ec26fa8ce6.skydrive.live.com/redir.aspx?resid=4D6796EC26FA8CE6!1388
thanks in advance
Problem signature:
Problem Event Name:
BlueScreen
OS Version:
6.1.7600.2.0.0.256.48
Locale ID:
1033
Additional information about the problem:
BCCode:
24
BCP1:
00000000001904FB
BCP2:
FFFFF880031BD898
BCP3:
FFFFF880031BD100
BCP4:
FFFFF8800141880C
OS Version:
6_1_7600
Service Pack:
0_0
Product:
256_1
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 2:11am
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa83009dd5b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002af83fa, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff0e0
fffffa83009dd5b0
FAULTING_IP:
nt!MiDeleteVirtualAddresses+481
fffff800`02af83fa 448b2b mov r13d,dword ptr [rbx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: fifa.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880090aff50 -- (.trap 0xfffff880090aff50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000100349c9 rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000000047 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002af83fa rsp=fffff880090b00e0 rbp=0000000028c49000
r8=0000000000000001 r9=fffffa8006e4fb30 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiDeleteVirtualAddresses+0x481:
fffff800`02af83fa 448b2b mov r13d,dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b468c1 to fffff80002ac7740
STACK_TEXT:
fffff880`090afde8 fffff800`02b468c1 : 00000000`00000050 fffffa83`009dd5b0 00000000`00000000 fffff880`090aff50 : nt!KeBugCheckEx
fffff880`090afdf0 fffff800`02ac582e : 00000000`00000000 fffffa83`009dd5b0 fffff880`009e6100 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`090aff50 fffff800`02af83fa : fffffa80`06e4fb30 00000000`28bff000 fd700000`3747ec6e fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`090b00e0 fffff800`02b090da : 00000000`00000000 00000000`2960ffff fffffa80`00000000 fffffa80`06e4fb30 : nt!MiDeleteVirtualAddresses+0x481
fffff880`090b02a0 fffff800`02ac6993 : ffffffff`ffffffff fffff8a0`02755968 fffff8a0`02755990 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`090b0390 fffff800`02ac2f30 : fffff880`043834b2 fffff8a0`04833d10 fffffa80`06e4fb30 fffffa80`06db5220 : nt!KiSystemServiceCopyEnd+0x13
fffff880`090b0528 fffff880`043834b2 : fffff8a0`04833d10 fffffa80`06e4fb30 fffffa80`06db5220 fffff8a0`02755960 : nt!KiServiceLinkage
fffff880`090b0530 fffff880`0436eb5a : fffffa80`04f7a000 fffff8a0`03f81d20 00000000`00000001 fffff8a0`03b16760 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`090b0560 fffff880`04369523 : fffffa80`03811700 00000000`00000001 fffff8a0`04833d10 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`090b0610 fffff880`0434fecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`090b06e0 fffff880`04291c10 : 00000000`00000000 fffff8a0`07e82000 fffff8a0`07e82000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`090b0710 fffff880`0429154b : fffff8a0`07e82000 fffff8a0`07e83300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`090b0800 fffff880`04291825 : fffff8a0`07e82000 fffff8a0`07e82000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`090b0850 fffff880`042956e0 : fffff8a0`03a7e300 fffff880`090b0ca0 fffffa80`06663000 fffff880`0425c3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`090b08a0 fffff880`04297d9b : fffff8a0`07e82000 fffff880`090b09b0 00000000`7efdb001 00000000`00000001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`090b0930 fffff960`001cb3a2 : 00000000`7efdb000 fffffa80`04e3c5a0 00000000`00000020 00000000`74015f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`090b0bf0 fffff800`02ac6993 : 00000000`00000008 00000000`18b80800 fffffa80`00000001 00000000`1be03f5c : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`090b0c20 00000000`7403120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7403120a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`043834b2 488b0e mov rcx,qword ptr [rsi]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
Followup: MachineOwner
---------
1: kd> lmvm dxgmms1
start end module name
fffff880`0434e000 fffff880`04394000 dxgmms1 (pdb symbols) downstreamstore\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
Loaded symbol image file: dxgmms1.sys
Mapped memory image file: DownstreamStore\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
Image path: \SystemRoot\System32\drivers\dxgmms1.sys
Image name: dxgmms1.sys
Timestamp: Tue Jul 14 01:38:32 2009 (4A5BC578)
CheckSum: 0004AD44
ImageSize: 00046000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms1.sys
OriginalFilename: dxgmms1.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
____________________________________
Bug Check Code 0x50: http://msdn.microsoft.com/en-us/library/ff559023(VS.85).aspx
Bug Check Code 0x24: http://msdn.microsoft.com/en-us/library/ff557433(VS.85).aspx
Run chkdsk /r /f and install that: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displayLang=en
If the problem persists, update your graphic card driver and check again.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
May 26th, 2011 3:21am
i am sorry but i did not understand the analysis properly.....
can u help me with it in fixing the bluescreen problem....
does the analysis refer to problems with memory (e.g RAM, HDD)
Thanks In Advance.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 4:03am
This is what I wrote:
Run chkdsk /r /f and install that: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displayLang=en
If the problem persists, update your graphic card driver and check again.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
May 26th, 2011 4:33am