Jump to content

Decoding Memtest86 results

Chris_R.
By Chris_R.
in Troubleshooting
 Share
Go to solution Solved by ionbasa,

Okay, So I tested each stick individually. One came up bad after testing each stick for 4 passes. I took that stick out, but it still Blue-screens.

 

This latest BSOD bug check string was entitled "ATTEMPTED_WRITE_TO_READONLY_MEMORY." --Any thoughts?

 

I uploaded it to the same google drive linked previously, It is entitled "NEW MEMORY DUMP AFTER MEMTEST" followed by the system name

 

I'm considering running memtest all night tonight with my known good 8GB set and if it comes back with errors, I'll know it's the CPU thoughts?

Looked at the minidump file, and well, its basically empty. No stack information, that tells me that something is definitely wrong and it's Memory related. I see it was while playing BF4 though.

You can try re-running the memtest with just 12 Gb of your 16Gb kit (leaving the faulty one out). Check if Memtest finds errors. If it does, then try re-running the Memtest with your 8 Gigabyte kit which should work. If it also fails, then it's definitely the CPU memory controller. 

 

If the 8Gb kit passes, then maybe you got unlucky with your 16Gb Corsair memory. 

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck BE, {fffff8a0070838c0, 80000002f3277121, fffff88009193080, b}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )Followup: MachineOwner---------3: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)An attempt was made to write to readonly memory.  The guilty driver is on thestack trace (and is typically the current instruction pointer).When possible, the guilty driver's name (Unicode string) is printed onthe bugcheck screen and saved in KiBugCheckDriver.Arguments:Arg1: fffff8a0070838c0, Virtual address for the attempted write.Arg2: 80000002f3277121, PTE contents.Arg3: fffff88009193080, (reserved)Arg4: 000000000000000b, (reserved)Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xBEPROCESS_NAME:  bf4.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000STACK_TEXT:  00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0STACK_COMMAND:  kbSYMBOL_NAME:  ANALYSIS_INCONCLUSIVEFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: Unknown_ModuleIMAGE_NAME:  Unknown_ImageDEBUG_FLR_IMAGE_TIMESTAMP:  0IMAGE_VERSION:  BUCKET_ID:  INVALID_KERNEL_CONTEXTFAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXTANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:invalid_kernel_contextFAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}Followup: MachineOwner 
Posted

Hello everyone, I just finished running memtest86 as a last resort, and I was going to ask if someone perhaps knew what these results mean.

 

Symptoms : Random BSOD's {Specifically bug codes: atikmdag.sys ; Paged_File_in blabla ; PFN_LIST Corrupt ; and the list goes on.

 

I have done this so far

  • New motherboard
  • New Ram
  • Tried different graphics cards
  • tried different graphic drivers
  • tried different versions of diretx
  • tried different versions of Microsoft c++ dist.
  • re-formatted windows several times
  • tried another HDD
  • tried a different SATA cable
  • tried a different SATA port
  • tried another PSU

So, as you can see I'm basically at the end of the line. I'm thinking maybe cpu memory controller?

 

Here are some pictures of the Memtest86 results

 

IMG_20150829_194546211_zpsu5tbbp2l.jpg

 

IMG_20150829_215128134_zps3wwgx99m.jpg

 

As always, any help is appreciated.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Hello everyone, I just finished running memtest86 as a last resort, and I was going to ask if someone perhaps knew what these results mean.

 

Symptoms : Random BSOD's {Specifically bug codes: atikmdag.sys ; Paged_File_in blabla ; PFN_LIST Corrupt ; and the list goes on.

 

I have done this so far

  • New motherboard
  • New Ram
  • Tried different graphics cards
  • tried different graphic drivers
  • tried different versions of diretx
  • tried different versions of Microsoft c++ dist.
  • re-formatted windows several times
  • tried another HDD
  • tried a different SATA cable
  • tried a different SATA port
  • tried another PSU

So, as you can see I'm basically at the end of the line. I'm thinking maybe cpu memory controller?

 

If you have tried new RAM and Mobo then I guess its your CPU, although have you tested with a single stick of RAM?

*Risky click of the day*

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@chris_R. I've never used that utility, but...  is it showing your 1600MHz memory running at 800MHz?    <ponders> could too slow cause failures? </ponders>

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

If you have tried new RAM and Mobo then I guess its your CPU, although have you tested with a single stick of RAM?

 

I.....I think so {lol it's been such a long road} I did stick by stick on my old Z87 board and it began BSOD'ing whenever I added a second channel. Didn't matter what stick.... Thought the board was the problem. wasn't..

 

 

@chris_R. I've never used that utility, but...  is it showing your 1600MHz memory running at 800MHz?    <ponders> could too slow cause failures? </ponders>

I did try upping the speed to a manual 1600 on the old board but it caused the CPU to overheat {or more warmer that it had been running for 1 and a half years} @ 65-67C and still gave bsod's If i can recall correctly

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@ionbasa might have some answers for you

CPU: i5 6600k @ 4.6 ghz  Motherboard: Asus z170-a  Cooling: Corsair h80i GT GPU: EVGA GTX 970  Ram: G.Skill 2x8 gb ddr4 2400  PSU: EVGA G2 Supernova 550w  Case: Corsair 200r Storage: 250GB 850 EVO + 2x wd 1 tb drives

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

@ionbasa might have some answers for you

Should I private message him a copy of the post?

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)

Should I private message him a copy of the post?

Just post a link to the previous thread you had. Also please follow the BSOD posting guideline pinned in the top of this subforum: http://linustechtips.com/main/forum/46-troubleshooting/

 

I'll go through the details. It may take me some time to comb through everything, but I always post back. Even if it takes me a few hours to do so.

EDIT:

Looking at the screenshots from the memory test: You can convert the Hex address space of 241D3BA0 to Decimal (which is 605895584). That corresponds to roughly to about the ~600 Meg point on a RAM DIMM. Although, we can't know for sure if the RAM is faulty. I'll need some dump files if possible. 

 

Manually converting the Hex addresses to realspace isn't a good strategy either, as it doesn't tell us which DIMM, or what module on the DIMM is having issues. It also tells us nothing about the memory controller, etc.The 600Meg threshold could technically be anywhere on any of the DIMMS, and it's up to the Memtest Linux kernel to assign the memory space.

Edited by ionbasa

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Done. Just glanced at the first line of the perfmon /report {brand new to me I may see the prob already}

 

Sorry for the improper bsod format, here is everything requested. Both in a .Zip file on Google Drive. "Report 1" = perfmon /report

 

Hope this link works

 

https://drive.google.com/folderview?id=0B5B6yyhmjnvGfk1Qbzlhcnh0Wk5La2pZVzRtSW1rYzVfMUJHdm1JSWpvYmtKLVQxR3FjLVk&usp=sharing

 

EDIT ::::::: it has only found one minidump file...but I assure you there have been many more blusecreens. For some reason, they are not showing in the minidump folder.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Done. Just glanced at the first line of the perfmon /report {brand new to me I may see the prob already}

 

Sorry for the improper bsod format, here is everything requested. Both in a .Zip file on Google Drive. "Report 1" = perfmon /report

 

Hope this link works

 

https://drive.google.com/folderview?id=0B5B6yyhmjnvGfk1Qbzlhcnh0Wk5La2pZVzRtSW1rYzVfMUJHdm1JSWpvYmtKLVQxR3FjLVk&usp=sharing

 

EDIT ::::::: it has only found one minidump file...but I assure you there have been many more blusecreens. For some reason, they are not showing in the minidump folder.

For now, 1 minidump is better than none. You can manually check if there are more by trying to open "%systemroot%\Minidump\" in file explorer, do you see any more dump files?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)
  • Author

For now, 1 minidump is better than none. You can manually check if there are more by trying to open "%systemroot%\Minidump\" in file explorer, do you see any more dump files?

Done. It brought up the minidump folder. Still just the 1 minidump from yesterday. I will try to make it bluescreen again and see if more minidumps show up.

 

 

EDIT::: I made it bluescreen again, but no minidump file is showing. For the few seconds I see the BSOD I do see the percentages at the bottom showing how much data is being collected / dumped.

Edited by Chris_R.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Done. It brought up the minidump folder. Still just the 1 minidump from yesterday. I will try to make it bluescreen again and see if more minidumps show up.

Do you happen to have an "MEMORY.DMP" file under "C:\Windows\"? I can see that there should be one more. But the dump file is huge.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Done. It brought up the minidump folder. Still just the 1 minidump from yesterday. I will try to make it bluescreen again and see if more minidumps show up.

 

 

EDIT::: I made it bluescreen again, but no minidump file is showing. For the few seconds I see the BSOD I do see the percentages at the bottom showing how much data is being collected / dumped.

Mind seeing if it's set to actually collect the minidump: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html (and not overwirte the old one)?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Typed it into the {windows 7} startmenu search bar and yes it did come up under "programs"

 

Checking manually, yes it is there just as you typed it, under C:\Windows

 

Would you like for me to post it with google docs?

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Typed it into the {windows 7} startmenu search bar and yes it did come up under "programs"

 

Checking manually, yes it is there just as you typed it, under C:\Windows

 

Would you like for me to post it with google docs?

If possible yes. It's only around 800 Megabytes?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

It is currently set on Kernel Memory Dump @ the MEMORY.DMP file you mentioned. and the overwrite box is checked

Change it Small Memory dump so it looks like this: 

164421d1310371661-dump-files-configure-w

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Okay. Done, The Original 801 ish MB MEMORY.DUMP file is uploading as I type this should be about halfway done, same folder linked.

 

I am trying to make it blue-screen again , but bf4 is only crashing now {how I've been able to blue-screen} instead of actually loading the game. I will keep trying.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)

Okay. Done, The Original 801 ish MB MEMORY.DUMP file is uploading as I type this should be about halfway done, same folder linked.

 

I am trying to make it blue-screen again , but bf4 is only crashing now {how I've been able to blue-screen} instead of actually loading the game. I will keep trying.

Okay, so the first one I got did blame the AMD driver, although the driver crashed because of a memory access violation. Once we get one two two more dump we can narrow it down.

 

 

EDIT: Just saw the MEMORY.dmp file show up on drive, will take a look at it.

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000007E, {ffffffffc0000005, fffff8800f187080, fffff88005b381e8, fffff88005b37a40}Probably caused by : atikmdag.sys ( atikmdag+bb080 )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8800f187080, The address that the exception occurred atArg3: fffff88005b381e8, Exception Record AddressArg4: fffff88005b37a40, Context Record AddressDebugging Details:------------------EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.FAULTING_IP: atikmdag+bb080fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h]EXCEPTION_RECORD:  fffff88005b381e8 -- (.exr 0xfffff88005b381e8)ExceptionAddress: fffff8800f187080 (atikmdag+0x00000000000bb080)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 0000001b96ba44a0Attempt to read from address 0000001b96ba44a0CONTEXT:  fffff88005b37a40 -- (.cxr 0xfffff88005b37a40;r)rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Last set context:rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  0000001b96ba44a0READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800039080e8GetUlongFromAddress: unable to read from fffff80003908198 0000001b96ba44a0 Nonpaged poolFOLLOWUP_IP: atikmdag+bb080fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h]BUGCHECK_STR:  0x7EANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8800f18282f to fffff8800f187080STACK_TEXT:  fffff880`05b38428 fffff880`0f18282f : fffff8a0`16f4b010 00000000`00000000 00000000`00000001 fffff880`0f182163 : atikmdag+0xbb080fffff880`05b38430 fffff8a0`16f4b010 : 00000000`00000000 00000000`00000001 fffff880`0f182163 00000000`00000002 : atikmdag+0xb682ffffff880`05b38438 00000000`00000000 : 00000000`00000001 fffff880`0f182163 00000000`00000002 00000000`0000001f : 0xfffff8a0`16f4b010SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  atikmdag+bb080FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmdagIMAGE_NAME:  atikmdag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  522e350eSTACK_COMMAND:  .cxr 0xfffff88005b37a40 ; kbFAILURE_BUCKET_ID:  X64_0x7E_atikmdag+bb080BUCKET_ID:  X64_0x7E_atikmdag+bb080ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+bb080FAILURE_ID_HASH:  {d88270af-e85d-6fbc-8e60-cfe13ef6a7c7}Followup: MachineOwner---------1: kd> .exr 0xfffff88005b381e8ExceptionAddress: fffff8800f187080 (atikmdag+0x00000000000bb080)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 0000001b96ba44a0Attempt to read from address 0000001b96ba44a01: kd> .cxr 0xfffff88005b37a40;rrax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Last set context:rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=???????????????? 
Edited by ionbasa

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)
  • Author

Okay, so the first one I got did blame the AMD driver, although the driver crashed because of a memory access violation. Once we get one two two more dump we can narrow it down.

 

 

EDIT: Just saw the MEMORY.dmp file show up on drive, will take a look at it.

 

 

Okay, could it be the card? / cards? I've tried several different drivers.

 

That's amazing, I've tried so many times to get the de-bugger to come up like that, with no success...Your a godsend!

 

I'm still trying to get the PC to blue-screen my main concern is what if it continues to not write the minidump files??

 

Also, the large 800MB Dump file has been uploaded to Google Doc's

 

EDIT:: Just read your latest Edit.

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000007E, {ffffffffc0000005, fffff8800f187080, fffff88005b381e8, fffff88005b37a40}Probably caused by : atikmdag.sys ( atikmdag+bb080 )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8800f187080, The address that the exception occurred atArg3: fffff88005b381e8, Exception Record AddressArg4: fffff88005b37a40, Context Record AddressDebugging Details:------------------EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.FAULTING_IP: atikmdag+bb080fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h]EXCEPTION_RECORD:  fffff88005b381e8 -- (.exr 0xfffff88005b381e8)ExceptionAddress: fffff8800f187080 (atikmdag+0x00000000000bb080)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 0000001b96ba44a0Attempt to read from address 0000001b96ba44a0CONTEXT:  fffff88005b37a40 -- (.cxr 0xfffff88005b37a40;r)rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Last set context:rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  0000001b96ba44a0READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800039080e8GetUlongFromAddress: unable to read from fffff80003908198 0000001b96ba44a0 Nonpaged poolFOLLOWUP_IP: atikmdag+bb080fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h]BUGCHECK_STR:  0x7EANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8800f18282f to fffff8800f187080STACK_TEXT:  fffff880`05b38428 fffff880`0f18282f : fffff8a0`16f4b010 00000000`00000000 00000000`00000001 fffff880`0f182163 : atikmdag+0xbb080fffff880`05b38430 fffff8a0`16f4b010 : 00000000`00000000 00000000`00000001 fffff880`0f182163 00000000`00000002 : atikmdag+0xb682ffffff880`05b38438 00000000`00000000 : 00000000`00000001 fffff880`0f182163 00000000`00000002 00000000`0000001f : 0xfffff8a0`16f4b010SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  atikmdag+bb080FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmdagIMAGE_NAME:  atikmdag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  522e350eSTACK_COMMAND:  .cxr 0xfffff88005b37a40 ; kbFAILURE_BUCKET_ID:  X64_0x7E_atikmdag+bb080BUCKET_ID:  X64_0x7E_atikmdag+bb080ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+bb080FAILURE_ID_HASH:  {d88270af-e85d-6fbc-8e60-cfe13ef6a7c7}Followup: MachineOwner---------1: kd> .exr 0xfffff88005b381e8ExceptionAddress: fffff8800f187080 (atikmdag+0x00000000000bb080)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 0000001b96ba44a0Attempt to read from address 0000001b96ba44a01: kd> .cxr 0xfffff88005b37a40;rrax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=????????????????Last set context:rax=0000000000000001 rbx=0000000000040000 rcx=0000001b96ba4000rdx=fffffa8013515f80 rsi=0000001b96ba4000 rdi=0000000000040038rip=fffff8800f187080 rsp=fffff88005b38428 rbp=0000000000000000 r8=0000000000000002  r9=000000f420edf000 r10=0000000000000001r11=0000000000000003 r12=fffff8a016f4b010 r13=0000000000040070r14=fffffa800e823000 r15=0000000000000000iopl=0         nv up ei pl nz na pe nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202atikmdag+0xbb080:fffff880`0f187080 488b81a0040000  mov     rax,qword ptr [rcx+4A0h] ds:002b:0000001b`96ba44a0=???????????????? 
Edited by Chris_R.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)

Okay, could it be the card? / cards? I've tried several different drivers.

 

That's amazing, I've tried so many times to get the de-bugger to come up like that, with no success...Your a godsend!

 

I'm still trying to get the PC to blue-screen my main concern is what if it continues to not write the minidump files??

 

Also, the large 800MB Dump file has been uploaded to Google Doc's (Obviously) :)

 

EDIT:: Just read your latest Edit.

Okay. Took a look at the kernel dump file. And it's also pointing to Memory issues. Technically, the GPU driver is also at fault, but if the GPU is being assigned an memory space where the RAM is faulty, that would be expected.

 

 

So while I'm here, I need to ask a few questions:

Do you have XMP enabled or disabled for your RAM? I'm assuming you have 4 DIMMS of 4 Gigs each for a total of 16 Gigs?

I know this may sound redundant, but re-run a memory test using Memtest86+ from: http://www.memtest.org/

Guide: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

You're using Passmark's Memory test, which isn't recommended. Let it run and see if it picks up anything. If it fails, do you have an extra set of RAM handy to re-test? If that also fails, then you have yourself either an misbehaving BIOS mapping memory addresses, or an an bad Memory controller on your CPU. I hope its the former, because it's fairly easy to fix with a BIOS flash.

 

EDIT: Also, what Motherboard are you using. For some reason, DIMM_B2 is running interleaved, while the other 3 DIMMS are not. I need to go through the manual and see how the BIOS handles memory.

 

EDIT2: You've also got some drivers missing from Windows. Ideally, We'd want all drivers up to date when doing BSOD analysis as it reduces our margin of error.

EDIT3: You've also got some junkware installed on your system, AVG sucks  :P

16.2: kd:x86> .load wow64exts16.2: kd:x86> !analyze -vThe context is partially valid. Only x86 user-mode context is available.********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff8800f085370, Address of the instruction which caused the bugcheckArg3: fffff8800aa95510, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.FAULTING_IP: atikmdag+5370fffff880`0f085370 48              dec     eaxCONTEXT:  fffff8800aa95510 -- (.cxr 0xfffff8800aa95510;r)eax=00000002 ebx=fffffa80 ecx=fffffa80 edx=0ec1d060 esi=0ec1d060 edi=fffff880eip=00000002 esp=000000f4 ebp=00000000 iopl=0     vif nv up di pl nz na po nccs=0000  ss=0018  ds=5ef8  es=0000  fs=0000  gs=f8a0             efl=06ad000000000000`00000002 ??              ???Last set context:eax=00000002 ebx=fffffa80 ecx=fffffa80 edx=0ec1d060 esi=0ec1d060 edi=fffff880eip=00000002 esp=000000f4 ebp=00000000 iopl=0     vif nv up di pl nz na po nccs=0000  ss=0018  ds=5ef8  es=0000  fs=0000  gs=f8a0             efl=06ad000000000000`00000002 ??              ???Resetting default scopeDEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x3BCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000STACK_TEXT:  00000000 00000000 00000000 00000000 00000000 0x0STACK_COMMAND:  .bugcheck ; kbFOLLOWUP_IP: atikmdag+5370fffff880`0f085370 48              dec     eaxSYMBOL_NAME:  atikmdag+5370FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: Unknown_ModuleIMAGE_NAME:  Unknown_ImageDEBUG_FLR_IMAGE_TIMESTAMP:  0IMAGE_VERSION:  8.1.1.1500BUCKET_ID:  INVALID_KERNEL_CONTEXTFAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXTANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:invalid_kernel_contextFAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}Followup: MachineOwner---------16.2: kd:x86> .cxr 0xfffff8800aa95510;reax=00000002 ebx=fffffa80 ecx=fffffa80 edx=0ec1d060 esi=0ec1d060 edi=fffff880eip=00000002 esp=000000f4 ebp=00000000 iopl=0     vif nv up di pl nz na po nccs=0000  ss=0018  ds=5ef8  es=0000  fs=0000  gs=f8a0             efl=06ad000000000000`00000002 ??              ???Last set context:eax=00000002 ebx=fffffa80 ecx=fffffa80 edx=0ec1d060 esi=0ec1d060 edi=fffff880eip=00000002 esp=000000f4 ebp=00000000 iopl=0     vif nv up di pl nz na po nccs=0000  ss=0018  ds=5ef8  es=0000  fs=0000  gs=f8a0             efl=06ad000000000000`00000002 ??              ??? 
Edited by ionbasa

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)
  • Author

Hmm, weird I thought It was Memtest86...oh well I will run again for sure, may take another 8-9 hours to complete.

 

I have XMP disabled. Correct It is 4GB Dimms and there are 4 of them. Here is the exact set : http://www.newegg.com/Product/Product.aspx?Item=N82E16820233143

 

I do have an extra set, but only of 8 GB of your typical consumer RAM, not 16 gaming ram.........will that work or no go?

 

I have a gut feeling that it is the Memory Controller, but I guess it is possible that I could have RMA'd my old ram...and gotten a bad stick(s)

 

UPDATE: as I was typing this out the PC completely crashed out. No blue-screen, it just reset completely. (FYI)

 

Thinking about sending you a little $$$ through Paypal or something, you've been {and still are} being a tremendous help. As I stated already, I could not get my de-bugger to pull up everything like that ; and up until tonight everywhere I've posted no one seemed to care at all despite where I was posting! I've been working with this PC and the blue-screen issue since August 1'st.

 

 

EDIT : It's an ASUS Z97-A the latest revision {U.S.B 3.1}.  I know for somereason my U.S.B hub  has just decided to just not do anything lol. Also have a Bluetooth adapter plugged into it {For my normal system} I never installed that driver because I don't want to use it. I switch the hub back and forth depending on what pc i'm using, so that may be what's showing up as a whole bunch of input devices.

 

Pssh AVG's saved my ass so many times :)

 

 

 

 

BRAND NEW MINIDUMP JUST CAME IN

Edited by Chris_R.

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Brand new minidump just came in off that crash I mentioned. Would you like for me to just upload the lone minidump file to google doc's?

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Brand new minidump just came in off that crash I mentioned. Would you like for me to just upload the lone minidump file to google doc's?

Yup, that'd be fine. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Brand new minidump just came in off that crash I mentioned. Would you like for me to just upload the lone minidump file to google doc's?

Ran it though WinDBG, unfortunately, it seems like it lost the stack information, because the working memory was corrupted. 

 

As for re-running the memory test, go ahead and leave all the DIMMS populated. It should catch any errors within an hour. Once it does catch an error. Power off your computer and pull out all the DIMMS. Leave 1 in at a time until an offending DIMM is found. If by chance, they all fail the memory test, check it against your 8 Gb kit. If both kits fail, it's a bad onboard memory controller on the CPU and you'd have to get it RMA'd.

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 24, {c08a5, 0, 0, 0}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************NTFS_FILE_SYSTEM (24)    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd    parameters are the exception record and context record. Do a .cxr    on the 3rd parameter and then kb to obtain a more informative stack    trace.Arguments:Arg1: 00000000000c08a5Arg2: 0000000000000000Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x24PROCESS_NAME:  Origin.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000STACK_TEXT:  00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0STACK_COMMAND:  kbSYMBOL_NAME:  ANALYSIS_INCONCLUSIVEFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: Unknown_ModuleIMAGE_NAME:  Unknown_ImageDEBUG_FLR_IMAGE_TIMESTAMP:  0IMAGE_VERSION:  BUCKET_ID:  INVALID_KERNEL_CONTEXTFAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXTANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:invalid_kernel_contextFAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}Followup: MachineOwner--------- 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Ran it though WinDBG, unfortunately, it seems like it lost the stack information, probably because the working memory was corrupted. 

 

As for re-running the memory test, go ahead and leave all the DIMMS populated. It should catch any errors within an hour. Once it does catch an error. Power off your computer and pull out all the DIMMS. Leave 1 in at a time until an offending DIMM is found. If by chance, they all fail the memory test, check it against your 8 Gb kit. If both kits fail, it's a bad onboard memory controller on the CPU and you'd have to get it RMA'd.

Okay, I feel super stupid. I've tried the memtest86+ auto-installer, and manually copying the file over, but every time i boot to the usb drive it just returns to the bios......

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 24, {c08a5, 0, 0, 0}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************NTFS_FILE_SYSTEM (24)    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd    parameters are the exception record and context record. Do a .cxr    on the 3rd parameter and then kb to obtain a more informative stack    trace.Arguments:Arg1: 00000000000c08a5Arg2: 0000000000000000Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x24PROCESS_NAME:  Origin.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000STACK_TEXT:  00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0STACK_COMMAND:  kbSYMBOL_NAME:  ANALYSIS_INCONCLUSIVEFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: Unknown_ModuleIMAGE_NAME:  Unknown_ImageDEBUG_FLR_IMAGE_TIMESTAMP:  0IMAGE_VERSION:  BUCKET_ID:  INVALID_KERNEL_CONTEXTFAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXTANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:invalid_kernel_contextFAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}Followup: MachineOwner--------- 

Thanks!

 

Chris R.

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×