Hello,
I have been experiencing frequent system crashes on my system (Windows 7 64bit). This is a rather new system so my initial thought was corrupted memory modules. I did run three different checks with Memtest86+ that showed that all was ok.
I have included my latest minidump files + a driver list in the attachment. Any further assistance is more than welcome to locate this problem.
Thank you.
Hi Lefterisd and welcome
The first parameter (c0000005) is a memory exception. The DMP files are fairly vague but I suspect it is still memory. I would run memtest for at least 5-6 passes.
If you still experience no errors in memtest, and have BSOD's I would also run a system file check. To do so you need to type cmd in search. Then right click and run as an administrator. Finally type SFC /SCANNOW.
Let us know if you need further assistance.
Jan
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\071810-15054-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50 Debug session time: Sun Jul 18 00:49:45.634 2010 (GMT-4) System Uptime: 0 days 0:45:24.945 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ....................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002a42068, fffff880027aac20, 0} Probably caused by : ntkrnlmp.exe ( nt!RtlpAllocateHeap+1dc ) Followup: MachineOwner ---------
Quote