Solved Had my computer for awhile recently started getting BSOD

[MistakenGeneral]

Since Ive had an issue with hardware on an old computer I just reformatted it everytime this would come up. Now that I built my custom PC but about a month or so ago I've started to get BSOD and I'm not quite sure how to fix it. No idea how to get the error reports or anything, my computer usually just restarts and I tend to ignore them, and at this point I don't think its healthy. I've also noticed sometimes that my computer starts up very slow lately, and I have to restart it manually for it to load up properly and as fast as it use to.

I've uploaded the logs.

 

[Tews]

Please follow these instructions and attach the results to your next post.


http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[Arc]

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[MistakenGeneral]

I've done so!

 

[Arc]

Hi.

Uninstall the MotioninJoy simulate Xbox 360 controller and install the earlier version; from Playstation 3 controller(Dualshcok 3 or Sixaxis) driver for windows | MotioninJoy

Let us know the results.
______________________________

BugCheck 10D, {5, 0, 1202, fffffa8019138e40}

*** 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+363a )

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

 

[MistakenGeneral]

Hello! I'm sure this is what you were talking about, I actually have been using better DS3 for my controller games, I'm not sure if that involves motionjoy or not. But I believe it's removed, I'm not sure whether or not I'll still get a BSOD since I think I've had them before I've installed motionjoy's driver

INFO:ENTER: DriverPackageUninstallW

INFO:Uninstalling driver package C:\Program Files\MotioninJoy\ds3\drivers\MijXinput.inf...

INFO:Successfully uninstalled 'C:\Windows\INF\oem59.inf'.

SUCCESSevice with device instance ID 'USB\VID_054C&PID_0268\5&EA04C51&0&4' reinstalled.

INFO:Successfully uninstalled 1 devices for C:\Windows\System32\DriverStore\FileRepository\mijxinput.inf_amd64_neutral_aad1beabb2f836a4\mijxinput.inf.

INFO:Successfully deleted properties for driver store entry 'C:\Windows\System32\DriverStore\FileRepository\mijxinput.inf_amd64_neutral_aad1beabb2f836a4\mijxinput.inf'.

SUCCESS:Uninstall completed.

INFO:RETURN: DriverPackageUninstallW (0x0)

 

[Arc]

OK, report us for any further BSOD.

 

[MistakenGeneral]

Alrighty sounds good! Thanks for all your help so far! I'll be sure to do so, Have a great weekend!

 

[MistakenGeneral]

OK, report us for any further BSOD.

Welp, I'm still getting blue screens, hopefully you can reply to this so I don't have to create another post! I'll submit new logs.

 

[Arc]

If you want us to help you for your BSOD issue, you need to upload the data as suggested in post #3.

 

[MistakenGeneral]

Apparently it said it was attatched, but it wasn't.

 

[Arc]

It is a totally different issue.

[COLOR=Red]BugCheck A0000001[/COLOR], {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+2824e )

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

A stop 0xA0000001 is associated with the AMD/ATI display environment.

As the first try, apply a driver known to be stable. Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

Let us know whether the issue continues with the changed driver or not.

 

[MistakenGeneral]

So I'm still having BSOD issues, I'm completely uninstalled all drivers for DS3. That may have been conflicting. And I still have a problem. I'm uploading the file now.

 

[Arc]

So I'm still having BSOD issues, I'm completely uninstalled all drivers for DS3. That may have been conflicting. And I still have a problem. I'm uploading the file now.

My last reply to you was on 30th May 2014, and the latest crash dump included in the zip is of 29th July 2014. And it is visually explicit that you overlooked/neglected/nullified the suggestion given there.

You are supposed to install 13.9 WHQL and you have installed 14.2 BETA ver. 1.3.

So, what more I can say/do for you?
________________________________________

....
[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8801111a83b, fffff8800423e228, fffff8800423da80}

[COLOR=Red]Probably caused by : atikmdag.sys[/COLOR] ( atikmdag+c483b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8801111a83b, The address that the exception occurred at
Arg3: fffff8800423e228, Exception Record Address
Arg4: fffff8800423da80, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
atikmdag+c483b
fffff880`1111a83b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD:  fffff8800423e228 -- (.exr 0xfffff8800423e228)
ExceptionAddress: fffff8801111a83b (atikmdag+0x00000000000c483b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT:  fffff8800423da80 -- (.cxr 0xfffff8800423da80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000070000 rdi=0000000000000002
rip=fffff8801111a83b rsp=fffff8800423e460 rbp=fffffa800f20b060
 r8=0000000000000002  r9=000000f415480000 r10=0000000000000000
r11=fffff8800423e690 r12=fffffa800f1fabc0 r13=fffffa800e9c6e00
r14=fffffa8017bca010 r15=fffff88011056000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc483b:
fffff880`1111a83b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000070000 rdi=0000000000000002
rip=fffff8801111a83b rsp=fffff8800423e460 rbp=fffffa800f20b060
 r8=0000000000000002  r9=000000f415480000 r10=0000000000000000
r11=fffff8800423e690 r12=fffffa800f1fabc0 r13=fffffa800e9c6e00
r14=fffffa8017bca010 r15=fffff88011056000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc483b:
fffff880`1111a83b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003708100
GetUlongFromAddress: unable to read from fffff800037081c0
 00000000000006a8 Nonpaged pool

FOLLOWUP_IP: 
atikmdag+c483b
fffff880`1111a83b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000005b80000 to fffff8801111a83b

STACK_TEXT:  
fffff880`0423e460 00000000`05b80000 : 00000000`05b99fff fffffa80`0f1fabc0 00000000`00000003 fffffa80`17bca010 : atikmdag+0xc483b
fffff880`0423e468 00000000`05b99fff : fffffa80`0f1fabc0 00000000`00000003 fffffa80`17bca010 fffff880`1117948f : 0x5b80000
fffff880`0423e470 fffffa80`0f1fabc0 : 00000000`00000003 fffffa80`17bca010 fffff880`1117948f 00000000`00000100 : 0x5b99fff
fffff880`0423e478 00000000`00000003 : fffffa80`17bca010 fffff880`1117948f 00000000`00000100 fffffa80`0f215b50 : 0xfffffa80`0f1fabc0
fffff880`0423e480 fffffa80`17bca010 : fffff880`1117948f 00000000`00000100 fffffa80`0f215b50 00000000`00000098 : 0x3
fffff880`0423e488 fffff880`1117948f : 00000000`00000100 fffffa80`0f215b50 00000000`00000098 000014e0`00000098 : 0xfffffa80`17bca010
fffff880`0423e490 00000000`00000100 : fffffa80`0f215b50 00000000`00000098 000014e0`00000098 00000000`00000000 : atikmdag+0x12348f
fffff880`0423e498 fffffa80`0f215b50 : 00000000`00000098 000014e0`00000098 00000000`00000000 00000000`00000001 : 0x100
fffff880`0423e4a0 00000000`00000098 : 000014e0`00000098 00000000`00000000 00000000`00000001 00000000`ffffffff : 0xfffffa80`0f215b50
fffff880`0423e4a8 000014e0`00000098 : 00000000`00000000 00000000`00000001 00000000`ffffffff fffff880`0423e730 : 0x98
fffff880`0423e4b0 00000000`00000000 : 00000000`00000001 00000000`ffffffff fffff880`0423e730 fffff880`0423e5e0 : 0x000014e0`00000098


SYMBOL_STACK_INDEX:  0

[COLOR=Red]SYMBOL_NAME:  atikmdag[/COLOR]+c483b

FOLLOWUP_NAME:  MachineOwner

[COLOR=Red]MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  530abc59

STACK_COMMAND:  .cxr 0xfffff8800423da80 ; kb

[COLOR=Red]FAILURE_BUCKET_ID:  X64_0x7E_atikmdag[/COLOR]+c483b

[COLOR=Red]BUCKET_ID:  X64_0x7E_atikmdag[/COLOR]+c483b

ANALYSIS_SOURCE:  KM

[COLOR=Red]FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag[/COLOR]+c483b

FAILURE_ID_HASH:  {dc9cc0b9-993f-663d-42f6-2cf123a43aab}

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

0: kd> lmvm atikmdag
start             end                 module name
fffff880`11056000 fffff880`11df7000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
[COLOR=Red]    Image name: atikmdag.sys
    Timestamp:        Mon Feb 24 08:58:25 2014[/COLOR] (530ABC59)
    CheckSum:         00D51E69
    ImageSize:        00DA1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[MistakenGeneral]

I did exactly as said in the last post after I submitted my log on saturday.