Closed Bug 635529 Opened 14 years ago Closed 14 years ago

BSOD due to memory corruption

Categories

(Firefox :: General, defect)

x86_64
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: brandonlim05, Unassigned)

Details

Attachments

(1 file)

285.70 KB, application/octet-stream
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) BSOD due to memory corruption caused by firefox - happened for the 2nd time. (refer additional info) Extremely high amount of memory usage upto ~1 GB (4GB ram installed) Reproducible: Didn't try 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: fffffa81816f36d8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8000308fabb, 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 fffff800032f30e0 fffffa81816f36d8 FAULTING_IP: nt!MiDeleteAddressesInWorkingSet+27f fffff800`0308fabb 488b4128 mov rax,qword ptr [rcx+28h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009421660 -- (.trap 0xfffff88009421660) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000058000000000 rbx=0000000000000000 rcx=fffffa81816f36b0 rdx=000000000544d009 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000308fabb rsp=fffff880094217f0 rbp=fffff7000108ef30 r8=fffffa8004452ec8 r9=0000000000000001 r10=0000000000000dcb r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiDeleteAddressesInWorkingSet+0x27f: fffff800`0308fabb 488b4128 mov rax,qword ptr [rcx+28h] ds:1a6e:fffffa81`816f36d8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000313a801 to fffff800030bb600 STACK_TEXT: fffff880`094214f8 fffff800`0313a801 : 00000000`00000050 fffffa81`816f36d8 00000000`00000000 fffff880`09421660 : nt!KeBugCheckEx fffff880`09421500 fffff800`030b96ee : 00000000`00000000 d5500080`7a679867 00000000`00001000 fffff800`031efbfe : nt! ?? ::FNODOBFM::`string'+0x40ecb fffff880`09421660 fffff800`0308fabb : 00000003`00000000 d5300000`94577867 fffff700`0108ef20 fffff680`0002a258 : nt!KiPageFault+0x16e fffff880`094217f0 fffff800`0308e5a2 : fffffa80`04452b30 fffffa80`00000000 fffff8a0`00000dcb fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x27f fffff880`094220a0 fffff800`033a1c4f : fffff8a0`05703490 fffff880`094223a0 00000000`00000000 fffffa80`040f96d0 : nt!MmCleanProcessAddressSpace+0x96 fffff880`094220f0 fffff800`0337a4d1 : 00000000`00000001 fffff800`0304b001 00000000`7ef56000 fffffa80`0408d7c0 : nt!PspExitThread+0x92f fffff880`094221b0 fffff800`030980e3 : 00000000`00000000 00000000`22a8e678 00000000`22a80000 00000000`33b8f9b8 : nt!PsExitSpecialApc+0x1d fffff880`094221e0 fffff800`03098520 : 00000000`22a8e6d0 fffff880`09422260 fffff800`0337a5dc 00000000`00000001 : nt!KiDeliverApc+0x2eb fffff880`09422260 fffff800`030ba8f7 : fffffa80`040f96d0 00000000`7ef56000 00000000`00000020 fffffa80`070bcd10 : nt!KiInitiateUserApc+0x70 fffff880`094223a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c STACK_COMMAND: kb FOLLOWUP_IP: nt!MiDeleteAddressesInWorkingSet+27f fffff800`0308fabb 488b4128 mov rax,qword ptr [rcx+28h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiDeleteAddressesInWorkingSet+27f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+27f BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+27f Followup: MachineOwner ---------
Attached file minidump
Please report BSOD to the vendor of that kernel mode component that caused the crash. A usermode application like Firefox can not cause a BSOD. Firefox only triggers the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
I forgot: Memory corruption could be also a hardware fault (bad RAM, overclocking)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: