Msi z87 bsod's

i recently just updated my bios to 1.8, everything was going great once i updated it, i thought updating my bios actually solved the problem. and about a day later out in the middle of no where i get a bsod. this really ticked me off because i thought this would be solved by now. here is the random bsod, i really need some help on this. oh and after i installed the bios version 1.8 my windows load screen loaded really fast but i seems like each time i shutdown and reboot it gets slower and it is more prone to bsod's
main bsod out of nowhere (bios version 1.8):
(happens when i try to play a youtube video in google chrome)
i have several other bsods with my bios version 1.7 (please help me with the top one first, check these if you have time):
please try to get back to me as soon as possible

Board: MSI Z87 G45 Pro
Bios: Version 1.8
VGA: GTX 660
PSU: EVGA 750w
Intel Core i7-4770k 4.3ghz
MEM: corsair 2x4gb 1333mhz
HDD: ocz vertex 2
COOLER: Corsair Hydro Series™ H80i High Performance Liquid CPU Cooler
OC: 4.3 ghz on 4770k
OS: Windows 7 64bit Professional
got a bsod today trying to watch a youtube video

Similar Messages

MSI Z87 G45 GAMING erratic BSOD/freeze @ 2300, stable @1600. Can't solve.

Hi All,
I would welcome some advice. I am about 4 months into a new machine build:
* MSI Z87 G45 GAMING motherboard
* i7-4770K Haswell 3.5 GHz & aftermarket heatpipe cooler
* 4 x 4Gb G.Skill SNIPER DDR3-2133 PC3-1700 (F3-17000CL11D-8GBSR)
* GeForce GTX 650 Ti w/ 2 Gb Video RAM
* Samsung 840 Pro 256 Gb SSD
* Thermaltake 700W Toughpower
* Win 7 Pro 64-bit SP1
The system seems to run fine at the default 1600 MHz RAM speed, however if I implement either of the X.M.P. profiles (which kick the memory speed up to the RAM's advertised speed of 2133 MHz), the system will occasionally (every 8 to 48 hours) freeze or BSOD. The BSOD stop codes are inconsistent in number (0x00, 0x41, 0x1E, 0xC4) and driver. When the system freezes, there is no consistent behavior. I am not doing any other overclocking besides using the X.M.P. profile in the memory.
RAM timing on the 2133 X.M.P. profile is: 11-11-11-30.
I have updated the BIOS to 1.5, including the ME, and updated all drivers in the system. All irrelevant hardware and drivers are disabled. Also I have done the following:
* MemTest+ 5.01 for over 30 hours, all 4 sticks in. No errors.
* Intel BurnTest on 'Very High', 10 passes, no errors
* Prime95 for over day with 90 C CPU temps constantly being hit. No errors.
* Unigine Valley Benchmark for 30 minutes; no issues
I increased V_DRAM from 1.60V (from the XMP profile) to 1.65V, and I also added +0.10V offset to increase the CPU I/O ANALOG , CPU I/O DIGITAL and SYSTEM AGENT voltages. Didn't seem to help. All other CPU voltages are default from [auto].
I rolled the memory speed back to the default 1600 MHz, and the system seems stable as a rock.
I don't really need to have the memory run at 2133 MHz, but it irks me that the system is not stable with the rated components, and I'm befuddled why the stress tests seem to pass just fine, then the system will randomly hang with arguably a far less demanding load than the stress tests.
Note that I have not yet:
* reset the CMOS when changing to X.M.P. Perhaps I should?
* reseated the graphics card or CPU. The latter will require R/R of the thermal grease, which I will do if needed, but it's a pain. Since the system is stable at 1600 MHz, I assumed that all basic systems are working as they should.
* Tried to work my way up in memory speed step by stem from 1600 to 2133 to see where things fall apart.
* Tested the video memory
I suspect main system memory, despite the clean bill of health from MemTest, and based on many of the comments to others with similar problems from the veterans on this board. I don't want to push the CPU voltages too much above the default/auto values, for fear of damage and reduced lifetime.
Also, the power supply is a nice unit from an older high-end gaming rig. It is rated at 700W. The PS does probably have over 30,000 hours on it (24/7 use for 3-4 years), however. Strange that it would work at 1600 MHz fine, and with only slightly more power load at 2133. I suppose stranger things have happened.
I've read the suggestions to run only 2 sticks, rather than 4, but I can't justify dropping $140 on new memory (I don't really need the extra speed benefit, it's more curiosity and just not knowing at this point).
Anyway, perhaps more seasoned souls than I can share their thoughts. The system is perfectly usable at 1600, but I'd really like to know where the lockups are stemming from. Troubleshooting is maddening because of the inconsistency in the long times before failure and lack of repeatability to reproduce the issue.
Thanks in advance for your time.
-Paul

Thank you both for the prompt replies. I'm learning a lot.
Turns out I also found this from G.SKILL in going over reviews of the memory modules I have. Another user had a similar configuration as mine and was having similar problems. G.SKILL replied:
Quote
We are sorry to hear you were unable to get two kits working in the same system. It is not guaranteed two kits can operate at the rated specifications since they were not pre-matched, tested, and guaranteed at factory. With multi-channel motherboards, perfectly matching memory is necessary to achieve high frequency. This is why we must offer high capacity 32GB, 64GB kits, otherwise we can just sell one module at a time and have you purchase as many as you need. Unfortunately, memory does not work that way. If you purchase a 16GB kit rated at DDR3-2133, you should have absolutely no issues. For any further questions or concerns, please feel free to contact us directly for assistance.
Thank you
GSKILL SUPPORT
Not knowing any better, I simply purchased two "kits" of 2x4 GB each and installed them. Perhaps worse, if the modules were matched, I may well have mixed them up so the matched modules don't even sit in the same channels 1/3 or 2/4. G.SKILL seems to have a pretty responsive board, so I'll ask them what they suggest.
Also in the end, I really just want a stable machine. This is a basically an office/engineering machine. My initial thinking was that if the system was unstable at 2133 then there is something wrong with it that needs to be fixed. It sounds instead like getting to 2133 is not guaranteed, and is much more of an art than simply throwing the modules in and powering up the system.
I'm perfectly happy at 1600 knowing the system is stable. Indeed realizing now that 2133 requires overclocking, I may well have backed off to 1600 even if everything had worked just fine at 2300, just to trade extra stability for the (small) performance improvement that I would likely never notice anyway.
I'll put together a post for the G.SKILL forums, and if I get anything useful I'll post what I learn here for completeness.
Thanks again for the fast and informative replies. It's much appreciated.
Best,
-Paul

Msi z87-g43 random 1 beep then BSOD then restarts plz help...

Heres the list of mods on my computer Below. everything is less than 6 months old besides the Harddrive witch I used from my 3 year old HP that I used to have. So anyways my Motherboard throws a 1 beep then BSOD then restarts every once and a blue moon like literaly every few weeks weather im gaming hard or not its just so random . I had it happen again today and prier to this time it happened like over 2 weeks ago. Ive tried reseting BIOS and also did Memtest on the memory for 6-7 hours or so and it passed and even made sure the memory was compatable with the Motherboard witch it is. So now im lost and don't know what to do...is it the HardDrive possibly??? SOMEONE PLEASE HELP....... :-(
Cosmos 2 case
msi z87-g43 motherboard
Intel i7-4771 CPU
2x4 GB Patriot Viper 1600 ( memory tested for 6-7 hours with memtested and passed )
Nvidia GTX 760OC edition 2gb card
3 year old sata 1.5TB harddrive
Windows 7 home 64bit
Thermaltake Smart Series 750w PSU

This could be one of many faults. Try here : http://answers.microsoft.com/en-us/windows/forum/windows_7-system/kernel-data-inpage-error-help-pls/94003454-5e1f-459f-89e8-1a555dc5e575
First do a Chkdsk. Choose Admin command prompt and type "CHKDSK /R /F" (without the quotes), press Enter. It will ask for a reboot, press Y, and let it do it's thing. It may take an hour or so depending on how many errors it finds. If you get a cascade of errors it is likely that you have a failing hard drive.
Anyway this is a good start.

Msi z87 gd 65 gaming freezing and bsod

msi z87 gd 65 gaming freezing and bsod happens in a game or on desktop
build 26/09/2013 08:16 PM
i7 - 4770k
msi z87 gd65 gaming
corsair 32 gb ddr3 cmy32gx3m4a2400c10r
asus r9280x-dc2-3gd5 r9 280x
h110i corsair
corsair hx860i
crucial m4
cooler master cormos 2 case
system started to freeze and bsod
items I have done
osri
new psu
memtest all sticks and one at a time all passed
hd tune smart test passed
increased voltage on memory in case it was that as the x m p does it at 1.5v increase 4 steps from 1.5v to 1.9v all 4 gave the same issue
1.65v bsod as well
who crashed says amd ccc is causing the issue reinstalled with driver from asus and latest also the beta same issue is happening
this is why I think its the main board but was going to run the system from intel gpu by removing the amd gpu from system maybe even test an alt slot x8 to see what happens
currently testing r9 280z card with default gpu clock 850mhz instead of 1000mhz incase that's whats causing it
I know this is another post the other post does not have edit on the post any more so making you aware of this
any one got any ideas as to what to try next
On Sat 06/09/2014 04:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8346-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2DBA1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FFB3BA1, 0xFFFFF8800CFEE540, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 21:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8564-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600012E354)
Bugcheck code: 0x50 (0xFFFFFD00C0873680, 0x0, 0xFFFFF9600012E354, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 17:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-7909-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3267E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004A3267E, 0xFFFFF880060F6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 23:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-9796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00B7F9E50, 0x0, 0x15B641)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:54:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-7878-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800494A12B, 0xFFFFF88011FF4558, 0xFFFFF88011FF3DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-8470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF8F8F0, 0xFFFFF8800907E420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 02/09/2014 18:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8B00E9D800C, 0x0, 0xFFFFF8000397A981, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 15:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-7753-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800413B12B, 0xFFFFF88011DEF558, 0xFFFFF88011DEEDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 31/08/2014 08:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-8424-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880048308F7, 0xFFFFF88008DC2B00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 30/08/2014 22:58:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-9687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFDA801908C040, 0x2, 0x0, 0xFFFFF80003659EC9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No need to edit, just add a reply as flobelix asked for exact models of RAM and motherboard.
As it's double posting, this one gets locked. Please continue this one:
https://forum-en.msi.com/index.php?topic=183138.msg1314803#msg1314803
>>Please read and comply with the Forum Rules.<<
Topic Locked

MSI Z87-G45 and BSoD all time

Hi,
my configuration:
MSI Z87-G45,
i5 4670k
2x8 GB ddr3 Patriot Viper 3 1600MHz CL9
Radeon HD 6870
PSU Corsair 550W
HDD SATA WD 500GB
SSD Corsair Force 3 128 GB
Windows 7 64bit
...and i have BSOD all time... At first I thought that the problem is SSD, but yesterday unplugget him and put normal HDD. And still got bluescreens. I updated BIOS to version 1.4, restored default settings and I tried to manually set the memory and enable/disable XMP profile. Memtest86 passed without problems. I changed SATA ports and dunno what more to do. Help please.

Quote
no BSOD so far, so this mean that first ram piece is bad?
Have that RAM kit exchanged. Perhaps even consider a Corsair Vengeance or Vengeance Pro. http://www.corsair.com/us/memory-by-product-family/vengeance-pro-series-memory/vengeance-pro-series-16gb-2-x-8gb-ddr3-dram-1600mhz-c9-memory-kit-cmy16gx3m2a1600c9.html
Quote
IRQL_NOT_LES_OR_EQUAL 0x0000000A
This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL).
Ouch, I just rechecked your screenshot. That XMP profile calls for a CR of 3T. Your setting is 1T. That is one probable cause as per the error explanation above.
I would consider an alternative kit as 3T essentially points to a lesser quality memory chip on those modules. You can of course attempt to manually set your CR to 2T or 3T and see if it works for you.

Continious BSOD MSI Z87-GD65 Gaming OC Genie

Hello,
Some time ago i bought the MSI Z87-GD65 Gaming motherboard and every now and then try to enable OC Genie.
Every time i do this the pc gets a BSOD.
Anything i should change or ?
System:
Motherboard: MSI Z87-GD65 Gaming (bios version 1.8)
CPU: Intel Core i7 4770K Boxed
Cooling: Corsair Hydro H80i
Memory: 16GB Corsair Vengeance LP CML8GX3M2A1600C9
GPU: Point of View GeForce GTX 670 Dual Fan
PSU: Cooler Master VS V550S
HD: Samsung 840 EVO 250GB
Case: Corsair Obsidian 550D
Running on windows 7

Quote from: Frans_Butter on 28-February-14, 13:54:58
022614-9516-01.dmp 26-2-2014 18:56:25 0x00000124 00000000`00000000 fffffa80`0cbe88f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4af01c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.22436 (win7sp1_ldr.130828-1532) x64 ntoskrnl.exe+4af01c C:\Windows\Minidump\022614-9516-01.dmp 8 15 7601 262.144 26-2-2014 18:56:26
022514-11497-01.dmp 25-2-2014 16:34:04 0x00000124 00000000`00000000 fffffa80`0cf02028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+12a37 Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.21855 (win7sp1_ldr.111104-1514) x64 ntoskrnl.exe+74540 C:\Windows\Minidump\022514-11497-01.dmp 8 15 7601 293.168 25-2-2014 16:35:24
Aha! There it is! The good old 124! That is insufficient CPU V.

MSI Z87-GD65 Random BSODs

Hi everyone,
First of all here's my rig:
Intel i7 4770K @ stock clock + CM hyper 212evo
MSI z87-gd65 mobo
16GB GSkill 1866MHz RAM (4x4)
Sapphire Radeon 7870OC
120GB Samsung EVO SSD
1 TB WD Caviar Black + 1 TB Seagate + 1 TB Samsung HDDs
Thermaltake Toughpower 750W psu
Carbide 400R case + couple of case fans
Win7 x64 Ultimate
Been using this system for a while but just two days ago I had my first BSOD. And today the second one. I was just idling on desktop.
I've downloaded Blue Screen Viewer (BSV) and the error name is System Thread Exception Not Handled
BSV saying that the first one is caused by pci.sys and the second one is caused by ndis.sys.
Also ntoskrnl.exe is involved.
Any idea what should be the real cause?
Also I can copy paste the log if you tell me which part of the dump log you need.
Looking forward to hear from you guys. Thank you
Best

about killer drivers: https://forum-en.msi.com/index.php?topic=178063.0
install the latest one from this link
Quote
Can you also check the dump files to further search for another possible bsod sign?
you can check it with whocrashed: http://www.softpedia.com/get/Antivirus/WhoCrashed.shtml

MSI Z87-GD65, Freezing while gaming, then reboot loop/bsod/total failure.

Hey fellow MSI'ers
Im hoping to find a solution for my problem i have been getting. I build a custom gaming rig a few months ago (specs below)
Sinds a couple of days iv been getting wierd problems, System runs fine, i can do everything watch movies do work stuff. But when i start gaming it will work great for about 15-30 minutes, then i hear a click/beep thru the sound system, and a total pc freeze, screen freezes nothing works.
So i hit the reboot, then the system decides to turn itself off and get into a reboot loop, turning on for few seconds then turning off again for a few back on for a few, etc etc.
Only way i can get it running is pull the power, make sure the Motherboard has no charge left, then wait a bit and replug the power. Most times it will boot up fine and story starts at part 1 again.
First off i thought it would be temperature, tho im running a almoost ull watercooled system, (Ramm + cpu + video) and i put up temp controlls on my seconds screen, and they never got above 35, on any of the components.
Now seeing my build it is extreemley hard to quickly test a diffirent component, been running memtest with no problems, But when i do graphx/cpu stresstest/benchmark i get the same issue.
As i stated before it has been running perfectly for few months.
I read that PSU might be a problem, compatability wise with Haswell, tho then it wouldnt have worked for so long and just now giving these strange problems.
What i tryéd so far:
-Reinstall windows
-Flash bios
-clear bios
-unplug as much as possible
-diffirent ramm
-Running with or without crossfire enabled.
All same problems, i hope somebody has a idea without having to pull apart my custom build.
Specs:
-Cooler Master HAF XB
-Intel Haswell 4770k
-MSI Z87-GD65
-2x Asus 7970 in Crossfire.
-Corsair Dominator GT 2x4gb
-Corsair ForceGT 128GB SSD
-Antec TruePower 1200
-2x 512gb Seagate MomentusXT

Hi again,
Quote from: robinvanesch on 03-October-13, 04:33:35
UPDATE: Been running bencharmks/stresstest from onboard graphix, both cards disconnected. (lots of towels to be sure) and runs without problems, tho reallo low fps but thats expected.
Going to see if i can run 1 card at a time, see if i can cause the problem to happen again.
So did you agtually try it?
Yep, bleeding is nice job and dooing it right on all steps is needed so yeah great, but if your CPU can handel the stress and you have tested the PSU then i cant see other way.
Tip: take the hard loop,pipe, bridge(betwean the blocks away and add two 90angle fittings with long tobe, so you can rest each card away the pc 1 at time that way you dont need to bleed the system bitwean.
(allso rest of the toops needs to be so long that it can be far away...)
And yes you need reg edit your SATA drivers like xmad sayd, if you like to change IDE to RAID.
P.s. nice build! Hope you get it working
Edit: You dont need to insert that PSU in the case, just connect wires whrere they need to be, at the momen for testing.
Edit2: My current needs little service and update( add backplate, water change, delid cpu and moving GPU to bottom slot).
Edit3: Wait that one 120mm low Rad keeps your sytem 32c??? Damn you have great chips, cold house or software issue. need for delid main is the heat i dont like and i have hmm 10 times that space to get heat off :D

MSI Z87 MPower Max - Bad board? Failed SATA and B2 problems????

So here's the thing, been having problems with my system, I have a SSD as the boot drive and a RAID 5 array using the intel controller as a Data drive. It started infrequently that occassionally the system would lock up with the HDD LED on solid, Then it became progressively more and more frequently while troubleshooting.
I started out thinking it was the RAID array since after it freezes it would reboot do a verification and find some errors, so I disabled the array and tried running the WD lifeguard on each drive, each one passed a full disk scan. I tried booting the system with 1 or the 3 drives unplugged, still froze so cycled through each drive, froze each time.
Started suspecting the SSD so I cloned the drive onto a mechanical hard drive, still froze.
Unplugged the entire array and just ran the HDD alone..... didn't freeze as frequently but would still freeze.
Swapped out the RAM with good ram... Still froze.
Swapped power supplies with a good supply... Still froze.
Removed all the components except the boot drive, the RAM and the CPU..... stopped freeze up completely, instead I would get microstutters where the system would freeze for .25 to .5 seconds then continue, could tell if you played a audio stream it would keep repeating (Even a buffered stream) did a latency test and interupts were flying like mad and taking a long time to process, with no specific driver or process assigned.
Plugged the RAID array back in and it was working with the microstuttering, while trying to backup data off the array it froze again.
Rebooted the system, bios would die at B2
unplugged the RAID drives, cleared the cmos the system would boot.
Plug back in the raid drives , clear the cmos and it dies at B2.
Took out a hardware RAID controller (LSI 9260) and connected the drives up to that, dies at B2
unplug the controller... Bios boots
Plug in the controller with no drives attached, dies at B2.
Take the controller out, bios boots.
Sometimes the system gets to A2 and the screen shows snowy static
What is also strange is this occurs on both bios's.... the primary bios which I have flashed to 1.5 and the backup bios which I had left at 1.1 as a fail safe and never flashed.
Thoughts?

Hi
Almost same story happened to me.
I have now 2 pieces of Z87 MPOWER boards and both have the same issues.
1. Board came with BIOS 1.5. I left BIOS B to 1.5 and flashed BIOS A to 1.7 with MFLASH method. I installed W8.1 on my onto my SAMSUNG SSD and the PC was working for 2 or 3 days.
Then I noticed strange behavior while booting. The SSD was not found sometimes. I hit F11 and the list was full of USB pen drive entries. Then I entered the BIOS and I have seen only two menu entries: Security and one more I don't remember. Inside of the menu items it was empty or some chinese letters. So I thought the Bios was currupted. Due to missing MFLASH menu I couldn't flash the bios via MFLASH, so I had to study the German MSI Forum. Then I prepared the USB pendrive with ABUDE method and I brought back BIOS A alive. Fine, I thought: It can happen but it shouldn't. But the boot problems came back....
2. The second board came and had BIOS 1.4 installed and I didn't touch board #1 anymore . So I flashed BIOS A again to 1.7 and you know already what's coming up. Totally the same story which I had with board #1.
I switched back to BIOS B and no problems at all with booting.
After a while I noticed some BSODs because of Killer EThernet driver (bwcW8x64.sys). I had so serious problems with that driver. The problem is: If the driver fails, you are even unable to go to the internet and look for a new driver, because your ethernet is dead. Very funny, but not for me. I got the drivers from antother PC and I tried to install them. During installation it was fine. The card was working, but I was forced to do a reboot. After the reboot, the ethernet card was disabled because windows coudn't load the driver. OK, that's a windows issue or a poor driver. I tried several times. No chance to get ethernet back alive. Finally I disabled the Killer Ethernetboad and plugged my former Intel Gigabit ET Dual Port Sever Adapter in. I thought, now I get rid of all the problems. Ha ha...
First was everything fine. Then the PC didn't want to boot anymore: BIOS message --> B2.
I hit del key: "Entering setup" message came up. Nothing more. Several times. Dead.
I plugged out the Intel ethernetboard. Bios came up. I put the ethernet board to another PCI slot. 2 days of working. later on, same story.
Then I switched back to BIOS B and no problems at all.
So what's up here with my 2 MPOWER boards, showing the same issues with BIOS 1.7? What I did wrong?
- MFLASH? May be. But I don't use it anymore. I use the MSIHQ USB Flashing Tool from this forum now which was also spread in the German forum.
- I never flashed BIOS beta versions, I always red articals how to flash and I think I did nothing wrong here.
- Overclocking? No. Unfortunatelly I bought an Intel i4770 CPU without K. Funny. So no overclock issues at all.
- Memory? I have fully equipped 32GB (G.Skill F3-2400C10Q-32GTX) and did the MEM86+ test successfully.
Day before yesterday I flashed BIOS 1.6 to BIOS A. All looks good until now. The intel ethernet board behaves well. No B2 messages.
I will further comment as soon there is anything new.
Do we have some issues with BIOS 1.7? I strongly belief....
I have seen BIOS V1.81 beta is out. But where is V1.8 official release? Anyway, I am tired of testing. If I do not have issues with 1.6 then I will use it.
Unfortunately the MSI Z87 MPOWER board is not yet widely spread. Otherwise we would have more user experiences.
Ok, any comments are highly appreciate it.
@ Corellon: Sometime I got A2 messages with black screen with BIOS V1.7
Which bios version had you installed when you experienced severe problems?
I guess V1.5 & V1.6 are save. 1.7 has got problems.

MSI Z87 GD65 Gaming and msata speed issue...

Hi,
So I'm running the MSI Z87 GD65 Gaming with a 128GB SanDisk msata. Now it all works perfectly; no BSOD or crashes, but what I have noticed is that sometimes when the PC boots and I look in Intel Rapid Storage Technology, the msata on port 5 is running at 3Gb/s not 6Gb/s: I verified the speed loss using AS SSD benchmark. Reboot and it's back to 6Gb/s and back to full speed.
Anyone else seen this or have an idea of a solution?
Thanks

Quote from: JLio01 on 06-March-15, 14:21:58
How often can you notice the problem? You mentioned AS SSD Benchmark has speed loss, what's the result of speed test then?
I notice it a couple of times a day minimum

MSI z87 g45 Boot up issues

So I built a computer for my sister and her husband and it has been having some boot up issues,Here are the computer parts:
wiindows 7 64bit
MSI Z87 G45 Gaming motherboard
INTEL CORE I-7 4770K 3.5GHZ
RADEON HD 5700 GPU
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866
kINGSTON 64 GB SSD ( spare part, not sure the numbers)
Sunbeam PSU-H680-REV-US 680W ATX 12V 2.0 Power Supply - OEM
Seagate Barracuda ST2000DM001 2TB 7200 RPM
ASUS Black 12X BD-ROM 16X DVD-ROM 48X CD-ROM SATA Internal Blu-ray Drive Model BC-12B1ST/BLK/B/AS
I've cleared both the HDD and SSD and now I'm looking to check the msi z87 g45 mobo, The computer starts up and sits on a2 for a while and then sometimes it fails to detect the SSD and says a0 and then I have to go back into the bios after I reset the computer again and maybe it detected the SSD and I can set it to boot from that again because it constantly changes the boot order, and sometimes it gives a blue screen when nearly into windows and then restarts, I had transferred some data from their old computer to this one and the data had virus's in it and I didnt know so I eventually found out and a day later and got rid of them all and the computer started behaving better but not fixed, faster mainly, I don't know if the virus may have altered some files so, I have a few more things to try, any help would be appreciated.
(Something I forgot to mention is that when I unplugg the HDD all the issues go away, the computer seems to work fine, But there are no issues with the hdd, ive tested it with seatools and I plugged it into my computer and restarted mant times as well as used my computer for a while and nothing, the HDD is fine, the start up on their computer sits on a2 for a long time when it isnt going to work and it only happens with the 2tb seagate HDD plugged in)

which storage drive holds the boot files the SSD or the HDD? the ATA mode of the BIOS needs to remain in the same mode it was when Windows was deployed to the storage drive. next the only way a BIOS settings will change with out user input is if the Li cell battery is going dead/the BIOS is getting reset frequently. sounds like you're about at square one, I'd format the Seagate 2TB HDD, install windows onto that either in RAID or AHCI mode whichever your preference, you can use the 64GB SSD as caching later if you use RAID mode, if AHCI the 64GB could be spare. I don't understand the SSD as boot drive method, it doesn't make sense the solid state storage is volatile meaning it degrades over time, the HDD isn't and the performance gain isn't going to change the way you use your PC. AHCI has it's advantages it's up to you. Following those steps is the only way you're going to keep the computer booting on a regular basis. You shouldn't need to manually configure which storage drive to initialize/boot from first, the BIOS automatically goes through your devices to find boot files then boots from the first one with boot files, it won't even try to boot from a device without boot files, because it can't. Just to reiterate the BSOD you speak of sounds similar to the ATA mode changing to something other than what it was when Windows was deployed to the device.

Looking for a stable 4.8 ghz (4770k/MSI Z87-GD65 Gaming) BIOS tips?

Yeah I know. It's a lot of volts. But other than deliding it, which I will do soon, I'm looking for any BIOS tips on decreasing the voltage and keeping it from getting the BSOD after an hour of gaming and general use. This whole platform is new to me since my last OC'ing experience was with socket 775/X38.
One approach I was thinking to take is using Aida64's stress test by individually stressing the cpu, cache and memory seperately since all the controllers are individual entities now. That way if the cache is crashing from lack of voltage maybe I can come down on the vcore, or maybe turn off XMP and run at 1333mhz, etc.. If you guys have any BIOS tips I would appreciate the help. Yeah I can do 4.5/1.26 all day long but what fun is that? Thanks!
Current BIOS: E7845IMS V1.1
Build date: 4/26/2013
ME Version 9.0.2.1345
4.8 ghz/1.445V/2.0VCCIN/4.0Ring/1.2RingV/Enabled XMP profile, VDimm to 1.59. Undelided. Only ran Aida for 30 min on cpu test. Max core temps of 82C.
Another useful guide getting me to 4.8 was this:

Quote
Nice of you just how you respond to post
Hijack the thread with next to useless replies, sing praises of brand-X, and then the responses are considered not nice? As xmad recommended, open a new thread with all of your systems components. From watching an uncle overclock his MSI Z87 to 50X on air cooling, it was relatively simple with some very slow and careful bits of trial and error done in small increments. It's a poor workman that blames his tools, think of it as a challenge if nothing else.

Overclocking 4670k on Msi z87-gd65 gaming

Hello.
Im hoping someone can help me. Im having a few difficulties overclocking the i5 4670k on the superb motherboard the Msi z87-gd65 gaming
Im not sure where to even start. I did watch a youtube video that suggested cpu ration 46 and cpu core voltage 1.220 but I get a BSOD
Can anyone help please?

Quote from: headshotmsi on 10-November-13, 21:01:30
Hello.
Im hoping someone can help me. Im having a few difficulties overclocking the i5 4670k on the superb motherboard the Msi z87-gd65 gaming
Im not sure where to even start. I did watch a youtube video that suggested cpu ration 46 and cpu core voltage 1.220 but I get a BSOD
Can anyone help please?
Start upping your voltage, my chip needs [email protected] and for stability at 4.4 it needs 1.38.
Those guys on YouTube definitely got a better chip
Once you get enough voltage to boot into windows without bsod start stability testing. Make sure to set volts to override
Sent from my iPhone using Tapatalk

MSI Z87-G45 Gaming, sound from USB mouse?

Hi!
I have some issue from my new computer, see spec below.
For the information I have a MSI Z87-G45 motherboard.
I have some sound that occurs sometimes (specially during the first 2-5 minutes) when i move the mouse around.
It occurs as well sometimes when I been using the computer for a while, basically random just more frequently at the start-up.
It's hard to know from where the sound occurs, could be PSU but today I read something on another forum about the motherboard I'm using:
- Higher sound quality using USB, thanks to special adapted current power.
So i wounder if this can be the case? Is that the reason why i get this noise from inside the computer?
Is there some way to disabled this "feature" in BIOS?
Greetings
|Asus 24" LED VG248QE 144HZ (2st) | EVGA GeForce GTX 780 3GB PhysX CUDA | Intel Core i5-4670K | MSI Z87-G45 Gaming, Socket-1150 | Corsair SSD Force Series GS 240GB 2.5" | Fractal Design Define R4 Black Pearl | Crucial DDR3 BallistiX Tactical 16GB | Corsair TX 850W PSU | Noctua NH-U14S CPU Kylare | CM Storm QuickFire TK Keyboard Brown | Ace Laser Gaming Mouse EDGE 3200 | QPAD XXXL |

The sound sounds like the old mechanics hdd kinda.
It comes inside the computer, not the speakers.
My feelings is that it can be the PSU as well, just wanted to check this first, since it most often comes when i move my mouse.

Msi Z87-GD65 Booting Failure With eSATA Drives

Hi Folks,
Before I go down the (probably ill-fated) Customer Service path I thought I'd address the forum here on a little problem I'm having with my Z87-GD65.
IN essence, if I have a hard drive connected to my eSATA port the PC won't boot. I'm using an ICYDOCK 4 bay external enclosure (MB561US-4SB if interested). If the drive itself is on but the HD trays are ejected then it boots. If any of the drives are secured then it'll hang at a post-BIOS/pre-Windows screen where all I get is a blinking cursor for about 30 seconds and then it disappears to a plain black screen. If the device is powered off then it boots.
I've checked the BIOS with one of the HDs running and it doesn't appear within my boot list - in fact, except for one selection in the bios allowing me to disable eSATA there really isn't much I can do there.
I've upgraded my BIOS to 1.30 from 1.00 and the process seems to move a bit further - now I get the oh-so-pretty ugly Windows logo and that's all.
When I do actually boot the PC with the ICYDOCK off then I'm able to get into Windows normally, and turn on the ICYDOCK. After a few seconds all 4 hard drives report in and everything's fine.
I've been using this ICYDOCK for about a year and a half, with 2 other motherboards (neither were an MSI) and i7 cores, and neither of them caused me any issues. I remember that neither of those boards had the port multiplier eSATA capability so I had to buy a controller card with that capability. I could probably dig that up and see if the problem remains.
In case you're wondering, if it helps, I built a Msi Z87-GD65/4770 i7 - based PC with 2 internal 2TB Hard Drives, and 16gb RAM. I already mentioned the ICYDOCK. I used LiveUpdate to install all the latest drivers & BIOS before uninstalling it.
I build & repair PCs for a living so I'm pretty familiar with what's going on with the system. I figure that there must be something happening between the BIOS and Windows "handoff" of the ICYDOCK, but I'm damned if I can figure out just what.

More information please. PSU, OS being used, etc..
Live Update is best uninstalled. Flash UEFI/BIOS the safer way;
https://forum-en.msi.com/index.php?topic=169827.0
Recommend to download drivers and utilities from the MSI Websites and install manually.
>> Posting Guide <<

Msi z87 bsod's

Similar Messages

Maybe you are looking for