P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video

The Problem:
Temporary system freeze with audio stutter. The system recovers 30sec - 2min later.
Key presses made during freeze will execute after system recovers (ctrl+alt+delete for example)
Usually, but not always, I see an error message in the system tray and I do NOT experience bsod.
This happens seemingly at random from 3D accelerated applications, and web browsing. Games such as BF3 (moderate), WoW (seldom), Planetside 2 (frequently), Minecraft (seldom), Hawken (seldom), etc.
Also happens frequently in both Internet Explorer 9/10, Firefox, Chrome, and Steam store browser. Typically when watching steaming video (youtube, HULU, flow player, etc)
but Pandora audio streaming also seems to create the conditions where this happens.
Error Message:
"Display driver stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver 314.07 stopped
responding and has successfully recovered"
The problem also shows up in the Windows reliability history with the following data:
Source
Windows
Summary
Video hardware error
Date
‎3/‎6/‎2013 9:11 PM
Status
Not reported
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name:   LiveKernelEvent
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033
Files that help describe the problem
WD-20130306-2010.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode:   117
BCP1:   FFFFFA8011E0C4E0
BCP2:   FFFFF8800654A198
BCP3:   0000000000000000
BCP4:   0000000000000000
OS Version:   6_1_7601
Service Pack:   1_0
Product:   768_1
My System Hardware:
CPU: Intel i7 2600k @ 4.5ghz
Motherboard: MSI p67a-gd65 (B3 stepping)
Memory: G.SKILL Sniper 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
GPU: Originally MSI 6950 2GB. Replaced with EVGA 670 FTW 2GB.
PSU: CORSAIR HX Series HX850 850W
HDD: 3x Western Digital WD RE4 WD5003ABYX 500GB in Raid 0
OS: Windows 7 Home Premium SP1 with all updates
Case/Cooling: Silverstone Raven 2E with Thermalright silver arrow cpu heatsink
What I've tried:
Updated all motherboard drivers and bios (4.3) to current versions (no improvement)
Updated display drivers (in safe mode with driver sweeper. No improvement)
Updated Realtek Audio drivers for onboard sound (no improvement)
Updated Intel Rapid Storage drivers (no improvment)
Cleared CMOS and tested system at default settings with no overlock (no improvement)
Flashed 6950 back to 6950 stock bios and removed overclock (no improvement)
Replaced old 6950 with new GTX 670 (problem still occurs in the same exact way)
Tried GPU in 2nd PCIe slot. No improvement.
Checked GPU Temps. GTX 670 fan profile in EVGA Precision X set to keep temp below 70 degrees Celcius. Card maxes at 60 degrees under heavy gaming load.
Complete reformat of raid array with fresh install of Windows (4 different times) Seemed to help for a few days, then freezes came back
Ran OCCT and Prime 95 Torture tests separately for a few hours at stock and OC settings. System stable with core temps of high 50's overclocked, and low 40's stock.
Ran Memtest86 for 10 hours with zero errors.
Used digital multimeter to test 12v rail on PSU. Noted solid 12v reported. Didn't test other rails.
Unplugged PSU cables from motherboard and reattached firmly
Ran HD Tune and Data Life Guard Tools for error checking on hard disks. Zero errors found.
Disabled Windows Aero (no improvement)
Updated Adobe Flash Player to latest setting (no improvement)
Removed Adobe Flash Player (no improvement)
Turned off Adobe Flash hardware acceleration (no improvement)
*EDIT: Forgot that I also adjusted Nvidia driver profiles for apps that have frozen to include power preference to max performance
All of my hardware with the exception of the new 670 was purchased and configured back in February of 2011. This problem first occured in BF3 multiplayer sometime in early 2012,
and has gradually been happening more frequently. Web searches found many individuals with this error, but the solutions are all over the map, and I've tried just about everything that I've found.
I think I've narrowed the problem down to the motherboard, but I just can't find a clear answer or solution. Maybe it's the raid array? I really thought replacing the GPU would solve my trouble here
and I was...NOT happy when it happened again with the new 670 that I scored for $250 after amazon gift cards. I typically get kicked/disconnected during online game play when this happens and I'm ready to be done with it. I was hoping to fix the issue without needing to buy new hardware, but I don't see any other way at this point.
My patience runs thin. Please help!

Quote from: Froggy Gremlin on 11-March-13, 15:28:36
Might want to ask for the special archive to return the mainboard to pre-Ivy support UEFI/BIOS and then test again with everything set to auto/stock/default.
Already tested that before updating to 4.3. I started having the problem on 1.8, then 1.J0, then 4.3.
Quote from: Bernhard on 11-March-13, 15:30:29
Just a shot in the dark.
The length of time that your CPU has been running at the OC could have accelerated the eventual degradation.
Have you tested your CPU in another board or do you have access to a "known good" CPU to test in your system ?
I do not have another 1155 lga board to test the cpu in unfortunately, hence the CPU stress testing. Based upon previous experiences with multiple overclocked systems that I've run at much more aggressive overclocks, I don't believe I'm seeing a processor failure, though I can't rule out the possibility.
Quote from: xmad on 11-March-13, 23:26:01
Quite a few components can cause this.
Do you have a friend that could lend you a psu to test? A weak of failing PSU can often be the cause of something like this?
No I don't have another PSU to test. I did use a digital multimeter to test the 12v rail, as well as the motherboard contacts for testing voltage to the cpu and system They were all right in line with what I'm seeing reported in the bios. I did not test these contacts while the system was under load however, so I may need to do it again.

Similar Messages

MSI P67A GD65 System Freezes while Gaming

hey
i m facing system hangs/freezes while gaming. it is all along working fine but suddenly problem arrises outta nowhere. mostly happens in Metro Last Light Game. i did change multiple things like 2 different rams stick, Bios are 4.1v (at default), i tried 2 different GPUs like 290 and 580 but stilll facing same issue. dont know why.
if you can help on it this, it would be alot appreciated.
m PC
MSI p67a GD65
I5 2500K
8GB RAM
800w PSU

What is the actual power supply?
Follow this >>Posting Guide<<
Make sure you run latest BIOS.
PS: Intel ME driver is crucial, without it system won't work properly, and that's why it didn't freeze anymore. Same applies to GPUs: if you have 400W power supply and want to run 2-way SLI, it will be fine until you install drivers, which make the computer and graphic cards recognise how much power they have and so on

P67A-GD65 still freezing up

Well I've tried every suggestion and supposed fix (ram timings, etc.) for the feezing up problem to no avail. I still get a total system freeze at least once a day which then requires a manual restart of the PC. Kind of sucks.
Even with everything set to stock unmolested config with no overclocking it still occurs.
Any other ideas?

How is this a thread hijack? Did you have a bad day or something? All I did was comment that I was in the same boat and it seems like there's a LOT of people having this issue.
The topic is "Re: P67A-GD65 still freezing up"
And the original poster said
"Well I've tried every suggestion and supposed fix (ram timings, etc.) for the feezing up problem to no avail. I still get a total system freeze at least once a day which then requires a manual restart of the PC. Kind of sucks.
Even with everything set to stock unmolested config with no overclocking it still occurs.
Any other ideas?"
I've done the exact same, and have the exact same issue. And YES, the bios is updated to 1.B...that's what the memory is qualified with.
I can see if someone was to jump in and say "hey, and my hard drive isn't connecting" or "My rig is constantly rebooting" which is completely off topic. That's a thread hijack.
Never seen a forum that asks people to post identical topics. From what I've read in other related posts it doesn't seem to be a problem with the RAM, and there's a ton of people who are posting on newegg who have similar problems with all different makes of RAM and they get the same "please email me at xxxx@msi to help with your issue." "and include your serial number".
That tells me that MSI has a crap manufacturing run out there but is too lame to admit it so people can check if they have a defective board themselves and get it replaced quickly. Instead customers have to waste their time spending hours or days trying to fix something that is likely a flaw in the hardware that MSI won'd admit to in the open. Been there, done that. I work for a hardware manufacturer and our lame PM's and executives do the same crap when there's a screw up on a large scale. But it doesn't mean it's right.
Quality RAM (especially RAM that's verified) should run with the auto settings. And since the same memory works fine in an ASUS board where I could actually run a memtest on it successfully, tells me that MSI's sweeping things under the rug given the amount of problems customers are experiencing which are either continual reboots or lockups with no errors in the Windows logs.
As for this "user forum", it's not a user forum, this is a helpdesk. What moderator decided that the format is "one user posts and others only post to help that one user"? Or is this the only support MSI offers it's customers?
Thanks for the great help though!
Scott

P67A GD65 System build First startup goes into restart loop

I just build a p67a GD65 System i am an experienced system builder testing out on a cardboard surface after the system would not boot.
Using corsair Vengence ddr 3 ram
Coolmaster silent pro 800 W power supply
Hyper 212 plus cooler
2600k processor
After the continuous loop i tested power supplies swapped them and got the same problem
Then i got a clean cardboard box and started troubleshooting now the system, even barebone with the essential hardware only won't boot at all I do however see the green power light go on and OC genie light, light up when i press the power button but the system won't budge, I'm wondering if this is a bad processor or motherboard? I am leaning towards a bad mobo as these problems with this particular MSI board have been rampant.
Just to add none of the bios LED's light up.

Quote from: crxer on 16-September-11, 04:44:54
I just build a p67a GD65 System i am an experienced system builder testing out on a cardboard surface after the system would not boot.
After the continuous loop i tested power supplies swapped them and got the same problem
Then i got a clean cardboard box and started troubleshooting now the system, even barebone with the essential hardware only won't boot at all I do however see the green power light go on and OC genie light, light up when i press the power button but the system won't budge, I'm wondering if this is a bad processor or motherboard? I am leaning towards a bad mobo as these problems with this particular MSI board have been rampant.
Just to add none of the bios LED's light up.
I have a question crxer, does the OC Genie Light come on and stay on, or does it turn off? If it stays on then you have the OC Genie Button pushed in and you're trying to overclock the system right off the bat which you don't want to do, and that could be why the constant power cycling because of an OC failure.
Not that this is similar to your problem, but I had a Z68A-GD65(B3) which gave me nothing but problems with overclocking and the the dual bios feature. I would get the power on recycling a few times every time I tried any OC and reboot whether by using the OC Genie button or manual OC, but it would then eventually boot. Mine would also give me the Bios LED coming on in all the different configurations telling me the primary bios failed or secondary or both but I was always able to re-flash the primary bios and the board was never bricked. You're not having that problem thank goodness.
I am a very experienced builder and troubleshooter and tried everything to isolate the problem and make that Z68A board work, but to no avail, which is why I returned it to Newegg and replaced it with a MSI P67A-GD55(B3) shown in my signature, which is similar to your GD65 and it works perfectly with all the same components as I used on the Z68A-GD65(B3), and I have it manually OC'd it to 4.3 Ghz which is good enough for now. Good luck crxer.

P67a-gd65 random freezes

Hello,
I am having issues with my new system that i have built.
MSI P67a-gd65 (B3)
Corsair XMS3 1600
MSI Twin frozr GTX560 TI
Core i7 2600K
Windows 7 64 bit
My system will randomly lockup and i can't get it to work again unless i hard reset the machine. I have set the motherboard to optimized defaults and the memory is running at 1333. I also made sure my RAM timings and voltages were set to their defaults. I have not overclocked the system in any way. These lockups only occur when i am doing leisure things like surfing the web or checking my email. I can play any game i want for several hours on end without a lockup. I have updated my drivers from the MSI website and this also did not help.
Any help would be appreciated.
Thanks,
Anthony

Quote from: Ethylo on 30-March-11, 05:28:23
I had exact same issue with very close hardware ( only dif is 2500K instead of your 2600K, and B2 motherboard ) and after many test I finally found the solution by changing SPD memory from JEDEC4 to XMP-1600.
JEDEC4 was completely unstable , I got no BSOD but random freeze, especially when idling/low activity.
IMHO Corsair memories are definately not stable with JEDEC4.
Now 10 days with XMP SPD and fully stable !
Hello all,
I've been 24 hour crash free. I also setup my memory as listed above (thanks for that tip).
Thanks to everyone who replied with ideas.

MSI p67a-GD65 system randomly shutsdown

I'm completely heartbroken about my new build. Everything was running solid for about a month now and I have just started to experience random shutdowns. According to my BIOS, my 2600K is running at stock at around 55 C. I performed a stress test last night using prime95 and the system shut down as well, although speedfan and HWMonitor both only showed an increase from 40-50C to 60-70C. After it shuts down, the system is completely unresponsive and will not start back up until I unplug the system or turn off the power supply, after which it suddenly will start up again. In my opinion, that's an indicator of something as I thought it was completely dead.
I have NO idea what could possibly be causing this issue. It could be heat, it could be my power supply, it could be my motherboard. How do I narrow this down?
Here's my build:
G.SKILL Ripjaws X Series 8GB (2 x 4GB)
ADATA S599 AS599S-64GM-C 2.5" 64GB
Intel Core i7-2600K Sandy Bridge 3.4GHz
Seasonic SS-850HT 850W ATX12V v2.31,EPS12V
2x MSI R6970-2PM2D2GD5 Radeon HD 6970 2GB
MSI P67A-GD65 (B3) LGA 1155 Intel P67
COOLER MASTER Hyper 212 Plus

Quote
One video card should be at around 200W - 210 W, so 400W for video cards.
Make that 250W per card + 100 W for the processor, about 50A @12V.
Quote
I do have a 750W power supply.
You mentioned other figures in your component overview:
Quote
Seasonic SS-850HT 850W ATX12V v2.31,EPS12V
So, what kind of PSU do you have?
Quote
system is completely unresponsive and will not start back up until I unplug the system or turn off the power supply, after which it suddenly will start up again.
Sounds like a PSU problem then. Use a different one and/or test with one video card only.

P67A-GD65 mainboard incompatibility with Steel series XAI gaming mouse

Hallo,
As mentioned officially on SteelSeries web site http://faq.steelseries.com/questions/166/My+computer+gets+stuck+at+BIOS+stage+during+the+boot+for+a+few+minutes+when+the+Xai+is+connected. there's a problem with p67A-GD65 mainboard ( i don't know if other MSI P67A MB series have the same problem) and Steel-series XAI mouse about the pc gets stuck at BIOS stage during the boot for a few minutes when the Xai is connected. and personally i add that it's impossible in my p67a-gd65 (B3) to use this mouse for navigate in UEFI bios because it's moves only laterally.
I HOPE THAT MSI RELEASE VERY SOON A BIOS UPDATE ( lasted version 1.B have again this issue) FOR P67A-GD65 (B3) ( maybe other P67 models?) MAINBOARD THAT RESOLVE THIS VERY FASTIDIOUS PROBLEM.
Thanks.

Hello,
next time you start a topic, please skip the CAPS. CAPS are considered SCREAMING and that is rather impolite. In addition to that, this is a user-to-user forum and not MSI Technical Support. We do not make BIOS/UEFI Updates here and if you want to report anything that needs fixing, report it to Technical Support directly: http://support.msi.com/
That said, please note that the latest UEFI/BIOS release is not E7681IMS.1B0 [=v1.11] but actually E7681IMS.1C9 [=v1.12b9]. Various mouse related fixes have already been implemented. So, I suppose the best thing to do is probably to find out whether or not your problem has already been fixed:
E7681IMS.1B0 ---> E7681IMS.1C5
- Updating the latest USB module version 4.6.3_USB_08.10.10.
- Fix the Achiva 27'' LCD QH270-IPSBS compatibility issue.
- Fix AEXEA DDR3-1600MHz memory boot fail.
- Don't clear password when load defaults in BIOS Setup.
- Fix mouse click will hang 0Dh in some page when entering setup with user password.
- Fix the GT ratio show error issue when OC genie enable;
- Fix the Package C State limit item No Limit option value.
- When unplug any USB mouse and plug again then system will hang in UEFI bios
- When using the USB mouse and move and play around for 1 minute then the mouse cursor disappear.
- You will see 2 cursor under overclocking page using the below mouse:
---> Steelseries KINZU
---> Razer Copperhead RZ01-050100
---> Razer Copperhead RZ01-050200
---> RAZER DeathAdder RZ01-0015, Infrared Gaming Mouse
---> ROCCAT KONE ROC-11-200
- Fix USB Keyboard can't use under dos.
- Fine tune 2133Mhz memory stabilization.
- Fix the issue that using AEXEA DDR3-1600MHz 4GB 1.65V will have normal boot up but when running Memtest Deluxe 3.8, display hangs at "running fast write tests¡".
- Fix Post Screen show CPU speed 100x63=6300 MHz when "Adjust CPU Ratio in OS" is Enable.
If I was you, I would give E7681IMS.1C5 a try first and see what it does to your problem: https://forum-en.msi.com/index.php?topic=144655.msg1105581#msg1105581

P67A-GD65 (B3) -I'm also getting random freeze ups

I'm getting a complete freeze up at least once a day where I then have to do a manual re-boot.
It occurs only when I'm on my desktop about to click on an internet linked shortcut. The arrow juts freezes over the shortcut and the whole PC gets locked up. Very frustrating. Any ideas what would cause this?

Quote from: Mark on 02-April-11, 23:17:40
Have you overclocked your system?
Yes, but mildly following some of the online guides. Currently cpu is running nice at 4.5 Ghz, any higher and I get bsod.
Right now I'm running all voltages on "auto" to see if that makes any difference.
It doens't freeze up at any other time other than what I described above when I'm about to click a link on my desktop. Just wondering if the new IE 9 has anything to do with it. ?
All temps seem to be good: around 38c at idle and 58c during heavy gaming.
It's weird because it freezes just at the moment I hover over a shortcut icon and it gets highlighted, it doesn't even get to the point where I actually click the icon.

The system freezes a lot and dmesg gives an error in Nvidia drivers

I faced constant system freezing in Ubuntu under both Unity and Gnome shell. So I came to Arch. In Arch also im facing the same issue. I tried many things in these forums but nothing helped. Please help me. The system hangs constantly and the mouse barely moves. When I press ctrl+alt+f2 it takes several minutes to go to the terminal and then I can reboot. Please help. Here's the output of dmesg :
[ 1.826414] systemd[1]: Starting Login Prompts.
[ 1.826435] systemd[1]: Reached target Login Prompts.
[ 1.826449] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 1.826519] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 1.826533] systemd[1]: Starting Remote File Systems.
[ 1.826547] systemd[1]: Reached target Remote File Systems.
[ 1.826572] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 1.826666] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 1.826685] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 1.826720] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 1.826732] systemd[1]: Starting Paths.
[ 1.826744] systemd[1]: Reached target Paths.
[ 1.826755] systemd[1]: Starting Encrypted Volumes.
[ 1.826767] systemd[1]: Reached target Encrypted Volumes.
[ 1.826780] systemd[1]: Expecting device dev-disk-by\x2duuid-c11bdfb5\x2db15e\x2d473a\x2d8cf8\x2d020715616bde.device...
[ 1.826793] systemd[1]: Expecting device dev-disk-by\x2duuid-8ada8f05\x2d1853\x2d45c7\x2da302\x2d7d11869fd5bd.device...
[ 1.826805] systemd[1]: Expecting device dev-disk-by\x2duuid-E8D0\x2d38A9.device...
[ 1.826816] systemd[1]: Starting Root Slice.
[ 1.834477] systemd[1]: Created slice Root Slice.
[ 1.834493] systemd[1]: Starting User and Session Slice.
[ 1.834670] systemd[1]: Created slice User and Session Slice.
[ 1.834684] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 1.834712] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 1.834724] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 1.834752] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 1.834764] systemd[1]: Starting Delayed Shutdown Socket.
[ 1.834790] systemd[1]: Listening on Delayed Shutdown Socket.
[ 1.834805] systemd[1]: Starting udev Control Socket.
[ 1.834829] systemd[1]: Listening on udev Control Socket.
[ 1.834843] systemd[1]: Starting udev Kernel Socket.
[ 1.834868] systemd[1]: Listening on udev Kernel Socket.
[ 1.834880] systemd[1]: Starting LVM2 metadata daemon socket.
[ 1.834907] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 1.834921] systemd[1]: Starting Journal Socket.
[ 1.834967] systemd[1]: Listening on Journal Socket.
[ 1.834986] systemd[1]: Starting System Slice.
[ 1.835160] systemd[1]: Created slice System Slice.
[ 1.835179] systemd[1]: Started File System Check on Root Device.
[ 1.835191] systemd[1]: Starting system-systemd\x2dfsck.slice.
[ 1.835379] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 1.835393] systemd[1]: Mounting Temporary Directory...
[ 1.835993] systemd[1]: Starting system-getty.slice.
[ 1.836195] systemd[1]: Created slice system-getty.slice.
[ 1.837686] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 1.838280] systemd[1]: Starting udev Coldplug all Devices...
[ 1.838810] systemd[1]: Mounting Huge Pages File System...
[ 1.839349] systemd[1]: Mounting POSIX Message Queue File System...
[ 1.841338] systemd[1]: Starting Apply Kernel Variables...
[ 1.841909] systemd[1]: Starting Setup Virtual Console...
[ 1.842552] systemd[1]: Mounting Debug File System...
[ 1.844757] systemd[1]: Started Load Kernel Modules.
[ 1.844789] systemd[1]: Mounting Configuration File System...
[ 1.845225] systemd[1]: Mounted FUSE Control File System.
[ 1.846612] systemd[1]: Starting Set Up Additional Binary Formats...
[ 1.847351] systemd[1]: Starting Journal Service...
[ 1.848175] systemd[1]: Started Journal Service.
[ 1.861600] EXT4-fs (sda6): re-mounted. Opts: data=ordered
[ 1.865901] systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 141 (systemd-binfmt)
[ 1.919562] systemd-udevd[165]: starting version 212
[ 1.974653] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.981863] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[ 1.981873] ACPI: Power Button [PWRB]
[ 1.981971] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 1.981976] ACPI: Power Button [PWRF]
[ 1.983340] parport_pc 00:08: reported by Plug and Play ACPI
[ 1.983390] parport0: PC-style at 0x378, irq 5 [PCSPP]
[ 1.983777] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 1.986033] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.986096] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.990191] mei_me 0000:00:16.0: irq 43 for MSI/MSI-X
[ 1.990406] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.990820] acpi device:43: registered as cooling_device4
[ 1.990950] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[ 1.991137] [drm] Initialized drm 1.1.0 20060810
[ 1.993033] wmi: Mapper loaded
[ 2.014083] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
[ 2.014092] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014097] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014103] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014105] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014110] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014112] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 2.016081] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.016084] ACPI: Thermal Zone [TZ00] (28 C)
[ 2.016323] thermal LNXTHERM:01: registered as thermal_zone1
[ 2.016325] ACPI: Thermal Zone [TZ01] (30 C)
[ 2.016391] ACPI: Fan [FAN0] (off)
[ 2.016435] ACPI: Fan [FAN1] (off)
[ 2.016476] ACPI: Fan [FAN2] (off)
[ 2.016517] ACPI: Fan [FAN3] (off)
[ 2.016555] ACPI: Fan [FAN4] (off)
[ 2.027162] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20131218/utaddress-258)
[ 2.027171] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.027373] input: PC Speaker as /devices/platform/pcspkr/input/input6
[ 2.036735] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.036746] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 2.037012] r8169 0000:03:00.0: irq 44 for MSI/MSI-X
[ 2.037275] r8169 0000:03:00.0 eth0: RTL8168f/8111f at 0xffffc900059b6000, 60:a4:4c:3d:76:fa, XID 08000800 IRQ 44
[ 2.037279] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 2.041327] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 2.042605] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[ 2.042682] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 2.042728] hda_intel: Disabling MSI
[ 2.042735] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 2.047515] mousedev: PS/2 mouse device common for all mice
[ 2.058597] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059406] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059423] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059438] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059519] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 2.070989] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 2.071058] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 2.071112] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 2.071164] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 2.071216] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 2.071268] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 2.096085] kvm: disabled by bios
[ 2.113324] ppdev: user-space parallel port driver
[ 2.118467] iTCO_vendor_support: vendor-support=0
[ 2.119501] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 2.119535] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460)
[ 2.120228] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.122797] asus_wmi: ASUS WMI generic driver loaded
[ 2.123577] asus_wmi: Initialization: 0x0
[ 2.123593] asus_wmi: BIOS WMI version: 0.9
[ 2.123620] asus_wmi: SFUN value: 0x0
[ 2.123943] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input14
[ 2.124655] asus_wmi: Backlight controlled by ACPI video driver
[ 2.139754] systemd-udevd[172]: renamed network interface eth0 to enp3s0
[ 2.159402] Adding 4882428k swap on /dev/sdb6. Priority:-1 extents:1 across:4882428k FS
[ 2.173202] nvidia: module license 'NVIDIA' taints kernel.
[ 2.173206] Disabling lock debugging due to kernel taint
[ 2.179335] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 2.179471] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[ 2.179477] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 337.12 Fri Apr 4 14:51:15 PDT 2014
[ 2.292323] Switched to clocksource tsc
[ 2.369970] EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: data=ordered
[ 2.380040] systemd-journald[142]: Received request to flush runtime journal from PID 1
[ 2.398821] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[ 2.399044] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[ 2.399180] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[ 2.704632] r8169 0000:03:00.0 enp3s0: link down
[ 2.704667] r8169 0000:03:00.0 enp3s0: link down
[ 2.704684] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.889853] nvidia 0000:01:00.0: irq 46 for MSI/MSI-X
[ 3.436679] NVRM: Your system is not currently configured to drive a VGA console
[ 3.436683] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 3.436686] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 3.436688] NVRM: drivers including, but not limited to, vesafb, may result in
[ 3.436690] NVRM: corruption and stability problems, and is not supported.
[ 4.318649] fuse init (API version 7.22)
[ 5.160446] r8169 0000:03:00.0 enp3s0: link up
[ 5.160458] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 18.971615] NVRM: GPU at 0000:01:00: GPU-3840b413-5a51-9da2-923a-a4cbb4a5005e
[ 18.971628] NVRM: Xid (0000:01:00): 13, 0003 00000000 0000a097 00002410 00000030 00000000

ondoho wrote:
archlinux comes as a barebones system - i guess you installed some sort of desktop environment on top of it.
if you installed the same (unity or gnome shell) that will probably not solve your problem.
if you managed to set up an arch system with a gui, you should be able to provide us with more relevant information, so we can start troubleshooting.
off the top of my head (or hat?) i'd say your hardware can't keep up with a full-fledged desktop environment and you should choose something more lightweight. but that's just guessing.
I tried both gnome and unity. My GPU is Nvidia GT640 2GB DDR3, Motherboard Asus p8b75m, Cpu i3-2100. Ram 8 GB. 64GB SSD (Root is on it), 1 TB HDD (Home is on it). I don'tthink my system can't handle a full DE.

P67a-GD65 won't boot with over 12 GB RAM

Hello all,
I am running the P67a-GD65 with i5 2500k, GTX 570, 1T HD and 60Gb SSD. I had 16 GB (4/4Gb) of Hyper x 1600 MHz RAM installed and it was working for a while. Then the computer shut off in the middle of a game. I realized the video card fan was not working and swapped it out. However, with the 4 (4gb) Ram installed it would start up for a few seconds (fans, lights running) then shuts off...the cycle continues but never stays on nor long enough to reach the BIOS setup. I removed one 4gb Ram and its up and running. I was able to play BF3 and I have had no issues. Is there any reason why this happens? is it a setting in BIos that I need to fix or do I just need to swap out the mobo? I know its not the RAM because I exchanged them earlier today along with the Video Card. Any ideas? Thanks in advance

Quote
Any word on when an updated BIOS will be released to fix this issue?
No, you need to check this thread regularly https://forum-en.msi.com/index.php?topic=144655.700
At this point flash back to the BIOS that did work. Use the forum flasher >>Use the MSI HQ Forum USB flasher<<
and report your findings to MSI so that they can fix it and potentially release the BIOS that you are hoping for If everyone reports their findings then the chances are so much better to get a fix sooner rather than later.

My nano keeps freezing up when i use hold and the clickwheel won't respond?

it's showing up on itunes and i did the menu center button trick. i put my ipod on hold and shuffle during a parade and when i went to turn it off afterward, i took it off hold and the click wheel wasn't responsive, but music was still playing. so i tried the trick and it reset (or whatever it does to) it and got back to the main menu but my click wheel still isn't responsive. this isn't the first time that it has happened but then i did some stuff i don't even know and it worked but it completely wiped out my ipod's memory so i had to redo it, and i would really rather not again. it's a 4G 3rd Gen Nano if that helps, and itunes is recognizing it. how can i fix this, and is this a common problem?

I had the same issue. After searching around online I found out that you can try downloading another app (it can be any app) onto your ipod. After it finishes downloading see if your other apps open. You don't even have to keep the new app. Just see if your other ones work and you can delete the new one. That should work. If not, try to hard reset it. Here is another apple support link for steps on hard reseting it (http://support.apple.com/kb/HT1430).

We have an airport extreme wifi in house, but also want to set up a hardwired ethernet connection for gaming and streaming of netflix. The computer only sees one or the other not both at same time.

We have a new iMac 2.9ghz and are running an airport extreme set up in house with several express entenders. The problem is that our son is streaming netflix and doing on line gaming and hogging all the band width. Time Warner tech suggested a hard wired ethernet connection to computer base sattion next to computer so that it can have direct conenction to internet. After much fishing of wire the connection worked great, but the wifi connection for the house is gone. I unplugged the ethernet connection and everything is fine. I read the articles about adjusting network preferences, but the issue seems to be in the extreme not in the computer. the connection goes from cable modem to extreme, from extreme to house and to hard wired conenction to other computer. Do we need a splitter before the extreme?

No. Something else is going on.
Your son may be hogging all the bandwidth but your wireless network should never simply disappear. Moreover, if your son isn't doing anything the available bandwidth for other devices should remain unaffected.
I suspect that something is miswired, and from what you describe I suspect that link is between the Extreme and the "other computer".
The way to accomplish what you propose is
Modem > Ethernet cable to Extreme's WAN port
Extreme's LAN ports > wired Ethernet devices.
There should be nothing but an Ethernet cable linking an Extreme LAN port and any other wired device. If you run out of available LAN ports on the Extreme, you need to by an "Ethernet switch" - they are not expensive, but don't call it a "splitter" or you will only confuse yourself. The switch would be connected to one of the Extreme's LAN ports, and you would connect additional devices to it. You can also use one of your Expresses for that purpose, assuming it is the current generation model with two Ethernet ports.

Online video and slow internet

In my Lumia 520 online video is not playing and internet is slow

Remember that if online video requires Flash it's not going to play as Flash is not supported and in general has been discontinued for mobile platforms quite some time ago.
On internet what do you mean it's slow? What kind of connection are you getting? What letter do you see next to the signal (E, G, H or H+)?
Where are you and on which carrier?
Click on the blue Star Icon below if my advice has helped you or press the 'Accept As Solution' link if I solved your problem..

P67A-GD65 new system bios setting recommendations and sata connections

Hey all,
My old dual core HTPC (after many hours of use) finally gave up the ghost and moved on to the great PC grave yard . I have ordered all the new upgrade parts from Newegg and am looking for recommendations on what bios settings and setup procedures I should use on the initial bootup and Windows load. I'm not looking to overclock I just want a fast stable system for video decoding and playback. It's my understanding from the manual that SATA 1-2 are controlled by the Intel P67 chip and 7-8 are controlled by the Marvell chip but I am unsure of SATA 3-6. Can SATA 3-6 do raid 0? I want to use the Crucial SSD as my primary boot drive and the 2 WD drives on raid 0 as my secondary drive. SATA connection advice (which SATA ports) and Raid Bios setting would be helpful. Should I install the raid 0 drives after I have Windows 7 loaded on the SSD? Any other setup advice is appreciated.
Here is my setup.
Windows 7 64bit
Bach HTPC case
Ultra LSP 750Pro PSU
Intel i5-2500 3.3G CPU
MSI P67A-GD65 Motherboard
Sapphire HD5570 1G RT Video Card
Crucial CTFDDAC128MAG-1G1 SSD 6.0Gb/s SATAIII (Primary boot drive)
2 WD3200KS Hard Drives SATA 3.0Gb/s (Raid 0)
Lite-on 12X Blu-Ray Burner SATA
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600

Two questions answered. SATA 3-6 are controlled by the Intel P67 chip and do support Raid 0 but I still wonder if I should wait to install the drives until Windows has finished it's install.
SATAIII controller integrated in Intel® P67 & Marvell SE9128 chipsets
- Up to 6Gb/s transfer speed.
- Supports two SATAIII ports (SATA1~2) by P67 PCH
- Supports two SATAIII ports (SATA7~8) by Marvell SE9128
- SATA1~6 ports support RAID 0/1/5/10 mode by Intel P67 PCH
- SATA7~8 ports support RAID 0/1 mode by Marvell SE9128

Msi p67a-gd65 mouse and keyboard freeze - blinking caps lock.

As the title says, my mouse and keyboard suddenly froze while I was chatting on Skype and I noticed that my system was still running. In fact, my razer mouse light was also blinking. The caps lock had a sort of sequential blink, although I'm not sure.
Anyway, I had to use the power button to shut down the system and everything seems normal again. Does anyone know what would cause this? Is it a software issue or due to my board?
I'm running 64-bit Windows 7 Ultimate.

p67a-gd65 motherboard
Intel i7 2600K
2x MSI 6970 graphic cards
Seasonic SS-850HT 850W PSU
G.SKILL Ripjaws X Series 8GB (2 x 4GB)
ADATA S599 system hard drive
ADESSO keyboard and Razer Deathadder mouse
This was the first time this sort of thing has happened. I did have to replace (RMA) my PSU once before due to a random shut down issue but that was resolved. I'm really curious as to why this would happen and I'm hoping it's a software issue and not something related to the USB ports on the board.

P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video

Similar Messages

Maybe you are looking for