Random BSOD problems in the past 2 days. Random errors at random times

[JacobT]

Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty of air flow. I installed a Cool Mater Hyper Plus 212 heatsink. I followed the instructions, and looked at a few installation videos on my phone just to be sure. I'm pretty positive everything was done correctly including the thermal paste as my system has not gone over 45C while gaming even playing games on Ultra settings.

I got one BSOD late last night, after about 6 hours of it being on but no other problems after that. Today however I have been having BSOD issues the entire time at random times from just 5 minutes up to 2 and a half hours between BSODs. They have ranged from: NTSF_FILE_SYSTEM, PAGE_FAULT_IN_NONPAGED_AREA, KMODE_EXCEPTION_NOT_HANDLED, and SYSTEM_SERVICE_EXCEPTION

I have researched the errors on google all day and tried fixes for each one such as running memory diagnostic tool, deleting the old page info from memory and creating a new one, deleted all of my video drivers and reinstalled them, and I've even opened my case to make sure all my memory and cards are plugged in all the way.

These are the errors that BlueScreenView gave me:

120313-25490-01.dmp 12/3/2013 11:01:36 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff87f`f903edfb 00000000`00000008 fffff87f`f903edfb 00000000`00000005 fltmgr.sys fltmgr.sys+4aae x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\120313-25490-01.dmp 4 15 7601 276,256 12/3/2013 11:03:15 AM

120313-14601-01.dmp 12/3/2013 3:20:13 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`13dc50b0 fffff880`0a3f4800 00000000`00000000 dxgmms1.sys dxgmms1.sys+100b0 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\120313-14601-01.dmp 4 15 7601 276,256 12/3/2013 3:21:31 PM

120313-22557-01.dmp 12/3/2013 4:04:04 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b90 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75b90 C:\Windows\Minidump\120313-22557-01.dmp 4 15 7601 276,256 12/3/2013 4:05:37 PM

120313-24679-01.dmp 12/3/2013 9:36:13 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff7ff`fb110030 00000000`00000000 fffff800`031d2ef1 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\120313-24679-01.dmp 4 15 7601 276,200 12/3/2013 9:37:49 PM

120313-22760-01.dmp 12/3/2013 9:41:25 PM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0319f758 fffff880`0319efb0 fffff800`02e6df96 Ntfs.sys Ntfs.sys+4688 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\120313-22760-01.dmp 4 15 7601 276,200 12/3/2013 9:42:54 PM



I have also created a compressed file using the SF tool this forum suggested and will be attaching it to this post. Any help would be appreciated as i am now completely stumped on how to fix the problem.

 

[koolkat77]

Welcome to the Forum.

Please remove the software:

Start Menu\Programs\Advanced SystemCare 7	Public:Start Menu\Programs\Advanced SystemCare 7	Public

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence. If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything. 10 Tips on How to Properly Maintain Your Computer

Start Menu\Programs\McAfee	Public:Start Menu\Programs\McAfee	Public
Start Menu\Programs\McAfee Online Backup	Public:Start Menu\Programs\McAfee Online Backup	Public

McAfee is a known cause to BSOD's. Please remove it and use Microsoft Security Essentials it is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - Free
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software:
CrystalDiskInfo - Software - Crystal Dew World
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#post2610227

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Check for heating issues using Speccy or HWmonitor:
HWMonitor
Speccy

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff87ff903edfb, 8, fffff87ff903edfb, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43801 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff87ff903edfb, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff87ff903edfb, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100
GetUlongFromAddress: unable to read from fffff800030fd1c0
 fffff87ff903edfb Nonpaged pool

FAULTING_IP: 
+0
fffff87f`f903edfb ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  LiveUpdate.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006047400 -- (.trap 0xfffff88006047400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800b719990 rbx=0000000000000000 rcx=fffffa800ce83481
rdx=fffffa800b719991 rsi=0000000000000000 rdi=0000000000000000
rip=fffff87ff903edfb rsp=fffff88006047590 rbp=fffff880060475e0
 r8=fffffa800b719990  r9=ffffffffffffffff r10=fffff880010596c0
r11=fffffa800ce83480 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng zr na po nc
fffff87f`f903edfb ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f425b3 to fffff80002ec5bc0

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff87f`f903edfb ??              ???

STACK_TEXT:  
fffff880`06047298 fffff800`02f425b3 : 00000000`00000050 fffff87f`f903edfb 00000000`00000008 fffff880`06047400 : nt!KeBugCheckEx
fffff880`060472a0 fffff800`02ec3cee : 00000000`00000008 fffff87f`f903edfb fffffa80`08475500 fffffa80`078361a0 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`06047400 fffff87f`f903edfb : fffffa80`078361a0 fffffa80`08475700 fffffa80`0829abb0 fffffa80`0829add0 : nt!KiPageFault+0x16e
fffff880`06047590 fffffa80`078361a0 : fffffa80`08475700 fffffa80`0829abb0 fffffa80`0829add0 fffffa80`0c3e4cb8 : 0xfffff87f`f903edfb
fffff880`06047598 fffffa80`08475700 : fffffa80`0829abb0 fffffa80`0829add0 fffffa80`0c3e4cb8 fffffa80`0c3e48d0 : 0xfffffa80`078361a0
fffff880`060475a0 fffffa80`0829abb0 : fffffa80`0829add0 fffffa80`0c3e4cb8 fffffa80`0c3e48d0 fffffa80`0c4f6e80 : 0xfffffa80`08475700
fffff880`060475a8 fffffa80`0829add0 : fffffa80`0c3e4cb8 fffffa80`0c3e48d0 fffffa80`0c4f6e80 fffffa80`0797c8f0 : 0xfffffa80`0829abb0
fffff880`060475b0 fffffa80`0c3e4cb8 : fffffa80`0c3e48d0 fffffa80`0c4f6e80 fffffa80`0797c8f0 fffffa80`09136010 : 0xfffffa80`0829add0
fffff880`060475b8 fffffa80`0c3e48d0 : fffffa80`0c4f6e80 fffffa80`0797c8f0 fffffa80`09136010 00000000`00000000 : 0xfffffa80`0c3e4cb8
fffff880`060475c0 fffffa80`0c4f6e80 : fffffa80`0797c8f0 fffffa80`09136010 00000000`00000000 fffff880`06040001 : 0xfffffa80`0c3e48d0
fffff880`060475c8 fffffa80`0797c8f0 : fffffa80`09136010 00000000`00000000 fffff880`06040001 fffff880`010409aa : 0xfffffa80`0c4f6e80
fffff880`060475d0 fffffa80`09136010 : 00000000`00000000 fffff880`06040001 fffff880`010409aa 00000000`00000000 : 0xfffffa80`0797c8f0
fffff880`060475d8 00000000`00000000 : fffff880`06040001 fffff880`010409aa 00000000`00000000 fffffa80`0c3e4cb8 : 0xfffffa80`09136010


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+43801
fffff800`02f425b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+43801

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+43801

BUCKET_ID:  X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+43801

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

If this does not provide stability. Test RAM.

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.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[JacobT]

Thanks for the reply. I have used Revo to uninstall both advanced system care and mcafee. I ran disk check on my hard drive from the CMD and it reported back no errors. I do not have a blank CD or USB with me right now to use the ISO for memtest86, but I did the windows memory diagnostic (7 passes) and it reported no issues found. I know There are sometimes conflicting reports between WMD and memtest so i will have to try that some point soon. There is a problem with testing the RAM sticks one by one. With the new heatsink I installed, and the way my motherboard is laid out the heat sink is over top of 2 of the RAM sticks. Not touching them, but only about an inch and a half or so of space. The only way to get to them is to uninstall the heat sink which I would need to remove the motherboard from the case to do.

If i take out the mother board, remove the heatsink, and place the motherboard back in the case with no cooling system on top of it would it stay cool enough to test the RAM one by one without causing damage? Also, would you recommend that I reformat and install a fresh copy of windows 7 in case the advance system care did damage or remove files?

 

[essenbe]

Never, under any circumstances, even turn your computer on without a fan and heatsink attached. With an 1 or 1.5" space, you may be able to get the stick out. You can also run tour board outside the case if it needs it. I have one running on a cardboard ( no conductive) box right now. Run the test with both sticks in and see if you get errors. Run it for 8 passes or overnight, which most people do because it will take it several hours to run 8 passes. Also, there are 2 similar tests. memtest86 and memtest86+. Be sure to use the 86+ version. It is much better.

 

[JacobT]

My computer became more stable after deleting those programs, but I am unable to run Memtest86+ for some reason. I got a blank rewrite able CD, downloaded the ISO, extracted it, and then burned it to the CD. It did not boot from CD so i restarted, entered BIOS, and made sure my cd drive was first priorty. Still would not boot memtest. I found an old USB drive and formatted it and installed the memtest USB install on it, went back into BIOS and made USB first boot priority and It still did not boot. It simply just jumps straight to starting windows.

I'm attaching another SF file of the errors over the past 2 days of looking at everything.

 

[essenbe]

Go to Memtest86+ - Advanced Memory Diagnostic Tool and look at the 2nd group down, memtest86+ V 4.20, go to the 5th one down and download the auto installer for USB key. download that. Insert your usb key and note the drive letter. Run the downloaded file by selecting the usb key drive letter and checking the format usb box. It will install it onto the usb drive. Boot from the drive and run it for 8 passes. It will take several hours, so run it overnight or until you get an error. to stop just press ecape on the keyboard and you will reboot into windows.

 

[JacobT]

I did that. That's what i said in the last post. Neither the CD with the ISO or my formatted USB with memtest are booting.

 

[essenbe]

I'm not sure what to tell you. I've never had a computer that won't boot from it if done right. With the pre configured USB installer it will install it to the USB drive. With the ISO file, just double click it and try windows disk image burner. Maybe there is something in this tutorial(http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html) that will help. But, for the CD, the iso has to be burned to the CD not copied. Windows disk image burner will do that or many of the disk image burners.

 

[JacobT]

I was finally able to get memtest86+ to run using a different USB. Not sure what was wrong with the other one. I let it run for 12 hours straight and it listed no errors with all 4 sticks of RAM still installed. I also checked my BIOS version and compared it the manufacturer. The last BIOS update for my motherboard was a 2010 version and my version of BIOS is labeled as the 2010 version so that is not the problem either. Since it's not RAM, my hard drive, video card drivers, or my BIOS I'm not sure what's causing the BSODs. I have just reformatted with a fresh install of Windows 7 and hoping that it will run fine now. We'll see what happens.

 

[JacobT]

Reformatting did not work to fix the issue. 3 BSOD crashes already. Attaching the newest crashes to this post.

 

[Arc]

Hi JacobT.

One of your latest crash dumps are indicating to Realtek ethernet driver. Update it from Realtek. Get the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/11/26.

But there are three different BSODs very frequently. And The other two are not pointing to anything else precisely. So let us go methodically. First let us search for any failing drivers. Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________________________

BugCheck A, {fffff6f440017e78, 2, 1, fffff80002ef5fe9}

Probably caused by : memory_corruption ( nt!MiUnmapPageInHyperSpaceWorker+49 )

Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck 50, {fffff95ff8155b50, 8, fffff95ff8155b50, 5}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!XDCOBJ::bCleanDC+2b0 )

Followup: MachineOwner
----------------------------------------------------------------------------------------
BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys

Probably caused by : Rt64win7.sys ( Rt64win7+1da01 )

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

 

[JacobT]

I downloaded the installer for the realtek driver and installed it. I also turned on driver verifer and rebooted so it would take effect. My PC ran a little bit more sluggish than usual with loading pages and such so i figured it was working. I did not have a BSOD while driver verifer was running, but I did have some sort of crash.

The first happened about an hour and a half in just surfing the web (facebook, youtube ect). What happened was my computer screen froze, but audio would continue for about 2-3 seconds after the freeze. Then audio would also cease and my screen turned into a lot of weird horizonal lines and fragments using the colors that were on screen at the time (first time on facebook so the color of the lines were blue and white). I rebooted and decided to leave driver verifier running again to see if i could repeat the issue or force another BSOD. This time I decided to put more stress on the system by running a game. The same issue happened. After awhile the screen froze, a few seconds later audio stopped, and then the same weird fragmented horizonal lines on the screen using the colors that were on screen as it froze. I'm going to attach a picture of something similar I found in a google search. It displays the same issue I had, but vertical lines instead of horizontal. I have checked my windump file using bluescreenview to verify that no blue screen logs were recorded. I'm guessing that this issue is related to my graphics card since it's the display freezing and bugging out?

 

[Arc]

At that point we may consider that the issue may not be a driver caused one. If so, there will be precise BSODs.

The screen definitely gives an idea of a hardware issue.

How many passes you have performed memtest? Try to complete 8 passes at least. That is time consuming, but worthy to decide.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
http://www.extreme.outervision.com/psucalculatorlite.jsp
Also let us know the actual wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know.

 

[JacobT]

I have already ran memtest86+ for 12 straight hours once with no errors. I'll try everything else though.

 

[Arc]

I have already ran memtest86+ for 12 straight hours once with no errors. I'll try everything else though.

Jacob, please concentrate on passes count, not on hours. I guess 12 hours is not enough to complete 8 passes on 8 GB.

It may find no error at end, but it is really worthy to decide that the RAM is good or not; and a failing RAM can cause any error there, including that odd look of the screen.

 

[JacobT]

I'll find time to run it again i guess, but it was over 8 passes in 12 hours. It was in the middle of test #10 I believe when I stopped it. I left it running for 4 hours and then went to sleep. The power recommended by that website for my PSU is 750watt. It's been 3 years since I had this computer built, but If i remember correctly it was a 800 watt supply. I'll double check it in a little while. Going to run video test now. Also heat has not been a problem. CPU stays around 36C while surfing the internet, and has not gone higher than 46C while gaming. I have also run Prime95 on my CPU for 100% load and it only went up to 50C when my AMD quad core is not rated to be in danger until 62C. My GPU has not gone over 52C. (I've been watching closely after installing the new heatsink).

 

[JacobT]

Okay I opened up the side of my computer to check the power supply. It is indeed a 800W PSU. While i was in there I also removed my video card, sprayed the slots with some compressed air, and then reseated my grahpics card. I'm hoping that if my GPU had a problem it was an issue with coming loose or dust build up (I also gave the card itself a once over with the compressed air). I also ran FurMark on it's 15 minute full screen burn in test. No errors, crashes, or artifacts on screen. It also did not have any heating problems. It went up to 73C about 3 minutes in and then plateaued for the entire rest of the test only going up to 75C at finish which was still in the yellow. I'm going to do things like normal for awhile. If I BSOD I will upload it to this forum and do another run through with Memtest86+

 

[JacobT]

Looks like no luck on the BSOD. 3 more crashes, two of which were very fast back to back. Attaching the dump files. I guess I'm going back to another day of memtest to see if it shows errors this time.

 

[Arc]

I also ran FurMark on it's 15 minute full screen burn in test. No errors, crashes, or artifacts on screen. It also did not have any heating problems. It went up to 73C about 3 minutes in and then plateaued for the entire rest of the test only going up to 75C at finish which was still in the yellow.

The latest crash dumps you uploaded contradicts with this observation.

BugCheck 3B, {c000001d, fffff80002e557b0, fffff88008507480, 0}

Probably caused by : hardware ( nt!MmGetImageBase+80 )

Followup: MachineOwner
------------------------------------------------------------------------------
BugCheck 3B, {c000001d, fffff880131d6b77, fffff8800954b770, 0}

Probably caused by : atikmdag.sys ( atikmdag+157b77 )

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

So the crash dumps are insisting us to believe it that it is a display error caused by display hardware.

A summery of what we have done so far:

• Driver Verifier did not catch anything.
• Memtest is fine.
• Furmark is fine.
• Prime95 is fine.
• Power supply is enough.
• Not overheating.

But the hardware issue is there. If Furmark really passed without any artifacts, I would say that the hardware identified by the memory dump is the GPU slot, which is a motherboard's element.

If you have any other slot for the GPU, try it there.

 

[JacobT]

I moved my video card over to the second slot. I also deleted my old drivers in case of corruption and reinstalled it. We'll see what happens. Are you fairly sure we have it hammered down to a video card/slot issue? Been messing with this thing for like a week. I'd just like to really know what the cause is at this point lol