Hi everyone,
I recently bought a new desktop PC that runs on Windows 7 and after about two weeks, the Flash and Java plug-ins started crashing, and now I keep getting a MEMORY_MANAGEMENT BSOD constantly. Switching browsers has not helped a bit. I have created a dump file, which you can find attached.
I really hope someone can help me and I appreciate the efforts!
Welcome
Your dumps are taking a lot of time to load. Please grab them with the instruction utility again and re-upload them.
From one dump that was able to load:
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Yusra\Downloads\TreeFiddy350\SF_19-09-2012\091912-27066-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504 Machine Name: Kernel base = 0x82c0c000 PsLoadedModuleList = 0x82d554d0 Debug session time: Thu Sep 20 03:46:00.923 2012 (UTC + 6:00) System Uptime: 0 days 0:36:23.609 Loading Kernel Symbols ............................................................... ................................................................ ............................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {c0851a40, 0, 0, 82c73b7e} *** WARNING: Unable to verify timestamp for SYMEVENT.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS Probably caused by : SYMEVENT.SYS ( SYMEVENT+17079 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: c0851a40, memory referenced Arg2: 00000000, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82c73b7e, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82d75848 Unable to read MiSystemVaType memory at 82d54e20 c0851a40 CURRENT_IRQL: 0 FAULTING_IP: nt!MiLocateWsle+97 82c73b7e 8b049e mov eax,dword ptr [esi+ebx*4] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: chrome.exe TRAP_FRAME: b379d85c -- (.trap 0xffffffffb379d85c) ErrCode = 00000000 eax=c0c0bf5c ebx=00013b4e ecx=00606058 edx=c0802000 esi=c0802d08 edi=02bd7001 eip=82c73b7e esp=b379d8d0 ebp=b379d8dc iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt!MiLocateWsle+0x97: 82c73b7e 8b049e mov eax,dword ptr [esi+ebx*4] ds:0023:c0851a40=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 82c73b7e to 82c4d65b STACK_TEXT: b379d85c 82c73b7e badb0d00 c0802000 c0802000 nt!KiTrap0E+0x2cf b379d8dc 82caba55 c0c0bf5c 02c56fff 02bd0002 nt!MiLocateWsle+0x97 b379d9d8 82cac28c 02bd0002 02c56fff 86625808 nt!MiDeleteVirtualAddresses+0x1b5 b379daa8 82cabf41 86625808 865c6470 86539a40 nt!MiRemoveMappedView+0x325 b379dad0 82e53417 86539a40 00000000 c0000001 nt!MiRemoveVadAndView+0xe5 b379db30 82e718af 86625808 02bd0000 00000000 nt!MiUnmapViewOfSection+0x265 b379db50 b399e079 ffffffff 02bd0000 85e1d938 nt!NtUnmapViewOfSection+0x55 WARNING: Stack unwind information not available. Following frames may be wrong. b379dbd4 82c4a27a ffffffff 02bd0000 b379dcec SYMEVENT+0x17079 b379dbd4 00400000 ffffffff 02bd0000 b379dcec nt!KiFastCallEntry+0x12a b379dc44 00000000 82c495f9 00000008 00000202 0x400000 STACK_COMMAND: kb FOLLOWUP_IP: SYMEVENT+17079 b399e079 ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: SYMEVENT+17079 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SYMEVENT IMAGE_NAME: SYMEVENT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4ecbea42 FAILURE_BUCKET_ID: 0xA_SYMEVENT+17079 BUCKET_ID: 0xA_SYMEVENT+17079 Followup: MachineOwner --------- 1: kd> lmvm SYMEVENT start end module name b3987000 b39b1000 SYMEVENT T (no symbols) Loaded symbol image file: SYMEVENT.SYS Image path: \??\C:\Windows\system32\Drivers\SYMEVENT.SYS Image name: SYMEVENT.SYS Timestamp: Wed Nov 23 00:30:26 2011 (4ECBEA42) CheckSum: 00027540 ImageSize: 0002A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4Please uninstall Norton Internet Security. This antivirus alone is a known cause to BSoDs. Also uninstall Daemon Tools. (Search our forum, you'll find allot of issues with this program)Code:Start Menu\Programs\Norton Internet Security Public:Start Menu\Programs\Norton Internet Security Public
* Download and install MSE. Run a full scan when updated.
Microsoft Security Essentials - Free Antivirus for Windows
* For additional security, recommend Malware bytes. (Also run full scan once installed)
* System file checker for repairing any damaged files within windows
Keep us posted
Hi guys,
again my computer is experiencing BSODs, along with constant crashes of Flash in Chrome and Firefox. I attached the ZIP folder with the dump file to this thread and hope that you will be able to open them. I really appreciate your help, as I am a total newbie to this and have no idea how to fix it. Thanks again!
Cheers,
TreeFiddy350
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, c0802170, ffff, 0} Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+389 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 00041790, A page table page has been corrupted. On a 64 bit OS, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit OS, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs. Arg2: c0802170 Arg3: 0000ffff Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82ccbdfe to 82ccd413 STACK_TEXT: c1393c14 82ccbdfe 887c4950 887c4950 00000000 nt!MiDeleteAddressesInWorkingSet+0x389 c1393c40 82e76897 ed972351 87cbed48 00000002 nt!MmCleanProcessAddressSpace+0x8c c1393cb4 82e8a1c7 00000000 859726b0 00000001 nt!PspExitThread+0x685 c1393ccc 82cbdbd0 859726b0 c1393cf8 c1393d04 nt!PsExitSpecialApc+0x22 c1393d1c 82c4a954 00000001 00000000 c1393d34 nt!KiDeliverApc+0x28b c1393d1c 77477094 00000001 00000000 c1393d34 nt!KiServiceExit+0x64 WARNING: Frame IP not in any known module. Following frames may be wrong. 0214fd04 00000000 00000000 00000000 00000000 0x77477094 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiDeleteAddressesInWorkingSet+389 82ccd413 cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiDeleteAddressesInWorkingSet+389 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 50e793e8 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x1a_41790_nt!MiDeleteAddressesInWorkingSet+389 BUCKET_ID: 0x1a_41790_nt!MiDeleteAddressesInWorkingSet+389 Followup: MachineOwner ---------
RAM - Test with Memtest86+
NotePay close attention to part 3 of the tutorial in order to rule out the faulty stick.
InformationErrors are sometimes found after 8 passes.
TipDo this test overnight, before going to bed.
Thank you!
Quote