Sign in with
Sign up | Sign in
Your question

Bluescreen

Last response: in Windows 7
Share
January 11, 2013 5:10:42 PM

Built my new computer over the xmas break and just a few days ago started to get this message any help would be appreciated

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88000F2500F
BCP3: FFFFF8800A6BB328
BCP4: FFFFF8800A6BAB80
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

More about : bluescreen

January 12, 2013 2:17:06 AM

On Fri 1/11/2013 6:30:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-11232-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x4F00F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000F2500F, 0xFFFFF8800A6BB328, 0xFFFFF8800A6BAB80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 1/11/2013 6:30:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mijxfilt.sys (MijXfilt+0x38E9)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88000F2500F, 0xFFFFF8800A6BB328, 0xFFFFF8800A6BAB80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\mijxfilt.sys
product: MotioninJoy DS3 driver
company: MotioninJoy
description: MotioninJoy DS3 driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: MotioninJoy SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Tue 1/8/2013 6:29:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-14352-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x53EA1)
Bugcheck code: 0xFC (0xFFFFF88008C00C70, 0x800000003BC49963, 0xFFFFF880059803C0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 1/6/2013 8:04:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-17113-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x4F00F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000E9100F, 0xFFFFF8800CDD72F8, 0xFFFFF8800CDD6B50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
m
0
l
Related resources
a b $ Windows 7
January 12, 2013 2:52:27 AM

Try using the information HERE as it matches the files that caused yours.
m
0
l
!