New
#1
NoteThat Minidumps only provide clues to your problem and not an actual answer
WarningMemory was a possible Issue here so please check your Memory with a System Repair Disk
See System Repair Disc - Create For More Information
Also can I ask what is your Pagefile Size and is it managed by Windows?
For Reference:
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Josh\Desktop\BSOD files (10).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 Executable search path is: Windows 7 Kernel Version 7600 UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.x86fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0x82c4c000 PsLoadedModuleList = 0x82d94810 Debug session time: Sat Feb 12 07:19:25.468 2011 (UTC + 0:00) System Uptime: 0 days 0:00:07.375 Loading Kernel Symbols ............................................................... ................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C5, {65e8, 2, 0, 82d6c795} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+135 ) Followup: Pool_corruption ---------Hope This Helps,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 000065e8, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 82d6c795, address which referenced memory Debugging Details: ------------------ BUGCHECK_STR: 0xC5_2 CURRENT_IRQL: 2 FAULTING_IP: nt!ExDeferredFreePool+135 82d6c795 8b10 mov edx,dword ptr [eax] DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System TRAP_FRAME: 8078614c -- (.trap 0xffffffff8078614c) ErrCode = 00000000 eax=000065e8 ebx=000001ff ecx=000001ff edx=82d81a20 esi=85ca3b90 edi=82d818c0 eip=82d6c795 esp=807861c0 ebp=807861f8 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!ExDeferredFreePool+0x135: 82d6c795 8b10 mov edx,dword ptr [eax] ds:0023:000065e8=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 82d6c795 to 82c9282b STACK_TEXT: STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+135 82d6c795 8b10 mov edx,dword ptr [eax] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExDeferredFreePool+135 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+135 BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+135 Followup: Pool_corruption ---------
Josh
I Did check my device manager and I find no errors in my device except my Microsoft ISATAP Adapter, Microsoft ISATAP Adapter #2, Microsoft ISATAP Adapter #3 and microsoft Teredo tunneling Adapter. It says This device cannot start. (Code 10)
my Page File Size is 1472 mb used, 3643mb available ( got it from dxdiag )
What do you mean it is managed by Microsoft?