unusual crashing
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3737
Printed Date: 05 Feb 2025 at 6:01pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: unusual crashing
Posted By: sadkkf
Subject: unusual crashing
Date Posted: 06 Nov 2016 at 1:49am
|
" rel="nofollow - Hi-- Just installed a new X99 Extreme4 board with Windows 7 Pro and I'm getting some unusual crashes. I boot and may not touch the PC for a few minutes, then it blue screens and reboots. On reboot, it give me a Disk Read Error. I've changed *all* the drives in the PC with new ones. Right now, I'm booting to a Samsung 850 EVO SSD and have a couple of traditional WD HDD's, but those aren't bootable. The BIOS says I'm using the SSD as the bootable device and I'm using the newest BIOS. I ran MemTest86 and found no errors. Really not sure what else to look for. Any ideas? Please help! Thank you! |
Replies:
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 1:53am
|
I should also mention I had this problem *before* replacing the drives. At that time, I was booting to a traditional HDD. I'm pretty sure the drives are fine. My complete specs: X99 Extreme4 BIOS v3.40 Samsung 850 EVO SSD (boot drive) Windows 7 Pro G.SKILL TridentZ 288-pin SDRAM DDR4 3000 Model F4-3000C14Q-32GTZ (4x8GB) MSI Radeon R9 390 Gaming 8GB PCI Express 3 Intel i7-5820K NOTHING is OC'd. I appreciate any suggestions and advice. |
Posted By: wardog
Date Posted: 06 Nov 2016 at 1:06pm
|
" rel="nofollow - I don't see you state a new OS install after switching motherboards. ?? |
Posted By: Xaltar
Date Posted: 06 Nov 2016 at 2:10pm
|
" rel="nofollow - A fresh OS install, as Wardog mentioned, is always prudent on a new system but seeing as you have a new boot drive I am guessing you already did that? When you replaced the drives did you also replace SATA cables? Bad SATA cables can cause the issues you are having. ------------- 
|
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 9:20pm
|
" rel="nofollow - Thanks for the replies! Yes, I did a clean install of Windows with the new drive. Also swapped out the SATA cable on the boot drive. No change. Does it matter where it's connected? Right now it's plugged into SATA3_0. I also double-checked the BIOS and AHCI is enabled; the boot drive is set to SSD. Can anyone confirm the RAM I have actually is compatible with the board? Also, HDD S.M.A.R.T. is active. Is this okay? |
Posted By: wardog
Date Posted: 06 Nov 2016 at 9:33pm
" rel="nofollow -
X99 boards a very finicky concerning memory. Did they boot the first time you cleared the BIOS and tried booting at their JEDEC default? G.Skill doesn't list any mems above 2666 for this board. http://www.gskill.com/en/configurator?manu=52&chip=2276&model=2297 That's not to say they won't work, just that G.Skill themselves hasn't tested/qualified those sticks on it. Hitting 3000 on a stock X99 non-OC'd board is a steep steep hill to be asking of it and your processor and that's why I asked if they will initially boot from a cleared BIOS at JEDEC. Heck, hitting 3000 on an OC'd one would prove hard to do. Have the mem in the correct slots? Can you even get into the BIOS?
No problem that I know of. That's how I set all mine up when they leave here. |
sadkkf wrote:Posted By: sadkkf
Date Posted: 06 Nov 2016 at 9:43pm
" rel="nofollow -
I see other mems at 3000 for this board. The only difference I see is the G.SKILL chips are a little faster with lower latency. The PC worked fine for a while then started acting up. I can even go a month or more with no issues then it won't boot. I'm also certain the memory is slotted correctly. An IT friend of mine double-checked the build before I plugged anything in to be sure. I understand that's an important step, but also recognized it would very difficult to change with the CPU cooler installed. I'd need to remove the heat sink and fans to get to the RAM. Oh, and yes, I can get into BIOS. |
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 10:04pm
|
I could buy a couple of sticks of "approved" RAM to see if that helps with this, but only as a last resort. This is why I was hoping MemTest86 turned up some errors, but it didn't. I'm wide open to suggestions here. |
Posted By: wardog
Date Posted: 06 Nov 2016 at 10:04pm
|
" rel="nofollow - Those F4-3000C14Q-32GTZ sticks, they do not have any X99 XMP Profiles, only Z170 ones. That means you need to set them up manually on the X99. Doesn't mean they will or won't work, even at a lower initial boot. Only that setting XMP doesn't work on the X99. Too, you'll most likely have to adjust other voltages seeings they don't have proper X99 XMP settings. Odd. I just cut and pasted the link I posted and it's working fine here. Oh. It runs for a month or so huh? Hmmmmm .... I was going off this was a new build giving you fits. Is the board/processor OC'd while this happens? Specs please. Of your system and generalize the OC if any. |
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 10:23pm
My specs again: X99 Extreme4 BIOS v3.40 Samsung 850 EVO SSD (boot drive) Windows 7 Pro G.SKILL TridentZ 288-pin SDRAM DDR4 3000 Model F4-3000C14Q-32GTZ (4x8GB) MSI Radeon R9 390 Gaming 8GB PCI Express 3 Intel i7-5820K NOTHING is OC'd. I've *never* OC'd anything with this build. The disk read error is somewhat intermittent. Yesterday, for example, Windows gave some errors, blue screened, reboot and gave the error. I ran MemTest86 and found nothing. Reboot it manually, then Windows automatically ran ChkDsk and that found a lot of errors and booted fine right after. I was rendering a 3D scene for work, went to bed, and over night the PC crashed and rebooted again. Right now I'm seeing the disk read error again. The error is intermittent, but getting more frequent. I bought the parts for this late August last year and probably didn't see the first problem for a few months. Now, the PC is unusable. I've checked the power consumption and it's never gone over 300 watts with an 850W power supply. CPU and case temps are well below limits, too. All I can think of is RAM unless there's something not right about this board. |
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 10:44pm
|
" rel="nofollow - One other question...Looking at the memory support list: http://www.asrock.com/mb/Intel/X99%20Extreme4/index.asp?cat=Memory Is it a safe bet to try one of the 3000's from that list or should I try something slower to be sure? I think changing the RAM at this point is all I can do. Everything else has been changed. If the new RAM doesn't work, it must be the board, right? |
Posted By: parsec
Date Posted: 06 Nov 2016 at 11:11pm
According to G.SKILL, your memory model, the F4-3000C14Q-32GTZ, is shown as compatible only with Intel Skylake 100 series chipset boards, only Z170 chipset boards are listed. Click on the QVL tab on this page, and then the little grey triangle next to each mother board manufacture: http://www.gskill.com/en/product/f4-3000c14q-32gtz" rel="nofollow - http://www.gskill.com/en/product/f4-3000c14q-32gtz It's frustrating that with only two platforms (Intel X99 and Intel 100 series chipsets) currently supporting DDR4 memory that compatibility should be a problem. But some of the CPU voltage parameters related to the memory controller (part of the CPU) are different between these two systems. Those are the VCCSA and VCCIO voltages. Usually, Z170 compatible memory needs more VCCSA and VCCIO voltage than X99 compatible memory. You should have VCCSA and VCCIO voltage offset settings in the UEFI/BIOS. You could try using a positive 0.1V additional offset voltage to stabilize your memory. Why it passed memtest fine is curious. If your memory is not over clocked, it should be running at a speed of 2133. Is that what your memory speed is currently? Next, the main problem seems to be the corruption of your OS installation, given the disk read errors you continue to have. Another fix for a corrupted Windows installation is to run the sfc command. Start a Command Prompt (Admin) window, and type in sfc /scannow That will take a while to run, just let it go and it will tell you what the results are. It is possible it may find errors that it is unable to fix. You mentioned your 850W PSU, but did not specify the model. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: sadkkf
Date Posted: 06 Nov 2016 at 11:40pm
Correct. My memory is running at 2133. I will try to get back to Windows to run sfc, but right now, all I get is the disk read error. I don't know the model of the PSU and will need to open the case to see what it is. Would you think replacing the RAM with these: http://www.newegg.com/Product/Product.aspx?Item=N82E16820231798&cm_re=F4-2666C15Q-32GRR-_-20-231-798-_-Product Would help my situation? |
Posted By: sadkkf
Date Posted: 07 Nov 2016 at 12:33am
|
" rel="nofollow - Right now I can't even boot from the Windows DVD. No matter what option I try (Safe Mode, Last Known Good Configuration...) all of them want to reinstall Windows. If I choose the option to repair, it tells me the version of the Software Recovery Software is not compatible with the version of Windows installed. It is the same disc I used to install it originally. Does this mean the recovery doesn't recognize the installation after all the patches and service packs? |
Posted By: wardog
Date Posted: 07 Nov 2016 at 1:17am
|
" rel="nofollow - Disk read errors, to me anyways, tells me there's something fishy with the current OS install, the drive or that drives power and or data cables. A write error means something altogether different IMHO. That's I'd be looking at the processor or chipset. Have you scanned the drive with the manufacturers test utility? IIRC I've read that the Anniversary upgrade of 10 borked some previous OS utils. And thanks parsec for coming in and mentioning the two voltages of the X99 that need tweaked when using 100 chipset XMPs on an X99. BTW, the Cat has exited stage left. Time for the mouse to play. Look at that thread for updates coming soon. SuperPi at 5.1 but I had to stabilize the IMC a pinch to get there with 32GB. I now have my old Sammy Green sticks at hand. Hoping 5.2 and above after lessening the IMC load. |
Posted By: sadkkf
Date Posted: 07 Nov 2016 at 3:14am
I've always thought a DRE was from the OS, too. The thing is, I've had this problem with the original HDD installed. That was an older drive from my old system so when I got the error I thought the drive needed replacing. That's when I bought the new SSD. Now it's happening with the SSD. It could be the OS because I used the same disc to install both. I doubt the drive is at fault. This is also Win 7 Pro, not 10, so the anniversary update didn't affect me. To recap what I've done... Built the original config with an old HDD. Replaced the HDD with an SSD. Replaced the SATA cable. Updated the BIOS. The only things I haven't changed are the RAM and MOBO. I just ordered new RAM from the official compatibility list and will install that when it arrives in a few days. When it does arrive, I'm going to try to find a different install disc, hopefully one that includes some service packs so I don't have to update everything all over again. Hm...just noticed I did replace a video card during all of this, but don't recall if any of these other issues happened before then or not. Any thoughts on that? |
Posted By: wardog
Date Posted: 07 Nov 2016 at 1:04pm
|
" rel="nofollow - What make, model, and size is your PSU and how old is it? Applies to/depends on your above answer: PCIE_PWR1. Above the topmost PCIe slot directly in the corner created by the PCIe slot and the 4 mem banks is a female 4-pin molex that will provide power to the bus to stabilize it. BUT, remember, as PSU's age they inherently loose performance and fall out of spec. Out of spec ie: drooping rails, less overhead, generate more heat causing internal rise of resistance leading to overall poor performance, etc etc. Windows 7 ISO's https://www.microsoft.com/en-us/software-download/windows7 Windows USB/DVD Download Tool - To put an ISO to USB to install https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool |
Posted By: wardog
Date Posted: 07 Nov 2016 at 1:08pm
Those count towards you saying a graphics card was changed. That 390(x) req's a stout PSU rated at 750-800W. And we're not talking an inexpensive PSU either. Not for that GC and X99 board/proc. No no. No Sir. |
Posted By: sadkkf
Date Posted: 07 Nov 2016 at 8:19pm
|
" rel="nofollow - This is starting to make sense. My PSU is older, but a solid brand. I need to open it up to find the name and date on it. Still, I was monitoring the power usage and it *never* went over 300 watts. Could this mean it's just not giving enough power? Thanks again, everyone. I really appreciate your helping with this. |
Posted By: wardog
Date Posted: 07 Nov 2016 at 10:13pm
" rel="nofollow -
Well, depends. How may rails, as the older ones seemed to have 2-4 separate rails. T'was the "thing back yonder. If a PCIe rail, if there is in fact one on the PSU and not one large rail to tap from, if that rail is weak or isn't simply providing the output your GC needs/requires, then yes. Overall draw is one thing, but the kicker is is if it's a multi rail and this particular rail feeding the GC that just wasn't up to powering the new hungry 390 in the first place. Then you'll have issues. This particular issue yuu have now, well, can't say. Yet with this new system, X99 and 390, you want to consider an older PSU being sub-par and look at it from that vantage point. I am, that's why I asked of the PSU. |
Posted By: sadkkf
Date Posted: 07 Nov 2016 at 11:01pm
|
" rel="nofollow - So my PSU is a Thermaltake PurePower 680W, not 850 after all. I don't see a manufacturing date on it, but I know it's been around a while. If the output of these does drop over time, I'm wondering if I'm underpowered. The new video card actually uses less power than my previous one and the calculators I've used online say my consumption should be around 500W with all my drives and fans included. Any thoughts on this? I really don't want to buy another PSU if I don't have to. |
Posted By: sadkkf
Date Posted: 07 Nov 2016 at 11:06pm
Well, I have new RAM on the way to eliminate that possibility. I could probably borrow a larger/newer PSU to test this for a while. It's funny. I built this new system thinking I could get away with using existing parts, but I've been slowly replacing everything as issues arise. Lesson learned, I guess. |
Posted By: wardog
Date Posted: 07 Nov 2016 at 11:50pm
|
You're underpowered. Borrow one to test with if it's possible, but you are underpowered now nonetheless. PSU Requirements for graphic cards: http://www.realhardtechx.com/index_archivos/Page362.htm" rel="nofollow - http://www.realhardtechx.com/index_archivos/Page362.htm |
Posted By: sadkkf
Date Posted: 08 Nov 2016 at 12:16am
Yeah, I guess, but this new card actually uses less power than the old one. |
Posted By: wardog
Date Posted: 08 Nov 2016 at 3:46am
" rel="nofollow -
You are underpowered atm. That itself lead to many many possible errors. Yours included among them My old Sig used to read "Consider the PSU to be the foundation of your computer. Anything built upon it is only as sturdy as the PSU." I'm sorry if you said earlier. was the previous GC a Radeon too? |
Posted By: sadkkf
Date Posted: 10 Nov 2016 at 7:17am
I'm looking at new PSU's. A friend may have one I can borrow to test. The new RAM arrived, too, so hopefully this weekend I can rebuild. My original GC was an Nvidia. EVGA I think. Nice card, but not enough memory. |
Posted By: wardog
Date Posted: 10 Nov 2016 at 7:38am
" rel="nofollow -
Have you tried using DDU to uninstall any leftover bits of the nVidia card? I still stand on you're underpowered yet some of what you describe leaves me scratching my head if all leftover bits from the previews driver maybe causing some of this. Your current PSU might be strain(ed)(ing) to keep up but I'm just left with that nagging feeling it, the PSU, isn't all of what's happening there. http://www.wagnardmobile.com/ |
Posted By: sadkkf
Date Posted: 13 Nov 2016 at 2:43am
|
" rel="nofollow - Today I installed new RAM from the compatibility list and a new PSU...a Corsair 850W unit. Plugged everything in and booted to the DVD drive to reinstall windows and get an error... "Windows has encountered a problem communicating with a device connected to your computer...status: 0xc00000ec" The computer boots fine, I press a key to boot to the DVD drive and windows starts installing files. The progress bar is at maybe 10% when I hear the drive really spin up for a few seconds, then I get the error. I rechecked ALL the cables and everything is snug. I see all my drives in the BIOS and all the new RAM. WTF? |
Posted By: sadkkf
Date Posted: 14 Nov 2016 at 11:21pm
|
I was *finally* able to get this working by replacing my optical drive. So officially I have replaced absolutely everything in the is PC except the case. Again, thank you *everyone* for helping me troubleshoot this. |
Posted By: wardog
Date Posted: 14 Nov 2016 at 11:33pm
Huh? Say what? The optical drive?  It sux on days where it comes down to the LAST frigging thing before things start working as they should. I feel for ya. I do. The "bright' side(used loosely here I'll add) is you have a functional system now. Enjoy! |
Posted By: Xaltar
Date Posted: 14 Nov 2016 at 11:50pm
|
Thanks for letting us know what the problem turned out to be and as Wardog said, sorry it was literally the last thing left to try -------------
|
Posted By: sadkkf
Date Posted: 15 Nov 2016 at 7:15am
|
I'm still nervous with it. Just running it through some endurance tests now, but it's holding up. It rendered a 3D scene for several hours and the CPU never got over 47 degrees C. All the RAM is running at 2100 right now, but I'm going to try OC'ing that and the CPU if it continues performing. Again, thanks for all your help. And, yeah, who would have thought an optical drive could have done so much harm. |
Posted By: sadkkf
Date Posted: 20 Nov 2016 at 11:06pm
I spoke too soon. After a few days of work, it crashed again. I got another error about not being able to save something to memory. Next, I couldn't delete something, getting an I/O error. Now, when booting, it gives the old BootMGR is missing and Disc Read Error. I'm going to try a fresh install of Windows, but I'm not holding my breath. EDIT: I would like to try a fresh install, but the BIOS no longer sees the SSD as a boot options. It DOES see it when going to the boot menu, however. Seriously, is this all a problem of the motherboard? What else would it be? |
Posted By: parsec
Date Posted: 21 Nov 2016 at 1:39am
Sorry, but I have no idea what you meant by: I would like to try a fresh install, but the BIOS no longer sees the SSD as a boot options. It DOES see it when going to the boot menu, however. It sees the SSD, "... when going to the boot menu..."?  If you are installing Windows again, why do you need to have the target OS drive listed in the boot order? You boot from your installation media, not the target OS drive, right? When you install Windows again, if you do, ONLY have the OS drive connected (or powered up) to the board. Let's go back to your first post in this thread. What happened? The PC just stopped working suddenly. You got to the point where you began replacing parts, including the board, memory, and CPU. Now you have a more powerful power supply. That worked for you, until this latest problem. My theory was the initial problem was a catastrophic failure of some kind, that we now are 90% sure took out the board, CPU, memory, etc. That is normally caused by a power source problem. Examples are a power surge through the AC lines, lightning strike, or the PSU itself failing, but its own built in safety features did not activate, or were unable to prevent it from sending a damaging voltage to all the components in the PC. That is, all of them. Your 850 EVO was in the PC when it had the main disaster, right? While it only uses the +5V rail for power, it is not immune to damage from a power problem. Assuming all the damage you suffered was caused by a power supply related problem, personally I would not trust ANY of the components that were in the PC at that time. In that case I would assume all parts are guilty until proved innocent of being damaged. Sorry to say that is. I hope the EVO is not damaged, but I would not assume it was untouched by your disaster. Try installing Windows again, and select a Custom installation. That will display the 850 EVO, which is one test to see if it is functioning. It will have existing partitions on it, which you should delete before proceeding with the installation. That is also a test of the SSD, will it interact and function normally. When you finish the installation, and if it does not seem to work right, that is yet another clue the SSD was damaged. If you have another PC you can put the EVO in (or do this before installing Windows again), do that and run the Samsung SSD Magician software on that PC, and see how it reacts to it. Does it read its attributes fine, does the SMART data appear normal, can you run a Samsung benchmark test on it with normal results? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: sadkkf
Date Posted: 21 Nov 2016 at 2:13am
|
The first failure happened a few months after building the new system. It was a Disk Read error. I replaced the HDD with the EVO SSD and continued having problems. Since then, I've replaced the RAM, PSU and video card. Still crashing. I have disconnected all other drives. When I enter the BIOS with F2, the SSD is not showing. When I press F11, the SSD is shown. I was *just* able to boot to a USB DVD drive and install Windows from that. So far so good. I'm trying to install all the updates before installing anything else. If the pattern follows, this PC will work for a few days then crash. |
Posted By: sadkkf
Date Posted: 21 Nov 2016 at 5:23am
|
Windows installed successfully and is now checking for updates. I will probably let that go overnight. I have unplugged all other drives so Windows found this right away. There were no partitions, but I reformatted it before installing. Also, running Samsung SSD Magician, it tells me the drive is OK. Authenticated and has the newest firmware. SMART data looks fine. |
Posted By: sadkkf
Date Posted: 21 Nov 2016 at 8:43pm
|
" rel="nofollow - So Windows is installed and overnight I let it download updates. During that time it again rebooted and went to BIOS. I am *still* not seeing the SSD is the boot section (F2) but I do see it and can boot to it when I press F11. Again, running all the tools in Samsung Magician tell me the drive is healthy and operating fine. Any ideas Xalter or Parsec? I'm ready to return this board. |
Posted By: sadkkf
Date Posted: 02 Dec 2016 at 4:51am
|
" rel="nofollow - Hey, everyone-- Just thought I'd wrap this up for anyone who's interested. After totally giving up on this, I contacted tech support to see about an RMA. We exchanged several emails (one of which seemed vaguely offensive) and I eventually discovered having my bootable drive plugged into SATA3_0 was the problem. Apparently, single drives need to be plugged into S_SATA3 ports. SATA3 ports are reserved for RAID drives. Can anyone please tell me where in the f*ing manual it explains this? All I've seen is the SATA3 ports are RAID compatible, not for RAID use only. I've looked on other forums (one of which actually said it didn't matter where single drives were connected) and no one has ever said this. Sorry, but I'm really angry about this. I've spent nearly a year battling this as well as hundreds of dollars replacing parts that didn't need replacing all because the manual is so poorly written. And to add further insult, the new PSU I purchased came with a rebate that was denied because the rebate company claims I never submitted the UPC, which I did. I think if this computer fails again, I'm melting it down and starting over. But, again, I do thank everyone for offering their suggestions. |