|
Fatal1ty K6+ BSOD - Need some fresh ideas |
Post Reply 
|
Page 123 4> |
| Author | |
heapson 
Newbie 
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Fatal1ty K6+ BSOD - Need some fresh ideasPosted: 17 Jan 2018 at 4:02pm |
|
It's been well over a year without a BSOD and I never wrapped this thread up.
The problem was not bent pins although I did bend pins storing this motherboard and switching to a Gigabyte board. The issue persisted on the Gigabyte board but disappeared after I replaced the GPU. The conclusion was the combination of an intermittent faulty AMD graphics card and faulty Intel drivers for when the GPU was removed. This gave the false illusion that the AMD GPU was not to blame as the problem persisted with it removed. Just wanted to say this had nothing to do with the AsRock board. |
|
 |
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 May 2016 at 7:29am |
|
The annoying conclusion to a miserable chapter of my life.
I switched back to the ASRock K6 board. I was going to run it with the old power supply outside the case but the cooler radiator is a pain to remove so I went for a complete swap. Final task was the CPU. I checked again for bent pins after seeing some photos while researching this issue. I found one. It required a magnifying glass and checking each and every pin. My previous check - as suggested way back by Xaltar - was with cursory disbelief and just my eyes. Not surprising I didn't see it. The pin was on an edge near the corner folded back on itself and hidden beneath the corner pin so it looked more like an empty pin than a bent one. I straightened it as best I could and it looked normal but still noticeably not quite right. The computer didn't post. Cycled through 00, 19, 4C error codes in a non-stop loop. I tried straightening it again but no joy. I swapped back to the Gigabyte board, which is all good, perfect pins and it booted fine. It also ran Prime95 all night without any issue. I have no clue how or when the pin was bent. It may have been from day one or during storage preparation after installing the new motherboard. I'm pretty careful and don't remember any problems. I did tighten the cooler with a screwdriver on the very first install but only finger tight since reseating the CPU. I have no idea how it ever worked or if it was definitely the reason but it's damaged now so I'll never know for sure. I'm closing this thread with the likely cause a bent pin on the socket. The Gigabyte board is another story but I'm starting to think it's just a simple driver issue. It worked fine for days with the original installation, which had newer drivers. The blue screens have been far less common and always on fresh installs with the stock Gigabyte drivers and the Killer Network software. I've always assumed it was the same issue as the ASRock board and haven't done much in the way of basic trouble shooting. I'm going to start afresh and move forward as if I have a new computer. If the blue screens persist, I'll start a new thread on the Gigabyte forum. Thanks again for all you help. Apologies Xaltar for not following one of your very first suggestions as well as I should have. Cheers. Mick. Edited by heapson - 31 May 2016 at 9:04am |
|
|
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 30 May 2016 at 9:54am |
|
Computer is on full time apart from reboots after changing something. Long 24+ hour periods between blue screens makes things hard to analyse. I'm reluctant to change anything as the current barebone configuration did blue screen. New components since adventure began:
Changed component:
Thur, 06:10 - Installed Development drive & worked all day with WiFi. Nothing connected. No blue screens. At this stage, only the speakers and network cable were connected to an otherwise bare bone motherboard and it blue screened within an hour. Prior to this, it ran stable for several days. Can fully operational but fairly old speakers potentially cause blue screens on two different motherboards with two different sound cards from different manufacturers??? Fri, 15:58 - Disconnected network cable At this point, it's blue screened with both speakers and network cable connected but not with only one. The next few days I try to isolate it to one or the other but get no blue screens for several days. Computers never blue screen when you want them to... **** behaved overnight. Sat, 06:42 - Disconnected speakers **** behaved overnight. Sun, 07:00 - Connected speakers **** Let's try again from scratch with nothing installed. Sun, 20:23 - Reinstalled Windows and installed drivers with speakers and network cable disconnected **** behaved overnight. Mon, 07:16 - Connected speakers What can I try next? I'm thinking of swapping back to the AsRock board as it was certainly less stable than this one, which might help to isolate the issue. Edited by heapson - 31 May 2016 at 9:29am |
|
|
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 May 2016 at 3:37pm |
The file copy seemed to trigger the blue screen so it was just what i was doing most often. All drives were affected. I did have one drive report bad sectors and I immediately ordered a new one. I copied all data from it during those four good days with the new motherboard. I then did a long format and ran another chkdsk /r. It came back good. Zero bad sectors. It also passed a long generic. It's still under warranty but appears to be OK. Default Microsoft drivers on the AsRock board and ASMedia drivers from Gigabyte on the new board. I do have the Intel IRST driver package installed. Thanks for your help and suggestions parsec. I think this may be a simple hardware issue and I've failed to isolate it because I've been so random in my approaches to resolve it. I'll soldier on and document everything from here. Edited by heapson - 27 May 2016 at 3:38pm |
|
|
|
|
Xaltar
Moderator Group 
Joined: 16 May 2015 Location: Europe Status: Offline Points: 25953 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 May 2016 at 3:32pm |
|
Damn, that is the absolute worst kind of problem. I remember building a server for a client once that gave me similar issues. I replaced literally every component and the issues persisted. It would be working fine in my workshop but within hours of deployment it would start messing about. In the end I built the client an entirely new server only to have the same issue spring up yet again. Eventually it turned out that their battery backup was defective.......
Moral of the story is check everything, sometimes the silliest thing could be tripping you up. Given the system seems OK with a minimal config and the PSU is brand new I would test your AC power and make sure it isn't fluctuating or running over or under spec. Good luck and thanks for keeping us posted.
|
|
|
|
|
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 May 2016 at 3:13pm |
|
Lots of great ideas there parsec. I'll try them if I ever get back to the AsRock K6 board. I no longer think it had anything to do with Sata drives. That was probably coincidence.
I'm still no closer to resolving this. I had a complete week without computers while I waited for my new power supply, which was nice. The new PSU didn't help. Replaced all cables. Blue screened in an identical manner to before midway through installing drivers. Blue screened again while installing software. Disconnected absolutely everything. New motherboard, new PSU, new RAM, different video card, single USB Flash drive for Windows and another for drivers. The only things the same, are the M2 Sata SSD drive, the CPU, case and cooler. Windows installed fine, drivers installed fine, updates installed fine, visual studio and office installed fine. Connected my development drive and actually did some urgent work. It's been up now for 26 hours without any issues. I'm going to install components one by one with 24 hours between each change and document as I go. Edited by heapson - 27 May 2016 at 3:16pm |
|
|
|
|
parsec
Moderator Group
Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
Quote Reply
Posted: 19 May 2016 at 2:34pm |
|
A few thoughts related to your comments about the SATA drives and SATA chipsets.
Check your PCH +1.0V setting in the UEFI, and the resulting voltage reading in the H/W Monitor screen. The PCH is the Intel Z170 chipset, containing the Intel SATA controller. Increase this voltage as an experiment. The Intel SATA chipset's power saving features for drives are not configurable unless you install the Intel IRST driver package. Yes, I know it's for RAID, but also has a superior AHCI driver. If your UEFI/BIOS has a SATA Link State Power Management option, disable it and keep it that way. If your UEFI has any of the PCH ASPM options enabled, try disabling them. Your M.2 850 EVO is a SATA drive. It just uses an M.2 interface. Your 3TB HDDs, formatted as GPT? Does the file copy failures happen with all the HDDs, or is it only one that is a hidden offender? ASMedia SATA chipset...  Mine are disabled. What driver do you use with the ASMedia SATA controllers?For an educational experience, connect a SSD to the ASMedia SATA chipset, and then run the Windows 8 - 10 optimize feature (manual TRIM) on that SSD.  |
|
|
|
|
|
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Offline Points: 25953 |
Post Options
Thanks(0)
Quote Reply
Posted: 19 May 2016 at 12:41pm |
|
I am sorry to hear that. Lets hope the PSU is indeed the issue and it resolves your problems. Good luck.
|
|
|
|
|
|
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 19 May 2016 at 9:57am |
|
The saga continues!
Good news for AsRock I think. After reinstalling Windows with the new motherboard from a different manufacturer, I had three blue screens before I'd even finished installing drivers. I cried a little at this point. I started again with a fresh install to see if it was a repeatable driver installation issue and this time got all the Windows updates completed and all the latest drivers installed. While installing Visual Studio, it blue screened yet again. They appear to be fairly random bug checks once again but all occur in ntoskrnl.exe+142780 the same as the AsRock board with the latest an IRQL_NOT_LESS_OR_EQUAL. I'm using the new 32GB of G.Skills RAM and a fresh Windows 10 installation but that's the only change from the previous few days of stability. On a brighter note, all software has activated without any issue. I've reordered the PSU I cancelled so I'll report back in a week or two. My current line of thinking is the new more expensive motherboard is hiding the PSU instability better than the AsRock board. To be fair to AsRock, if this system is ever stable, I'll reinstall using their motherboard before I do the RMA. Edited by heapson - 19 May 2016 at 9:58am |
|
|
|
|
heapson
Newbie
Joined: 03 May 2016 Location: Townsville Status: Offline Points: 22 |
Post Options
Thanks(0)
Quote Reply
Posted: 17 May 2016 at 6:43pm |
|
I did choose a different brand and model of motherboard. I haven't reinstalled Windows yet but Microsoft Office Professional 2016, Adobe Master Collection, Adobe RoboHelp and Norton Internet Security have all deactivated. I'll let you know how everything behaves after the reinstall. Hopefully, they reactivate without any dramas.
I forgot to deactivate the Master Collection manually, which was stupid so hopefully it did that itself and will let me reactivate on the new install. You can deactivate Norton remotely from their website so it's no drama. RoboHelp is an expensive wild card and I'm not sure what Office will do. Other software like Visual Studio, Sony Vegas and Lightroom are currently behaving. I have no idea how their activation algorithms work. Swapping with the exact same motherboard may solve the problem but I think a motherboard has a unique ID, the same as the CPU so I doubt it would help. I really have no clue how all this works. |
|
|
|
|
Post Reply
|
Page 123 4> |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
parsec wrote: