New
#11
Alright Gianni.
This could be a Memory Corruption or a driver issue. First thing we want to do is to check your RAM-sticks for errors. An amazing little running troubleshooting tester will do the trick! Follow the tutorial below and post back your results.
RAM - Test with Memtest86+
It'll tell you if any errors we're found. Let it be running for like 7 passes, the tutorial will cover all this.
Bugcheck
Fred.Code: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: 0000da04, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, 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: 82aa503d, address which referenced memory