P55 gd 65 RMA

Well contacted msi support on my pcie running 8x instead of 16x and this was their reply:
If the bios did not fix the PCIE speed, we will need to issue you an RMA. You will receive an email which contains and RMA number and instructions.
How long does an rma take? and since its running at 8x which is fine for the 5770 i dont think its worth waiting and paying for the rma

RMA process is unpredictable and depends on where you stay. Some countries are fast, whereas some can take a week or two.

Similar Messages

RMAed 4890 making high pitch sound in game

MSI P55-GD80
I5 750
Cosair dominator 2x2gb
MSI 4890 cyclone
win7 64bit
ocz 700w
just got RMAed 4890 back
it's making high pitch sound whever I start gaming
did have this before RMA, when it was working
I remember this sound from back in the nvidia 7xxx/8xxx series, remember reading somewhere it was normal for cap to make this kind of sound?
not sure....

That sound can happen on video cards and is usually generated by some coil on the card when the card si heavy loaded .I have it on my 4850 and in 3D Mark 03 on my 5770.Never had it on my previous Nvidia cards though.You can have that with your PSU too.If your card is performing ok don t worry about it.Try and use V-Sync ON in driver control panel ,it may fix the anoying sound ,at least in some games.

MSI P55-GD55 Won't post 3 Beeps-Need Assistance

Built many PCs but never had a problem like this. Starting to think MB is bad.
Built this in Dec 2008
MSI P55-GD55
A-DATA Gaming Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
Intel Core i5-750
OCZ ModXStream Pro OCZ500MXSP 500W
MSI N95GT-MD512Z GeForce 9500 GT 512MB 128-bit GDDR2 PCI Express 2.0 x16 HDCP Ready Video Card
Western Digital Caviar Black WD1001FALS 1TB
COOLER MASTER Hyper 212 Plus Cooler
2 weeks ago PC would do nothing at all after I turned off and then tried to restart. Thought I had bad power supply, but it checked out. Cleared cmos by removing battery and turned off oc genie and that seemed to cure problem.
Left PC on ever since. Had to turn off yesterday to check unrelated network issue and when I tried to restart It won't post. Just get 3 beeps. No video. Nothing. Tried to clear cmos, switch memory sticks, only use one mem stick in slot 1 and I get nothing but 3 beeps. Very unlikely that both sticks are bad. Tried powering on from internal switch and got nothing but 3 beeps. Beeps are less than 1 second in duration so I guess they are short beeps.
Any thoughts are greatly appreciated.
If I have to RMA to MSI how long does it take to get replacement? What do I have to send to MSI, all contents of retail box or just the board?

Quote
If I have to RMA to MSI how long does it take to get replacement?
Quote
I am ready to toss this board and buy another unless I can get this working.
At the moment there is know certainty about the definate cause for your problem. What makes you so sure that the board is the cause (and not your CPU (which hosts the memory controller, after all), faulty RAM sticks (have you tested every single stick of RAM you have in the first slot (check user manual) and cleared CMOS (with A/C power cable unplugged from PSU before each new start-up attempt)?).
A contact problem between CPU Pads and board socket pins could also cause this (please reseat CPU and heatsink). Another possible cause is a short-circuit problem inside the case (test the board outside the case on a non-conducting surface).

Occasional GPU (N580GTX TF II/OC) freezes (usually recovers), should I RMA?

About a week ago after being depressed with Rage's poor performance with my Radeon HD5850 I went ahead and ordered a shiny MSI N580GTX Twin Frozr II/OC. After it arrived I installed it and it seemed to work fine (at least in Rage), but then I found that certain games (World of Warcraft, Battlefield 3, some other game I forget) would infrequently freeze or cause my screen to go black, after which I needed to CTRL+ALT+DEL to get to the task manager to close the program. Usually I'd also see a popup telling me the GPU/driver stopped responding and was succesfully reset/recovered. (Sometimes I wouldn't get this popup, and sometimes instead of just the game freezing, the whole PC would freeze - though the latter is somewhat rare).
Now, initially I had a CoolerMaster Real Power 520W power supply, with only 19A on both 12V rails (38A total). This power supply was obviously not enough for my GPU so the first thing I did was order a CoolerMaster Silent Pro M 700W PSU, with a single 12V rail with 50A. To my horror, after installing this I discovered I still had the same sort of freezes. According to GPU-Z my GPU wasn't getting too hot, as far as I could tell (79°C being the highest temperature measured during full load), and my case has a decent airflow (two 120MM fans as intake and exhaust).
Then, to rule out a flaky PSU or anything else in my system, I went ahead and installed my GPU in a different machine with a Corsair RX750W PSU, but the issue remained, after 1-2 hours of playing Battlefield 3, the game would freeze in the manner described above. Finally I also tried a bunch of the NVIDIA drivers in the 28x.xx series (280.26, 285.38, and 285.62), to no avail.
So now I've kind of ran out of ideas, and I'm starting to wonder if my GPU has a defect. Could this be the case? Should I RMA it? I'm a bit weary of sending it back to the shop where I bought it, considering it can literally take hours before some of the games I've tested freeze (Rage for example hasn't frozen up on me at all yet despite over 11 hours of play time, BF3 can take up to an hour or two before it freezes) - I doubt they will be willing to spend that much time to verify that it is faulty.
PS. I've googled around a bit and saw some anecdotal evidence that this could be an issue with the 28x.xx driver series, and I'm tempted to give it a try, but that would probably not help me with getting Rage and Battlefield 3 to run since they depend on more recent drivers :/ (I'll probably give it a shot anyway this weekend just to see what happens)

Thanks for your reply, I have 'discarded' the old 520W power supply already since I guess using that is asking for trouble However I'm not sure if this is a specific issue to Battlefield 3 since I had other games crash as well - but.. I haven't really tested anything other than BF3 after installing the new 700W power supply, so I'll spend some time to see if those still crash. If they still crash/freeze like BF3 does, I'll post a reply here
Also, since I forgot in my initial post, here are my full (current) system specs:
CPU: Intel Core i7 870
MOBO: Gigabyte P55-USB3 (BIOS version F9 2010-11-01)
MEM: 4x2GB DDR3 Kingston PC3-10700 (667MHz)
GPU: MSI N580GTX Twin Frozr II/OC (Label top line: 912-V255-067, S/N:602-V255-060B1108015588, BIOS version: 70.10.20.00.01, Default clocks: 800-core/2048-memory/1600-shader, Default voltage: 1038mV)
HDD: Samsung HD103SJ / Samsung HD753LJ
OS: Windows 7 64bit
PSU: Cooler Master Silent Pro M700, 700W, 50A @ +12V (Full DC output: http://www.coolermaster.com/upload/product_feature/SilentProM700-6.jpg)
Should probably point out that before replacing my Radeon HD5850 with the new 580GTX I have not had any stability issues

P55-GD65 BIOS bug

Hi! I`m having compatibility problems with my imon remote/reciever! It is supposed to turn the computer ON but the BIOS won`t let it! There`s no option in the BIOS for turning on the computer by USB device! It works by shorting the power button pins, but if the USB cable is connected it doesn`t work.

Songokussm the same issues I reported to support, they responded to me, that my MB is faulty and I should RMA ( did it twice, 4 month without MB ) I prove them otherwise, I had 3MB P55-GD65 with the same issues. Short speaking every MB with ERP=040 is faulty on engineering level Overvoltage like you described, problems with fans on sysfan1 and sysfan2, restore AC on power loss not working correctly and sometimes USB2 stops responding.
My conversation with MSI support ended when they statement that they can`t check if I`m correct because they don`t have MB with ERP=040, so the problem is .... gone I bet that with bios 1.9 in your case issue still occur but is`t less "visible".

P55-GD65:USBPORT.SYS fault

Nothing than troubles with this one.this is my first MSI board and it will be my last MSI board nothing then troubles with it
When i remove the webcam from the system the PC starts automatic again.
When i unmarked automatic reboot then i get this fault "USBPORT.SYS"(blue screen)
When i do the same with usb stick it works fine,i have this problem only with the web cam and in all the usb ports
And it is only in Win xp and the fault is not when i unplug the webcam in win7.
Log files of win xp let see this:
ftdisk id-57
0000: 00 00 00 00 01 00 be 00 ......¾.
0008: 02 00 00 00 39 00 04 80 ....9..
0010: 00 00 00 00 0e 00 00 c0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
P55-GD65
I7 860
Antec 750W Truepower
Antec W160 case
4GB corsair TW3X4G1600C9D
Samsung F1 sata
2x ide 120HD
synthe ninja cooler
Bios version 1.5
Win xpsp3 and dualboot Win7
Greets William

I send the modules back to the shop on RMA before I read the above suggestions. Hope you do not mind guys!
My opinion at the moment is that I have done a whole lot to make these modules work, more than you can expect from a customer. As far as this goes, I believe the modules should be able to run at standard settings (timings, voltage, etc) on any motherboard. I am not interested where the responsibility lies for the manufacturers of either hardware, but the whole thing seems to be lacking standardization (if at all possible with this kind of hardware). Maybe I am to narrow minded in this, but that’s the reason I send them back. Apart from being a hardware and computer enthusiast, I am also still a customer with certain expectations.
It looks like the shop agreed because, after receiving the modules via the RMA procedure they replied (translated from dutch):
Quote
Dear xxxx
We have tested your returned product(s). The results from our test indicate that the product is indeed faulty.
We will contact you as soon as possible to discuss further steps.
Since the receipt notification (of receiving the package I send) and the notification above were only 1 minute apart, I have reason to believe that they did not test the modules at all (or did not care what the result is).
I do wish to express my gratitude for your help, without your help I could not have come this far! Thanks!
@utgamer2004: I hope your RMA will be granted as well, my experience may be positive but this will depend on the shop or the manufacturer.

MSI P55-GD65, P55, Socket-1156, DDR3 won't run :-(

Just bought this mainboard and after connected the Intel Core? i7 Quad Processor i7-860, and Corsair Dominator DHX+ DDR3 1600MHz 4GB Ram I turned on the Cooler Master Silent Pro M700, 700W PSU and the Mainboard beeps 3 times and then runs as smooth as a cat with all 6 led's shining beautifully,the fan on the graphics card runs and everything looks fine but there,s no signal on the GraphicCard :-( Neither on the "DVI-I to VGA" adapter that followed the card (HIS Radeon HD 4890 1GB GDDR5) to the screen (Acer AL 1916w LCD) nor from the "DVD-I to HDMI" adapter to my samsung HDTV
I've allready tried:
-to clear CMos in a 'power off' state
-start the mainboard without the grapics card
-started it with only one ram innstalled
-used many different cables
Does anybody out there know how I can fix this?
What is the Beep.Code for 3 beeps???
I see 2 and 4 is used when you flash bios but what the hechk is 3 ?????
Please anybody........

Quote from: DaLoona on 03-October-09, 07:28:20
In my opinion a load of .....
Ive never heard that you MUST use 1 and 3, when just using 2 sticks.
That would be a real big design flaw, because when slot 1 fails, you can no longer use your board if what you state is true.
So every one with a broken no.1 and/or no.2 slot would have to buy a new board if it happens outside warranty period.
Furthermore, I have my mem running in slots 2 and 4 and no problems. Sure its a different board but the rules havent changed, last time I checked, but I could be wrong.
Second, a mate of mine has a P55 board, other manufacturer and he uses 2 and 4 with no problems.
For troubleshooting, best is to use the first slots, but if all is fine, you should be able to use any slot you like.
Please post link with that info, that you must use 1 and 3, because seeing is believing.
As to the problem, since it doesnt boot at all, try a memory set from QVL and try again. If that doesnt solve it, me thinks the board is DOA and best is to rma.
just take a look at the manual if you dont believe, you sure have enough to say, you surely have time to read the manual
the p55 range do not boot if the black slots are not populated, the manual does state dual channel has to be the black slots
check it yourself

Installed addl memory on P55-CD53 - Started smoking!!!

Has anyone run into this before.
Just built a new box (have built about 20 machines in the past) with i5, Gskill 2x2gb, 128gb SSD, Win7 64bit.
No overclocking yet, just some software install.
Then I added another Gskill 2x2gb into the other DIMM (1/3), no boot.
Then I mixed the ram around, no boot.
Then I went back to original DIMM config (4x2gb), no boot, I look down and it is seriously smoking.
I couldn't tell where the smoke was coming from since I was scrambling to unplug the power cord (which I did).
HELP.
(1) Does anyone know what the cause might be?
(2) What is salvagable? Is the mobo fried?
(3) What should be my next steps to iterate through the testing of good parts?
THANKS in advance!

Here are photos of the board. I put a yellow box around the burned out chip area behind the DIMMs.
Full pic of P55-CD53. Location of burn in upper left area (see yellow box)
Zoom in to area
Close up of area (kind of blurry)
Thanks, any help is appreciated. I guess I have to RMA???

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 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 - 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 GD-65, Core i5 wont boot

EDIT: Problem solved, motherboard is RMA.ed.
And now I have the same problem!! MSI P55 GD-65 bios 1.5, Core i5-750, 2x2 gb Kingston DDR3 1600mhz, Ati Radeon hd 5770v2, Corsair vx550w power. I started to boot up today, first time cpu phase led 4 did not light up, other lights blinked and fans turn on for 1sec. And thats go on and on, until I power off. Then other time: cpu phase led 6 + oc-button and +- -button lights blinked and fans turn on/off for 1sec -untill power off. What's going on.. Tryed everything re-seated cpu and so on. everything worked fine two weeks, until today.. sorry my bad english

Quote
Join the club.
What club?
Quote
There are more people with the same problem
If you say something like that, please provide links to the threads/posts that describe the "same problem". Similar symptoms are not necessarely a sign of the same problem. There can be different causes for seemingly identical symptoms. As long as we cannot be entirely sure that the cause causes for a system behaviour are identical it is not really helpful to simply assume that the problems are related.
Quote
find a (hardware) solution for us
How is that supposed to work? There are countless systems out there that show no sign of a hardware problem. In case particular boards became defective during operation (for whatever reason) they need to be RMAed and/or replaced.
Quote
Tryed everything re-seated cpu and so on.
Please make a list of the things you are referring to, when you say "everything". Have you tested the board outside the case (on a non-conducting surface) in barebone configuration (CPU, video card, one memory module in the proper slot, keyboard, power connectors) and cleared CMOS (with your PSU disconnected from A/C power) at any point?

P55-GD65 BSODs

The last two weeks I've experiencing fairly frequent (1 or 2 a day) BSODs. They are 4 or 5 different ones that happen.
I'm running the following equipment:
MSI P55-GD65
Win 7 64 bit
i7-860
Two sets of G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL7D-4GBRM
SAPPHIRE Vapor-X 100281VX-2SR Radeon HD 5870 1GB 256-bit GDDR5
APC BR1500LCD 1500VA 865 Watts 8 Outlets BACK-UPS RS
SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" (raid 5)
CORSAIR HX Series CMPSU-850HX 850W
LG Black 8X BD-ROM 16X DVD-ROM 40X CD-ROM SATA
Thermaltake Armor water cooled box.
This system has been running this configuration for about 3 months. Temps are around 19 at idle and high 40s under 100% load. When the BSODs started I first ran memtest86 and found no problems. I have a second rig and swapped out the following
Replaced CPU with second i7-860.
Replaced memory with two sets of CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Replaced Video card with SAPPHIRE 100215L Radeon HD 3870 512MB 256-bit GDDR4
Made sure that all the drivers were up to date and tried various versions of bios.
I'm still getting BSODs. Only thing the same are Motherboard, disks, OS and PSU. Since most BSODs are related to drivers or Memory problems I believe that it may be the mother board which is bad. Time to RMA the board?
Dan

Here are all the errors. The system was totally clean before 22 May.
22 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80003305410). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-25334-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
27 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d59e0, 0xfffffa80069d5ab0, 0x00000000040d0007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-29078-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x000000000000077a, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-30841-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000020, 0x0000000000000009, 0x0000000000000000, 0xfffff88004e0b7d7). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-26582-01.
28 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000d9f10, 0xf5500001bdf32886, 0xfffff8a0108b57b9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052810-26379-01.
29 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000010000006f, 0x0000000000000002, 0x0000000000000000, 0xfffff88001a368f9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-32479-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800374d5c8, 0xfffff8800374ce30, 0xfffff8000322f9e9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-36270-01.
30 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000000bf20e, 0x0000000000000003, 0x0000000000209de5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053010-26083-01.
31 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800b67a8d8, 0xfffff8800b67a140, 0xfffff880016c172f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-28158-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa800ca6c270, 0xfffffa800ca6c740, 0x00000000044d0005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-27924-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000403, 0xfffff68000103670, 0xa12000022385c867, 0xfffff6800002b840). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-29920-01.
1 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff680000243d8, 0x97b0000066e89867, 0xfffffa800c772810). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060110-29811-01.
2 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000020ad1d, 0x0000000000000003, 0x0000000000016a25). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-22682-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000031, 0xfffffa800d81fa50, 0xfffff8800820c000, 0xfffff8a00e4be67d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-23899-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff800035b8f1a, 0xfffff8800c0dde00, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-33805-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000001f6fe9, 0x0000000000000003, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-24835-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000352f90d, 0xfffff8800ad85080, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-30279-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xfffff800032da873, 0xfffff8800be47600, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-31574-01.
3 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffbbc0209541b, 0x0000000000000000, 0xfffff800032d543b, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-23337-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000203d8, 0xb310000169bc8886, 0xfffff6800004fca1). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-22838-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000124b4a, 0x0000000000000002, 0x0000000000123bb4). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-25272-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000172aeb, 0x0000000000000002, 0x00000000001721ea). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-31995-01.
4 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff88004bfb000, 0x0000000000000000, 0xfffff88004eb56a0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060410-33665-01.
5 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff88001274efa, 0xfffff88003b398b8, 0xfffff88003b39120). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25989-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80003309371, 0xfffff8800375b0e8, 0xfffff8800375a950). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25677-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x0000000000000c72, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-27315-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c6d3b30, 0xfffffa800c6d3e10, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-26176-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff6800001a270, 0xa2f0000223f1c886, 0xfffff8a00aec7c29). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-29343-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000005422f1, 0x0000000000000003, 0xccccccccccc35f20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-33228-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c0f9940, 0xfffffa800c0f9c20, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-34055-01.

P55-GD65 Voltage Discrepancy

Why is the voltage variance of this board so high? With low Vdroop enabled on a voltage of lets say 1.36 in the bios I get a 1.40v reading in CPU Z @ idle. This turns into 1.42 or more under load. Am I missing a setting that will keep it closer to what I set it at? This variance is rather ridiculous if you ask me. I have all the standard power saving features turned off before anyone asks.
Thanks!
My System:
Mobo: MSI P55-GD65
CPU: Intel i5 750
GPU: Ati 4870x2 2 GB
Mem: 2X 2 GB G.Skills Ripjaws DDR3 1600
SSD: OCZ Agility 60 GB
HD: 2x WD Black 500gb ea Raid 0
PSU: PC P&C Silencer 750

Songokussm the same issues I reported to support, they responded to me, that my MB is faulty and I should RMA ( did it twice, 4 month without MB ) I prove them otherwise, I had 3MB P55-GD65 with the same issues. Short speaking every MB with ERP=040 is faulty on engineering level Overvoltage like you described, problems with fans on sysfan1 and sysfan2, restore AC on power loss not working correctly and sometimes USB2 stops responding.
My conversation with MSI support ended when they statement that they can`t check if I`m correct because they don`t have MB with ERP=040, so the problem is .... gone I bet that with bios 1.9 in your case issue still occur but is`t less "visible".

P55-GD65 and Acrylux Wireless

I currently having trouble with a P55-GD65 and Acrylux Wireless KB009W-B keyboard with a particular port. I sent the keyboard for RMA already and I have a replacement. Before the keyboard RMA, I would have random shut down and sleep with this particular port along with intermittent connectivity. Now, I have repeated looped keystrokes and disconnects issues.
It's this port:
I'll try using another a port but what is different with this one? Underpowered?
BIOS 1.8
Windows 7 Pro x64
Drivers are current

Bad port, if you don't really need it it's probably not worth the cost for RMA shipping. Simply block it off with a piece of tape and let it be. Choice is yours whether to RMA or let it be. Could simply be what is called a 'cold solder joint' where the port terminals attach to MB.

P55 gd 65 RMA

Similar Messages

Maybe you are looking for