MSI P55-GD65 Freezing and BSOD Problem?

Hello I got a weird problem with my new PC, I bought some new components to my PC (I5 750, MSI P55 GD65, 2x2GB RAM DDR3 Corsair TW3XG1333C9DHX), Well the problem is that I'm getting freezing issues everytime (Sometime just surfing on internet, other times doing nothing at all) and sometimes BSOD. I check even log and all it said is "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
Also, I tried to reinstall Win 7 but it froze on installation, I installed it on my third try.
I ran Memtest86 with no errors, I check the temp on CPU, GPU, HD and they were normal.
What could be the problem?
Thanks for the help, I really need it :(

Quote from: chad179 on 28-June-10, 09:17:30
If u mean how the voltage is set on those thing there it is:
High vdrop----------------------------Low vdrop
vcore - Auto (1.22500v)---------------1.30
vtt - Auto (1.097v)--------------------1.22
dram voltage- 1.600v-------------------1.65
pll -Auto (1.800v)-----------------------1.85
pch - Auto (1.050v)----------------------1.10
Change those voltages to the onee's on the right. Change your memory back to 1t, use the lower qpi setting, and 5x memory multiplyer. I really believe its because your using a incorrect memory multiplyer. With these voltages and a good cpu cooler you can run blk up to 180. Let me know what happens.
It's safe to do all this change?

Similar Messages

MSI P55-GD65 freeze

Hi,
I recently set up a system with:
MSI P55 GD65 BIOS ver 1.20
Intel i5-750 Lynnfield 2.66 GHz
Corsair TW3X4G1333C9 DDR3 1333 4GB (2x2)
Corsair TX-750 PSU
I'm having random freezes even booting "Winki" from the DVD I found with the motherboard (I also have Win7 64bit but has not fresh installed from prior configuration (Asus socket AM2 board) so instability could be due to many causes, but not with Winki).
I tryed only the standard settings in BIOS ("Optimized and Failsafe") because I don't know what changes are safe in CPU or Memory settings.
I didn't try to update the BIOS yet because this is my second P55 GD65 Motherboard sent me after RMAed the first (that had the same issues) because after the BIOS update made with M-Flash, it died. After death of first motherboard, I read MSI forum and discovered (too late) that M-Flash is not safe for BIOS update (https://forum-en.msi.com/index.php?topic=119375.0). I also read (again, too late) that to update BIOS is recommended a stable system (https://forum-en.msi.com/index.php?topic=103441.0).
I read also that with Corsair RAMs, the voltage and/or timings have to be changed, but I don't know neither where (I see the menu in BIOS but I don't know which particular settings have to be changed) nor how much I can change settings without risk of damages.
I hope to have written all the necessary info and I apologize for my english, I'm italian

I will reinstall Win7 but I would like to have a stable machine first. At this moment I'm booting with Winki but sometimes and randomly it freezes, so I think it's not a software problem but an hardware/bios one.

MSI P67A GD65 Multiplier and software problems

Hi
i just bought i5 2500k and Msi mb, it came with 1.4 bios version and the maximum multiplier that i could log into Windows was 44 even though the vcore adjustment didnt work properly
maxing out at 1.224 (bios reading) no matter the voltage set manually, I updated to 1.7B4 and i was able to get into windows at 46x100 the downside of the new bios was the memory suddenly stopped working at 2133 10-11-11-30 1.65v even 12-12-12-30 would end up in oc failed message so i had to settle for 1866. Now i updated to 1.8B5 and i can run my memory at 10-11-11-30 again no problem but
maximum muliplier went down to 44... again - theres no way to make system work with 45 or higher multiplier so basically oc-wise 1.8B5 is like 1.4 with vcore adjustment working properly/pll fix - Plz p67 users need proper bios.
Second problem is that Overcloking center crashes with 0xc0000005 code right after launching exe - first happened on my old XP SP3 so i installed fresh Win7 unfortunatelly its the same story.

Ok now im mad i flashed back to 1.7B4 and guess what i cant choose any multiplier above 44! Whats weird is that although bios version says 1.7B4 its behaving exactly like 1.8B5
Every time i changed some voltage option in bios V1.4 or V.1.7B4 the pc would power down and then power up, since 1.8B5 it would just reset. That and inability to go above x44 when just yesterday
i could go x46 (i didnt check more as i want to run my SB below 1.35vcore) makes me think my cpu is artificially locked and ability to go above x44 in 1.7B4 was just an accident that was
corrected in 1.8B5 whch has some code inside that prevents (in case somebody wants to downgrade) to update data responsible for cpu oc. Another example supporting that is that my cpu can
boot up at 4.4 ghz@stock voltage (1.168 in bios) log into windows and run some tests , of course it would freeze and reset randomly after some seconds or minutes but still... On the other hand changing the mulitplier to 45 and vcore up to 1.4v doesnt even make HDD start spinning and load WIndows after the MSI logo screen vanishes, its just seems locked.

[WTA] MSI P55-GD65 6 phase on all the time? Where's APS?

Hello, First Post here..
I bought a MSI P55-GD65 lately and it runs spectacular and overclocks nicely. the newer BIOS 1.6 is noticably more stable when High VDroop is used than the BIOS 1.5, resulting in more power-efficient system of my own despite overclocking .
But nonetheless, i have some issues i would like to be answered:
1. When I use BIOS 1.5, the core voltage would be dropped to 0.896 (CPU-Z) when i set the core voltage as auto and all the power saving features enabled (C1E & EIST Enabled, C6 state selected, Turbo Mode off). but when i flash into BIOS 1.6, the same setting does not result in decreased voltage, the core clock still slows down though like it used to be. Maybe the next revision of BIOS will fix it?
2. I searched this forum about APS on P55-GD65, i have found that somebody here had testified that the BIOS 1.6 fixes the all-phase-working problem, as i was having the same problem too. Then i decided to flash to 1.6 too (which work flawlessly with your USB Flasher by the way, kudos ). But the problem still persists. APS only works when i apply through Control Center. i wonder about APS statement of "will work regardless of operating system" is a true and automated one. And yeah, i have tried to clear CMOS and run it on nominal mode and still no changes from BIOS 1.5. The 6 phase LED is lit all the time unless i "apply" in Control Center.
My Current system are:
MSI P55-GD65 (Lotes ILM)
I5 750
HD 5770
Silverstone Zeus 750Watt
WDC Black 500GB
Windows 7 Ultimate
Thanks for your attention.

Quote from: chrisjb on 19-January-10, 17:13:56
you have to run the cpu at default settings so (133mhz X multiplier) the slight overclock of the cpu will disable power saving so all the phase leds will constantly be lit up.
Have the multiplier running at 160 because of XPM 1600 memory blocks, and the board runs with 2/3 phases in normal mode.
Are using BIOS 1.3 because of XPM problems with other versions.

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 P55-GD65 + Corsair XMS3 CM3X2G1333C9 = Random freezes,buzzes,reboots..

Hello..
My system specs are:
Mobo: MSI P55-GD65
CPU: Intel Core i7-860 (with Megahalems heatsink)
RAM: 2x 2x2GB (dual channel = 8GB in total) Corsair XMS3 CM3X2G1333C9
GPU: ATI HD5770
PSU: Corsair HX520W
The problem I face, is that I get random freezes (sometimes this is accompanied by a loud buzzzzzzzzzzzzzzz coming out of my speakers), or cold reboots. It's not something that is triggered by some specific action (e.g when I run a specific application or something like that), sometimes there are days that I don't get a single reboot, and other days that I get 4-5 freezes one after another..
I read in another forum, that this specific series of motherboards (GDxx) have some trouble dealing with certain memory brands, especially corsair. I don't know if that's true, just throwing it out there if someone has any similar experience to share..
So far I've tested my memory with memtest (overnight 8 hour test, it completed a few cycles), I've tested my cpu with a several hour prime95 small FFT test, which stressed my CPU in 100% for a few hours but that didn't trigger a freeze or a reboot. My temps are perfectly nice and normal..
Reading from Everest, I still use the AMI v1.0 version of the BIOS, but I don't tend to update things that work (there were a couple of times in the past that this only made things worse). I have set my bios settings to auto, do I don't know if I should play around with anything there, I must say though I've always been a bit skeptical about changing voltages or something (never played with overclocking in my whole life), fearing that I could damage anything, or at least lower its "expiration date"..
I hope someone expert can help me out..
PS. I must say this mobo is the second one I got, my first GD65 was replaced, but it had nothing to do with similar issues, I accidentally damaged the cpu socket. I can't seem to recall though, if I had such problems with my first mobo too..

Quote
So far I've tested my memory with memtest (overnight 8 hour test, it completed a few cycles), I've tested my cpu with a several hour prime95 small FFT test, which stressed my CPU in 100% for a few hours but that didn't trigger a freeze or a reboot.
As gcanuck mentioned, in BIOS Cell Menu, Spread Spectrum should be disabled. If not done so, test each RAM stick individually in the primary black dimm slot. DRAM V. maximum is 1.65v's. It also may be that the CPU IMC refuses to cooperate. With only two sticks in the black slots, does this freeze problem continue? Another possibility is that the two RAM kits are of different chips even though they have the same specs. Are the batch numbers the same? Some may have Elpida chips, & the other kit Samsung.
Quote
Although another guy in another topic suggested even higher voltages, up to 1.79V (!!!!)
Whoever advised that is a moronic idiot!

Problems with MSI P55-GD65

Hello,
I purchased an MSI P55-GD65 mobo approximately a month ago and have been having some problems with it. When I first started it, everything turned on fine. I attempted using OC Genie and began to encounter problems restarting the computer. Either the computer would turn on but I would receive a blank black screen and would have to perform a hard shutdown, or the computer would turn on, stay on for 3 seconds, then reboot. I realize the latter problem is an overclocking protection measure. Occasionally the computer would start right off the bat, but this is a rare event. At first I thought this was due to bad overclocking, so I set all BIOS settings to default. It seemed to work fine for a few days, but now I am experiencing these problems with default settings. I am currently testing both sticks of RAM with memtest. During testing of 1 stick, my computer went to a black screen and stopped responding. However, I have been unable to reproduce this effect and so far no errors are being reported. I reseated the CPU to reset my fan, yet the problems began before this. I think it might be the RAM,but I am worried that either I have a short (in which case I wouldn't know how to find it), or I have a damaged motherboard (in which case I am past my RMA date). Any help would be appreciated! Thanks!

Hey, thanks for the quick response! I have cleared CMOS and am currently retesting. I will update with further results. Additionally, I forgot 1 more symptom. When the POST screen comes up, it turns into a blank white screen and I have to perform a hard shutdown. This has only happened twice though.

MSI P55-GD65 problem

Computer is new, hardware bought via internet. After first run everything was good - no problems, but when I tried to install Windows XP appeared an error (unfortunately I didn't type down what exactly was written on screen), something like an error or failure of BIOS components. The installation was interrupted and after next start I heard one short - beep. After few seconds I see black screen and I can't do nothing.
I tried to run a computer with a single RAM card, and was trying to change it's location - but with no result.
My computer:
MSI P55-GD65
Core i5 750
PowerColor Radeon HD4870
Samsung 500GB 7200rpm 16MB cache SATA-II F3
OCZ ModXStream Pro 500W
Patriot 2x2GB 1333MHz Dual Viper II Sector 5(PVV34G1333LLK)
bios version 1.3

If this problem appears again:
Quote
when I tried to install Windows XP appeared an error (unfortunately I didn't type down what exactly was written on screen), something like an error or failure of BIOS components.
... please write down the STOP Error Code.

MSI P55 GD65 - BSOD - MEMORY_MANAGEMENT

I'm facing a weird issue with my pc:
If I turn on the PC, the system starts up fine, but within 30 secs up to 5 minutes I get a BSOD (usually MEMORY_MANAGEMENT).
If I then restart the system it will run fine..
CPU intensive gaming, memory checks, benchmarks, standby and wakeup, all runs fine... after a first BSOD.
I've tried all kinds of memory settings, but nothing seems to help. Also hard to test if it runs fine after a crash.
It's almost like the system needs to warm-up a bit and then it will run fine
The BSOD message indicates a memory issue, but then I would expect random BSOD, not only right after cold start.
Any suggestions?
MSI P55 GD65 - latest 1.9 bios
i875k
Windows 7 64bit
Geil DDR3-1600 2x2GB Black Dragon GB34GB1600C8DC
This Geil ram is not in the MSI memory list but Geil shows the MSI P55 GD65 in their compatibility list for this memory:
"All motherboards listed on the GeIL Qualified Motherboard List – GQML have been tested with the specified GeIL memory kits for compatibility, stability and
performance by GeILs’ FAE to ensure best quality."
http://www.geil.com.tw/uploads/download_files/c8c397a9533d1896e708e3c106a99cb3.pdf

Status update:
I've reset the bios to safe defaults.
Started up memtest86+ and screen turned red rather then blue, so lots of mem-errors.
Restarted and then memtest ran fine for more then 10 hours.
Passed 20 times all tests no errors with both Dimms inserted.
Then I tested cold start with 1 dimm only:
- with 1 DIMM in slot 3 only system cold-starts fine and memtest runs fine with no errors.
- with 1 DIMM in slot 1 only system cold-starts fine and memtest starts up but then doesn't even start a test. So it seems to be hanging already.
Swapping both dimms showed the same result.
Preliminary conclusion now is a faulty slot 1
Does it indeed sound like a slot 1 issue?
MB is the worst part to RMA, so hopefully I can find a solution.... slot 1 seems not to be completely broken after all.
PS: increasing to 1.6V I had already tried before without success.

MSI P55-GD65 (HARDWARE COMPATIBILITY)

MY HARDWARE SPECIFICATION
Processor:   Intelcore i5-650 (3.20G)
Motherboard:   MSI P55-GD65
Memory:   G. Skill Trident DDR3-2000 cl9 2x2GB
Harddisk:   500GB WD Digital SATA
Video Card:   Sapphire HD5850
Player:   Samsung 22x SH-S223Q/L SATA LS
Power Supply:   Silverstone DA750 (decathlon)
I'm having a problem with my PC set up.. every time i play a game it just simply stops. not just the game but the whole computer. it freezes and never works again and then i have to restart and then play restart.as soon as i start playing any kind of game it simply freezes.. im using Windows 7 64-bit operating system and played the game ARMA 2. also played HoN. when i play any kind of game still the same effect. are there any incompatible hardware that i have installed into my CPU? need help badly..

What is your current BIOS Version?
Please run a test with the following setting:
-> Disable XMP in BIOS Setup (if enabled) and ensure that the memory speed is set to DDR3-1333 for now (and not one bit more)
-> Manually set the DRAM Voltage to ~1.575V
-> Manually set the Memory Command Rate to 2T/2N
-> Disable Spread Spectrum

MSI P55 GD65 Booting issue [SOLVED]

Hello everyone!
I finished a new build two days ago:
Intel i5-750, 2.66GHz
MSI P55-GD65, rev. 1.0, BIOS 1.3, Lotes socket
A-DATA 2x2GB DDR3 1600Mhz CL8 Vitesta Extreme Edition
GIGABYTE ATi R5850 1GB
KINGSTON V-series SSD 64GB SATA
SAMSUNG SpinPoint F3 500GB SATA 7200rpm
Artic Cooling Fusion 550, 550W, dc outputs are mentioned below
and some minor components (optical drives, wifi card etc.)
I started the computer and everything seemed fine. I managed to enter the bios. I was checking H/W monitor and several other options, I didn't change anything. Suddenly (after circa 5mins) the computer shut down and started to turning on and off repeatedly. I stopped the loop by turning off the power supply. I started it again, however it got stuck in the loop imediately. After a while I managed to access the bios again, meanwhile I was trying to find some answers on internet.
I decided to remove all memory sticks (as a lot of topics here in forum which are describing the very same problem sign RAM problem) and started computer. I expected beeps and LED-show. However, the computer didn't start at all! Even fans were not spinning, just nothing (although PSU was giving tension). I put RAM back and computer started. It was like black magic. I tried again, remove RAM - no start, put RAM back - no start too. Mobo went definitely dead. So I RMAed it.
I've obtained a new one, which was:
MSI P55-GD65, rev. 1.0, BIOS 1.2, Foxconn socket
I put all the stuff together and started computer. Everything went fine, I managed to enter the bios. Nevertheless, I decided to check RAMs for sure; I changed booting devices, restarted and booted system rescue cd with some utils. I started memcheck basic test. The basic test was fine with no errors, then I started filling with random pattern test. It ran for almost 24h. I wanted to try another exercise test and... computer shut down and the loop was there once AGAIN!
I don't think the mobo is the issue here anymore. I bet on two things: PSU or RAM (I'm not going to think about CPU!)
I don't recall exact dc ouputs but: AC Fusion has 2 12V rails with 17A each. Mobo needs 18A, but as I understand it, I have to check 2 rails combined against the requirement - 34A > 18A, it's okay, isn't it? I've choosen this one as I wanted silent PSU (it performed really good in tests, f.e.: http://www.anandtech.com/casecoolingpsus/showdoc.aspx?i=3516). I don't have any other similar PSU to swap (neither my friends).
My suspicion is the problem is RAM incompatibility. My RAMs (AD31600E002GU2K) have 1.65-1.8V working voltage. Maybe the mobo sets auto settings badly (I'm not present at my computer now, I left for the weekend); they are not in QVL too (http://eu.msi.com/uploads/test_report/TR10_1846.pdf). The problem is I was not able to get into bios before I left. As I read on the internet, P55 is pretty touchy when it comes to RAM. I'm thinking about swapping them for Kingston 2x2GB 1333MHz DDR3 CL7 (http://www.valueram.com/datasheets/KHX1333C7D3K2_4GX.pdf; which are not in QVL either, but KHX1333C8D3K2_4GX are; only latency difference).
Any advices on the whole problem?
P.S.: I've tried CMOS clear on the former one too, no change. As I mention I went through the most of the gd65 booting issues posts here on MSI forum and several others.

Do you think Corsair VX550 550W could do the job? It has a single rail with 41A on 12V. ATi certified Straightpower BQT E6-550W for 5850, which has 4 rails per 18A, but overall 41A too (http://www.be-quiet.net/be-quiet.net/data/media/_stories/216/sp_e6_550_EN.pdf).

MSI p55 gd65 will not post

hey guys i'm having problems with my MSI p55 gd65
the build is
i7 860
msi p55 gd65
antec signiture 650w
ati 3450
seagate 7200 400GB hdd
8GB Corsair xms3 1333mhz
( i know some parts are under powered but it is going to form the basis of my new home server)
anyway i managed to get server 2008 R2 installed last night so all was working for a while but after restarting after changing the comp name and registering with Microsoft (i.e first actions) the computer refuses to post.
upon pressing the power button the power supply ticks as though there is a shot in the build somewhere , however i have tried to build this both inside and outside of a case and the same occurs.
Thinking it could be a psu issue i tried powering another machine with the psu and it fired no problems.
so i thought i would strip down the mother board to basics and ran the board with memory and cpu only the same occurred i have tried various different combinations of Hardware but to no avail. the only little joy i did have is when i removed the 4 pin mobo connector and then hte board starts going into a loop of lighting up the board leds for less than a second then tripping out as previous
i have tried reseting bios on various occasions
i have tried everything i can think of is it time to RMA the board i just feel that there is something i maybe overlooking

I have tried both of the above and the same still occurs
i have tried a different psu from the machine i am typing from now and had no joy
i believe for whatever reason my motherboard is dead (or at least shorting for some reason)
unless there are any other ideas i think i'm going RMA

MSI P55 GD65 registers only 4gb of memory.

To start off here's my system:
CPU: Intel i5 750
Motherboard: MSI P55 GD65
Ram: 4x 2gb G.SKILL Ripjaws DDR3 1600 dual channel memory (8gb total)
Video card: nvidia 9600gt 512mb (temp till new AMD cards)
The bios boot screen states 4gb of DDR3 1333 ram. Going into bios, it does recognize that 4x2gb sticks are in the system, but still states only 4gb of ram available. Booting into Win7 64-bit, the Performance and Information screen states 8gb (3.99gb usable). Task manager/resource monitor also show only 4gb total. Essentially, the system knows there's 8gb but will only use 4gb.
I've been told to check for a memory remapping option in the bios, but I've seen no such option so far.
Link to hardocp thread on the same subject: http://hardforums.com/showthread.php?t=1452669

I have just recently experienced this problem. I built my machine about 3 weeks ago and everything was working great, booted first try and no errors in memtest+ or LinX or Prime95. I have been running just fine since then. I have MSI P55-GD65, Core i5 750, DDR3 2x2GB GSkill Trident 2000MHz RAM.
This past weekend I decided to mildly overclock, I upped the bclk to 160 and adjusted the DIMM voltage to 1.6 according to the RAM spec. I tested and tested this config and everything seemed stable. I have been using the machine to play games and things with no problems.
I go to resume from hibernate this morning and the machine hangs. I restart and I notice BIOS is only showing 2GB during POST. I check out the BIOS settings and it sees the 2 DIMMS, but still only shows 2GB. I boot into Windows 7 x64 and it shows 4GB (2GB Useable). Previously all 4GB were recognized and useable just fine. This may be relevant, I don't know, but I started a long video transcoding job before bed last night. Presumably this job finished and the machine went into hibernate.
I reset all settings back to default, thinking maybe my overclock wasn't as stable as I thought, but no change. Even before I reset the clocks, I tried upping the DIMM voltage, the VTT voltage, reducing RAM frequency. Nothing.
I figure maybe I need to upgrade the BIOS, as I am currently running v1.5 and latest is 1.8. I download the 1.8 image to a flash drive and try to use M-Flash to boot the BIOS image off the drive, but BIOS hangs with a repeating BEEP when I try that.
Then I noticed something very odd. When I boot up with the flash drive plugged into a USB port, BIOS reports 4GB on POST. Without the drive, 2GB on POST.
As an absolute last resort I will reseat the CPU, but after the flash drive behaviour, I am not sure it is a CPU pin-contact issue. When I get home from work I am going to flash to v1.8 BIOS and see if that helps. If not, I will reseat all DIMMS and try that. If the problem persists, I will try DIMMS individually and in different sockets and see.
Is there anything else I should try before reseating the CPU? What if I just wiggle the heatsink? If it all possible, I would like to avoid having to clean up the TIM and reapply, it was a big pain on my heatsink.
Thanks,
--MrAnt--
EDIT: Forgot to list detailed system specs
MSI P55-GD65 v1.5 BIOS
Intel Core i5 750 @ 2.66GHz
CM Hyper 212+ HSF
GSkill Trident 2x2GB DDR3 2000 - F3-16000CL9D-4GBTD (Running @ 1333MHz 9-9-9-24)
WD Caviar Black WD1002FAEX 1TB HDD
Corsair CMPSU-750TX 750W
Sapphire Radeon 5850 1GB

Msi p55-gd65 wont start up

trying to build a new pc so i bought a Intel upgrade kit from komplett with
Intel Core™ i7 Quad Processor i7-860 2,80GHz, Socket LGA1156, 8MB,
MSI P55-GD65, P55, Socket-1156, DDR34 DDRIII, ATX, 2xPCI-Ex(2.0)x16, GbLan(Winki), OC Genie, DrMOS, Super pip
Crucial DDR3 1066MHz 4GB KIT, CL7,Kit w/two matched DDR3 2GB, 240pin
WD Caviar® Black 1TB 3,5", SATA,32MB Cache, Dual Processor, 7200RPM
my old part are 600w x-power atx12v ver.2.2 compliant and nvidia 8800 gts 320mb gddr3-320bit-dual dvi
and a Antec Twelve Hundred Big Tower Black
problem is it wont boot up keeps stoping after about 5 or 6 secs and starts again
ive tryed reinstalling ever thing again and using one stick of ram runing out of ideas
help me please

download the manual from msi site , then look at different light configuration and compare it to what you see on your board when it keeps rebooting, then from the manual you should see possible causes. i give you an example
i see red red blue red {each light can be blue or red or green,or off}.
and on the manual such config gives the possible cause, cpu not sited properly or memory not installed..
from what you have described it looks you have bios problem which means you have to return it to the seller or nearest msi dealer.
http://i240.photobucket.com/albums/ff177/kourosh22/pp45.jpg

[MSI P55-GD65] Different XMP readings from MSI Control Center, CPU-z, BIOS

Hello,
I have a MSI P55-GD65 with a 4 GB Corsair XMP DDR3-1600 CL8 kit (2x2GB, in dual channel configuration),
however I am getting very different readings for the XMP profile from MSI Control Center, CPU-z and the BIOS.
Here is a screenshot from CPU-z and Control Center: http://img683.imageshack.us/img683/2217/xmpv.jpg
The memory is rated at 1.65v for 1600mhz CL8, however control center reports it as being 1.5v, CL9.
CPU-z reports timing rate to be 2T, however when setting the RAM settings to XMP/Auto in the BIOS (which automatically clocks to 1600 mhz, CL8),
timing rate gets set to 1T (which tends to be unstable with CL8).
So my question is: how can I reliably read the XMP information? My bios is the latest version by the way (v1.9).

Quote
the bios readings are almost the same, except that the BIOS sets 1T timing.
The BIOS readings (or: what the BIOS actually sets) is not that important when we talk about SPD/XMP Profiles. When you are in BIOS Setup you should be able to find Memory-Z which does nothing else but reading the SPD/XMP Profiles that are programmed onto the SPD Chip (regardless of what the actual settings are).
Quote
So I'll just use the bios XMP settings but change the timing to 2T and see if that is stable.
Yes. AND: The fact that the BIOS automatically sets the Command Rate to 1T instead of 2T is not okay. Please report this problem to MSI Technical Support: http://support.msi.com/

MSI P55-GD65 Freezing and BSOD Problem?

Similar Messages

Maybe you are looking for