BSOD only when computer is idle

Welcome to SevenForums

If you have a SSD, make sure the firmware is up to date

If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics.

Code:

Start Menu\Programs\ASUS	Public:Start Menu\Programs\ASUS	Public
Start Menu\Programs\ASUS\AI Suite II	Public:Start Menu\Programs\ASUS\AI Suite II	Public

This is overclocking software and can lead to system instability and BSOD's. Please reset all components to their stock speeds and then remove the software.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800a71d638, 2, 8, fffff8800a71d638}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+1b638 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800a71d638, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8800a71d638, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800048c6100
GetUlongFromAddress: unable to read from fffff800048c61c0
 fffff8800a71d638 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
MijXfilt+1b638
fffff880`0a71d638 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88004BA1FB0

TRAP_FRAME:  fffff88004ba1b00 -- (.trap 0xfffff88004ba1b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000057ff5dd4538
rdx=0000057ff5d78838 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800a71d638 rsp=fffff88004ba1c98 rbp=fffff88004ba1ce0
 r8=000000000a258248  r9=0000000000000000 r10=fffffa800a228e40
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
MijXfilt+0x1b638:
fffff880`0a71d638 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`04ba1ca0=c077280a80faffff
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004696569 to fffff80004696fc0

FAILED_INSTRUCTION_ADDRESS: 
MijXfilt+1b638
fffff880`0a71d638 48895c2408      mov     qword ptr [rsp+8],rbx

STACK_TEXT:  
fffff880`04ba19b8 fffff800`04696569 : 00000000`0000000a fffff880`0a71d638 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`04ba19c0 fffff800`046951e0 : fffffa80`098f81b0 fffff880`099786eb fffffa80`00000000 fffffa80`0a2877c0 : nt!KiBugCheckDispatch+0x69
fffff880`04ba1b00 fffff880`0a71d638 : fffff880`00e7d042 fffffa80`0a2877c0 fffffa80`0a2877c0 fffff880`04ba1ce0 : nt!KiPageFault+0x260
fffff880`04ba1c98 fffff880`00e7d042 : fffffa80`0a2877c0 fffffa80`0a2877c0 fffff880`04ba1ce0 00000000`00000040 : MijXfilt+0x1b638
fffff880`04ba1ca0 fffff880`00e7c42f : fffffa80`0a22ba00 fffffa80`00000000 fffffa80`0a22bac0 fffffa80`0a22d208 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x542
fffff880`04ba1d20 fffff880`00e87fbb : fffffa80`0a228e40 fffffa80`0a287702 00000000`00000000 fffffa80`0a2877c0 : Wdf01000!FxIoQueue::DispatchEvents+0x66f
fffff880`04ba1da0 fffff880`00e8130a : fffffa80`0a228e02 fffffa80`0a2877c0 fffffa80`0a259010 fffff880`04ba1e80 : Wdf01000!FxIoQueue::QueueRequest+0x2ab
fffff880`04ba1e10 fffff880`00e809da : fffffa80`0a2877c0 fffffa80`0a259010 00000000`00000000 fffffa80`0a259010 : Wdf01000!FxPkgIo::Dispatch+0x4da
fffff880`04ba1e80 fffff880`00e80aa6 : fffffa80`0a259010 00000000`00000000 fffffa80`0a234570 00000000`00000000 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`04ba1ec0 fffff800`046a16ec : fffff880`04b72180 00000000`00000000 fffffa80`0a258fa8 00000000`00000095 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`04ba1f00 fffff800`0469a105 : 00000000`00000000 fffffa80`06a5c040 00000000`00000000 fffff880`00ed35e8 : nt!KiRetireDpcList+0x1bc
fffff880`04ba1fb0 fffff800`04699f1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`04f083e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MijXfilt+1b638
fffff880`0a71d638 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  MijXfilt+1b638

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MijXfilt

IMAGE_NAME:  MijXfilt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fade6a0

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_MijXfilt+1b638

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_MijXfilt+1b638

Followup: MachineOwner
---------

2: kd> lmvm MijXfilt
start             end                 module name
fffff880`0a702000 fffff880`0a724000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        Sat May 12 10:27:12 2012 (4FADE6A0)
    CheckSum:         00022009
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> !sysinfo
!sysinfo [ cpuinfo | cpumicrocode | cpuspeed | gbl | machineid | registers | smbios ] [-csv | -noheaders]
2: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3596

Reinstall drivers afresh for your MotioninJoy simulate Xbox 360 controller (virtual Xinput device) (latest version/drivers if available)

Daemon Tools

Code:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.

Post back results.