New
#1
BSOD - Minidump debug
Would someone please debug these minidump files? This has been occurring a min. of 2x per day. Thanks for any help in resolving this crisis.
Would someone please debug these minidump files? This has been occurring a min. of 2x per day. Thanks for any help in resolving this crisis.
ok, the file indicated was one of those red-herring files ike ntoskrnl
here is what I mean
this is a red herring, it is a major OS file which means that it is highly unlikely that it caused the crash.Code:FOLLOWUP_IP: nt!ExAllocatePoolWithTag+4b7 82f314c1 897004 mov dword ptr [eax+4],esi SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!ExAllocatePoolWithTag+4b7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 55a68e73 FAILURE_BUCKET_ID: 0x50_nt!ExAllocatePoolWithTag+4b7 BUCKET_ID: 0x50_nt!ExAllocatePoolWithTag+4b7 Followup: MachineOwner
this is what we need to look at here.Code: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: ffde7b44, memory referenced. Arg2: 00000001, value 0 = read operation, 1 = write operation. Arg3: 82f314c1, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved)
here is my info on the bugcheck:
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
run memtest86+ by following this tutorial:
RAM - Test with Memtest86+
check your BIOS for updates and check temps in the processor and chack the motherboard in case of hardware failure.