BSOD after sleep mode

foxyaardvark

New member
Local time
3:56 PM
Messages
3
I've noticed that my computer shuts off after being in sleep mode for a while. When I reboot and look in EventViewer I find the message: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." Locale ID: 1033.

Here's my computer setup:
Operating System
Microsoft Windows 7 Professional 64-bit
CPU
AMD Phenom II X6 1100T
Thuban 45nm Technology
RAM
8.00 GB Dual-Channel DDR3 @ 715MHz (9-9-9-24)
Motherboard
ASUSTeK Computer INC. M4A79XTD EVO (AM3) 44 °C
Graphics
Generic Non-PnP Monitor (1920x1080@60Hz)
1023MB GeForce GTX 460 SE (EVGA) 30 °C
Hard Drives
932GB Seagate ST31000524AS ATA Device (SATA) 30 °C

I've attached the zipped files from SF diagnostic tool: View attachment 251524

I will note that I recently did a clean install of Windows 7 and the problem remains. I'm really stumped on how to fix this one. Thank you.
 

My Computer

OS
Windows 7 Professional 64 bit
Welcome to SevenForums.

Apparently it looks like MotioninJoy simulate Xbox 360 controller (virtual Xinput device) driver from may is causing the blue screen.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88001912638, 2, 8, fffff88001912638}

*** 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: fffff88001912638, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88001912638, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031050e0
GetUlongFromAddress: unable to read from fffff80003105198
 fffff88001912638 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
MijXfilt+1b638
fffff880`01912638 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:  FFFFF88002F93FB0

TRAP_FRAME:  fffff88002f93b50 -- (.trap 0xfffff88002f93b50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000057ff7042d08
rdx=0000057ff6fa0fd8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001912638 rsp=fffff88002f93ce8 rbp=0000057ff7042d08
 r8=000000000900c420  r9=0000000000000000 r10=fffffa8008fc96a0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
MijXfilt+0x1b638:
fffff880`01912638 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`02f93cf0=20f0050980faffff
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ece469 to fffff80002ecef00

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

STACK_TEXT:  
fffff880`02f93a08 fffff800`02ece469 : 00000000`0000000a fffff880`01912638 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f93a10 fffff800`02ecd0e0 : fffffa80`06a21c68 fffffa80`0905f020 00000000`00000000 fffff800`02ed69ba : nt!KiBugCheckDispatch+0x69
fffff880`02f93b50 fffff880`01912638 : fffff880`00eda047 fffffa80`0905f020 fffffa80`08fc96a0 fffffa80`08fc96a0 : nt!KiPageFault+0x260
fffff880`02f93ce8 fffff880`00eda047 : fffffa80`0905f020 fffffa80`08fc96a0 fffffa80`08fc96a0 fffff800`02ed1516 : MijXfilt+0x1b638
fffff880`02f93cf0 fffff880`00ed999f : 00000000`00000000 fffffa80`0905f020 fffffa80`08fbd2f0 fffffa80`08fbd2f0 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`02f93d70 fffff880`00ed8f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0905f172 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`02f93de0 fffff880`00ede558 : fffffa80`079a4e02 fffffa80`0905f020 fffffa80`079a4c60 fffffa80`0905f020 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`02f93e50 fffff880`00ec8245 : fffffa80`0905f020 fffff880`02f64180 00000000`00000000 fffffa80`0900d538 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`02f93ed0 fffff800`02eda5dc : fffff880`02f64180 00000000`00000000 fffff880`00f77fc0 00000000`00000000 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02f93f00 fffff800`02ed5065 : 00000000`00000000 fffffa80`06a1e040 00000000`00000000 fffff880`00eabccc : nt!KiRetireDpcList+0x1bc
fffff880`02f93fb0 fffff800`02ed4e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`03192510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MijXfilt+1b638
fffff880`01912638 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`018f7000 fffff880`01919000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name:[COLOR="Blue"] MijXfilt.sys[/COLOR]
    Timestamp:        [COLOR="Red"]Sat May 12 10:27:12 2012[/COLOR] (4FADE6A0)
    CheckSum:         00022009
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
I would check for a update on its driver, or roll back to a last known stable driver and see if that helps resolve the BSOD issue.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps
You're welcome.
Let us know how it went.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps
Back
Top