Hello,
Today during my work I received irql_not_less_or_equal BSOD and I want to be sure that all hardware in my machine is fine because before one week I replaced my motherboard because problem with memory slots.
I am attaching the dmp file.
Welcome
Before replacing your motherboard did you test if your memory modules are okay?
BSOD Analysis
To make sure your memory modules are good ones follow the tutorial below on MemTest86+ at least for 8 passesCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {1b9411fe0, 2, 1, fffff80002cb3ff0} Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+230 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 00000001b9411fe0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff80002cb3ff0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec5100 00000001b9411fe0 CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveProtoPteFault+230 fffff800`02cb3ff0 4183e01f and r8d,1Fh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: dwm.exe TRAP_FRAME: fffff88009505790 -- (.trap 0xfffff88009505790) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff68000000000 rdx=000007fee2649f80 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cb3ff0 rsp=fffff88009505920 rbp=fffff8a002dfa490 r8=07d4007d8df58021 r9=fffff683ff713248 r10=0000000000000000 r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po nc nt!MiResolveProtoPteFault+0x230: fffff800`02cb3ff0 4183e01f and r8d,1Fh Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c95769 to fffff80002c961c0 STACK_TEXT: fffff880`09505648 fffff800`02c95769 : 00000000`0000000a 00000001`b9411fe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`09505650 fffff800`02c943e0 : 000000f4`00000000 00000000`00000001 fffff8a0`14a09830 fa800fb1`beb00420 : nt!KiBugCheckDispatch+0x69 fffff880`09505790 fffff800`02cb3ff0 : 45100004`0bd1f025 00000004`0bd1f121 fffff880`095053d0 00000000`029dcaf0 : nt!KiPageFault+0x260 fffff880`09505920 fffff800`02cb2aa3 : 00000000`003f59a6 000007fe`e2649f80 fffff683`ff713248 fffffa80`0fa433f8 : nt!MiResolveProtoPteFault+0x230 fffff880`095059b0 fffff800`02ca2749 : 00000000`00000000 000007fe`e2649f80 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3 fffff880`09505ac0 fffff800`02c942ee : 00000000`00000000 000007fe`e2649f80 000007fe`00000001 00000000`0005ba9d : nt!MmAccessFault+0x359 fffff880`09505c20 00000000`77369c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`029dbef0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77369c12 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveProtoPteFault+230 fffff800`02cb3ff0 4183e01f and r8d,1Fh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveProtoPteFault+230 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+230 BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+230 Followup: MachineOwner ---------
RAM - Test with Memtest86+
Then we'll run Driver verifier for finding buggy drivers:
Post back with results
Hello,
After I have started the verifier and rebooted my machine, it started to freeze every time before loading all startup programs, in most cases before loading AMD drivers which i have download from the website.
Is there any chance to check which drivers is causing this issue. I was not able to find out how to view this info and i disabled the verifier.
The verifier puts all drivers under stress. The bad ones will cause BSODS. After 36 hours just give me your dump reports as you did in your earlier post.
Quick update: Whenm i select to verifier all non Microsoft drivers every time when windows starts it freezes.
Any ideas , now i have selected to verifier all AMd drivers and it is loading normal, but if i starts some clip from my browse again it freezes.
I am attaching the monidump files.
I will take a look at the time, in that between get into safe mode and see how your computer performs there.
BSOD Analyze
Still points towards hardware but this time with a different bugcheck and relates to your CPU.
BSOD Index STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR | Usual causes: Hardware, Incompatibility, May be driver corruption
Can you tell me if any part of your computer is overclocked?
Start with stressing your CPU following the tutorial below:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa800f35e358, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_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: fffffa800f35e358, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`0318b6f0 fffff800`02f10ca9 : fffffa80`0f35e330 fffffa80`0c9f5b50 00000000`00000015 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`0318bc10 fffff800`02df1547 : fffffa80`0f35e330 fffff800`02e6b2d8 fffffa80`0c9f5b50 00000000`00000286 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`0318bc40 fffff800`02d58945 : fffff800`02eccae0 00000000`00000001 fffffa80`0fad5220 fffffa80`0c9f5b50 : nt!WheapProcessWorkQueueItem+0x57 fffff880`0318bc80 fffff800`02cd7841 : fffff880`0110de00 fffff800`02d58920 fffffa80`0c9f5b00 fffffa80`0c9f5b50 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`0318bcb0 fffff800`02f64e6a : 12091115`0a12150a fffffa80`0c9f5b50 00000000`00000080 fffffa80`0c9d5040 : nt!ExpWorkerThread+0x111 fffff880`0318bd40 fffff800`02cbeec6 : fffff880`03088180 fffffa80`0c9f5b50 fffff880`03093040 02040202`05020205 : nt!PspSystemThreadStartup+0x5a fffff880`0318bd80 00000000`00000000 : fffff880`0318c000 fffff880`03186000 fffff880`0318ac90 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV Followup: MachineOwner
Next, stress your hardware with Prime95:
Use Speccy for monitoring your temps during the tests:
Also take a look at this for the bugcheck you're getting: Stop 0x124 - what it means and what to try
Take your time and post results of the above
The computer freezes after i started the CPU stress test. It freezed after 32c.
I am attaching the minidump file.
Quote