localITguy
Suspended
- Joined
- Dec 13, 2013
- Messages
- 17,788
- Reaction score
- 1,674
thks bro for the help... dump file is taken from C:/windows/minidump? how do i attach the mini dumpfile to HWZ? or can i send to ur email?
mediafire.com
thks bro for the help... dump file is taken from C:/windows/minidump? how do i attach the mini dumpfile to HWZ? or can i send to ur email?
Turns out might be RAM issues.![]()
RAM. Swap, monitor, report here.
thks for taking a look... this minidump was created after the benchmarks test when back to desktop and crash again... do u need the minidump file when the benchmarks test?
the minidump file from the initial benchmarks test crash
http://www.mediafire.com/download/euu92l1eutmx2lu/051916-3437-01.dmp
the problem is i dun hav extra ram... this is the only rig after 10 yrs of break was using laptop this time round...

well if u are urgent den buy new ram, if not u try cleaning the gold contact with eraser and reseat it. else still buy ram![]()
itz possible i rma the ram and bring the mini dump file from them to see?wah no budget for new ram lolitz possible i rma the ram and bring the mini dump file from them to see?
still the same error:
HEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00021527028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200135, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
BAD_PAGES_DETECTED: 4d30
STACK_TEXT:
ffffd001`e7f625f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 19760 instance(s) of page corruption, target is likely to have memory corruption.
RAM issues.
anyway u can upload to this website to view as well :
http://www.osronline.com/page.cfm?name=Analyze
try to have your RAM in A2/B2 slots, these are the 2nd and 4th slot from the CPU. and make sure the RAM settings are for DDR4-2133. if still unstable, try a little more DRAM voltage, you can try 1.21V or 1.22V.
*Update
yesterday i try running single ram on slot 2 with Valley Benchmark 1.0 running for 2hrs + on each ram no BSOD or any error... i try on slot 4 today and see weather might be mobo slot problem will update again tyvm for ur time guys

well tbh since we know it could be ram issues, why not just do a ram test and see![]()
yea true but i dun really know how to run memtest... read that must burn into a bootable usb etc... but i will try to do that and report b the result thks