Problem: P67A-C43 - Random Hard lockups

Problem:  Random hard lockups with any power management features on (c-state, C1E, etc) and RAM set to X.M.P mode.  The system is not overclocked at all.
P67A-C43 V1.A (aka Version: V1.10), i5 2500K, Windows 7 Ultimate 64-bit
CORSAIR XMS 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) CMX8GX3M2A1600C9
CORSAIR CMPSU-750TX 750W ATX12V v2.2 SLI
ASUS HD6950
WD Caviar Black WD1002FAEX 1TB running in SATA 6.0
TST corp DVD/CD R-W w/LightScribe combo drive
Description:  Random hard lockups with any power management features on (c-state, C1E) and RAM set to X.M.P mode.  Also experiencing jittery mouse.  As suggested in another thread, turn off all power management features and manually set RAM to DDR1333 along with changing the voltage.  This seemed to have helped as I have had no lockups in two days and my mouse is significantly better.
I have read that there is not much difference running in XMP mode and I understand that but I would like to take advantage of the power management features and eventually overclock as well.  Please let me know if you need any more info from cpu-z etc.  Thanks in advance!

Your mem setting changes probably solved the problem. You need to enable your power saving features again to test them one by one. Leave EuP2013 disabled.

Similar Messages

  • P67A-C43 - Windows 7 64bit - Random BSOD

    Quote
    Machine Specs:
    P67A-C43 (B3) 1.14, i5 2500k
    Windows 7 Ultimate 64bit
    16GB (4x4GB) Corsair CMZ8GX3M2A1600C9
    Coolermaster GX650 (+12v~52a, +5v~25A, 3.3v~25A)
    Gigabyte GeForce GTX 460 1GB Super Overclock Edition
    Sata 1: Western Digital 750GB WDC WD5 00AACS-00D6B0 (Boot Drive)
    Sata 2: Seagate Barracuda Green 2TB ST2000DL003
    Sata 3: Seagate Barracuda Green 2TB ST2000DL003
    Sata 4: Seagate 1.5TB ST315003 41AS
    Sata 5: LG Blu-ray/HD-DVD Drive GGw-H20L
    Sata 6: LG DVD-Rom GH22NS70
    Hotway HUR1-SU3S2 USB3.0/eSATA Dual Bay
    1x Western Digital 750GB WDC WD5 00AACS-00D6B0
    1x Seagate 1.5TB ST315003 41AS
    Permanent/Regular programs running:
    AVG Anitu-Virus Free Edition 2012
    WinVNC (to connect with HippoRemote on my iphone)
    Itunes Helper and Apple Push (in startup items under msconfig)
    RazerHID Application (for my mouse)
    jdownloader - not a startup application. But is open most of the time even when I'm not downloading
    A few common BSOD messages I've had:
    STOP: 0x0000003B didn't get the string code
    STOP: 0x00000024 (0x00000000000c08a2....) didn't get rest of string
    STOP: 0x0000001A (0x0000000000041790, 0xFFFFFA8008CD2190, 0x000000000000FFFF, 0x0000000000000000) - Memory management... got this the last 2 times it crashed
    Although there have been a few others. This one seemed to be a one off while trying to install Windows Updates)
    STOP: 0x00000051   (0x0000000000000001, 0xFFFFF8A018295010, 0x0000000084919000, 0x0000000000000465) - Registry Error
    The crashes seem to be at random, but most often they occur while browsing the internet. For example I can be watching movies or tv shows through XBMC for hours and it runs perfect. Then I'll load up an internet browser and it will crash not long after.
    Although the last crash I had was while watching a TV Show in XBMC. My computer had not been on very long, and it was only 10 minutes into the show. Although I was running jdownloader in the background. I also have AVG 2012 Free Edition running permanently.
    Things I've tried that didn't work:
    I've disabled the USB3.0 drives and the problem still occured. I thought they might have been the issue as they cause my computer to freeze on boot or in the BIOS (or boot EXTREMELY slowly) when it's switched on. Although the second I switch it off everything continues as normal. Would like to fix this issue too, but compared to the BSOD it's really a nothing issue.
    I've updated my video card, USB 3.0 and Ethernet drivers.
    I've upped the voltage on the RAM (not by much).
    I've fiddled with some of the Turbo etc. settings for CPU.
    I updated to the most recent BIOS.
    I switched web browsers. Originally I had Chrome and each crash seemed to happen while using it, so I went to Firefox and it didn't change at all.
    I switched my RAM around (Blue slots to black and vice-versa)
    Currently trying:
    I've removed 2 sticks of RAM. When/if it crashes again I'll swap in the other two sticks. Unfortunately it can run for ages before it crashes, so it's hard to tell whether an attempted fix has worked until it crashes and I know for certain that it hasn't.
    Im pretty sure RAM is the most likely cause of the problem. But the PC was running fine up until the last 3 weeks or so. I got a BSOD a few weeks back which seemed to be a one off. Then a week or so later another one. Now it's happening daily.. sometimes 3 or 4 times. I would google the codes back when they happened and was lead toward different possibilities.. which is why I tried Chrome, Drivers and unplugging USB devices. Although obviously RAM seemed to be the most common possibility.

    When did you start to see this crashing start?
    Try running >>Memtest86<< on the RAM individually.
    Try to uninstall jdownloader.

  • P67A-C43 usb/freeze problem

    For quite a long time now I have had problems with the machine freezing and requiring a reboot.  It seems to happen at random, perhaps once a day.  Its just happened again, this time when I plugged in a usb hard to one of the ports.  I've installed the latest intel series 6 chipset driver.  I could be wrong but it seems to me that the underlying problem is usb related. 
    Some years ago I shared this problem on this forum when the freezes were happening multiple times per day.  The forum solution (thanks Svet yet again)  was to increase the voltage of my Corsair Ram to 1.65v - sounds high but that's what the manufacturer specifies.  The freezes still occurred but much less frequently.
    I really would like to see this problem disappear and would appreciate any help.

    I've run one iteration of Memtest so far which showed no errors.  I'll run a 5 iteration one overnight (takes a long time).
    I decided to run a a HW Monitor report, a truncated version is below.  This shows several things that worry me.
    1.   The +12v rail on the psu shows only 9.06 volts which looks too low. The psu is nearly 6 years old and could be failing
    2.   Temperature 1 on the Fintek F71889A chip seems high (max 78degC).  I'm not sure what this is how to address this if it is a problem.
    CPUID HWMonitor Report
    HWMonitor version   1.2.6.0
    Monitoring
    Mainboard Model      P67A-C43 (MS-7673) (0x000003EA - 0x52735B20)
    LPCIO
    LPCIO Vendor      Fintek
    LPCIO Model      F71889A
    LPCIO Vendor ID      0x1934
    LPCIO Chip ID      0x1005
    Config Mode I/O address   0x4E
    Config Mode LDN      0x4
    Config Mode registers   
    Hardware Monitors
    Hardware monitor   Fintek F71889A
       Voltage 0   3.36 Volts [0xD2] (+3.3V)
       Voltage 1   1.22 Volts [0x99] (CPU VCORE)
       Voltage 2   1.86 Volts [0x74] (VIN2)
       Voltage 3   1.38 Volts [0x75] (VIN3)
       Voltage 4   5.72 Volts [0x88] (+5V)
       Voltage 5   9.06 Volts [0x67] (+12V)
       Voltage 6   2.08 Volts [0x82] (VIN6)
       Voltage 7   3.22 Volts [0xC9] (VSB3V)
       Voltage 8   3.33 Volts [0xD0] (VBAT)
       Temperature 0   45°C (113°F) [0x2D] (TMPIN0)
       Temperature 1   71°C (159°F) [0x47] (TMPIN1)  Max 78°C
       Temperature 2   33°C (91°F) [0x21] (TMPIN2)
       Fan 0      813 RPM [0x735] (FANIN0)
       Fan 2      792 RPM [0x765] (FANIN2)
       Fan PWM 0   35 pc [0x59] (CPU)
       Fan PWM 1   65 pc [0xA6] (System Fan 1)
       Fan PWM 2   65 pc [0xA6] (System Fan 2)
    Hardware monitor   NVIDIA NVAPI
       Temperature 0   67°C (152°F) [0x43] (TMPIN0)
    Processors
    Number of processors      1
    Number of threads      4
    Processors Information
    Processor 1         ID = 0
       Number of cores      4 (max 8)
       Number of threads   4 (max 16)
       Name         Intel Core i5 2500K
       Codename      Sandy Bridge
       Specification      Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
       Package (platform ID)   Socket 1155 LGA (0x1)
       CPUID         6.A.7
       Extended CPUID      6.2A
       Core Stepping      D2
       Technology      32 nm
       TDP Limit      95.0 Watts
       Tjmax         98.0 °C
       Core Speed      3292.1 MHz
       Multiplier x Bus Speed   33.0 x 99.8 MHz
       Stock frequency      3300 MHz
       Instructions sets   MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x, AES, AVX
       L1 Data cache      4 x 32 KBytes, 8-way set associative, 64-byte line size
       L1 Instruction cache   4 x 32 KBytes, 8-way set associative, 64-byte line size
       L2 cache      4 x 256 KBytes, 8-way set associative, 64-byte line size
       L3 cache      6 MBytes, 12-way set associative, 64-byte line size
       FID/VID Control      yes
       Turbo Mode      supported, enabled
       Max non-turbo ratio   33x
       Max turbo ratio      60x
       Max efficiency ratio   16x
       Min Power      60 Watts
       O/C bins      unlimited
       Ratio 1 core      60x
       Ratio 2 cores      60x
       Ratio 3 cores      60x
       Ratio 4 cores      60x
       TSC         3292.4 MHz
       APERF         3691.5 MHz
       MPERF         3292.6 MHz
    Storage
    Drive   0
       Device Path      \\?\ide#diskwdc_wd20ezrx-00dc0b0____________________80.00a80#5&16c0005a&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
       Type         Fixed
       Name         WDC WD20EZRX-00DC0B0
       Capacity      1863.0 GB
       SMART Support      Yes
    Drive   1
       Device Path      \\?\usbstor#disk&ven_seagate&prod_desktop&rev_0130#2ghn0vp5____&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
       Type         Fixed
       Name         Seagate Desktop
       Capacity      1863.0 GB
       SMART Support      Yes
    Drive   2
       Device Path      \\?\usbstor#disk&ven_wd&prod_my_book_1130&rev_1016#5743415a4131393739373138&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
       Type         Fixed
       Name         WD My Book 1130
       Capacity      1863.0 GB
       SMART Support      Yes
    USB Devices
    USB Device         Generic USB Hub, class=0x09, subclass=0x00, vendor=0x8087, product=0x0024
    USB Device         USB Input Device, class=0x00, subclass=0x00, vendor=0x045E, product=0x00CB
    USB Device         CanoScan 8800F, class=0x00, subclass=0x00, vendor=0x04A9, product=0x1901
    USB Device         USB Mass Storage Device, class=0x00, subclass=0x00, vendor=0x0BC2, product=0x3300
    USB Device         Generic USB Hub, class=0x09, subclass=0x00, vendor=0x8087, product=0x0024
    USB Device         Generic USB Hub, class=0x09, subclass=0x00, vendor=0x05E3, product=0x0605
    USB Device         USB Mass Storage Device, class=0x00, subclass=0x00, vendor=0x1058, product=0x1130
    Graphic APIs
    API            NVIDIA I/O
    API            NVIDIA NVAPI
    Display Adapters
    Display adapter 0   
       Name         NVIDIA GeForce 7300 GS
       Board Manufacturer   GIGABYTE Technology
       Revision      A3
       Codename      G72
       Technology      90 nm
       PCI device      bus 1 (0x1), device 0 (0x0), function 0 (0x0)
       Vendor ID      0x10DE (0x1458)
       Model ID      0x01DF (0x3413)
    [ ERROR: SPECIFIED ATTACHMENT MISSING ]

  • P67A-G65 (b3) - Hard Lock Problem

    I recently built a new machine (specs at the bottom of the post), and am experiencing random hard locks that I can't figure out. The locks generally happen 30-60min after booting up the computer, and seem to happen more often when idle than when in use, but I can't confirm that. I have tried turning off XMS and other overclocking on my memory, as well as doing a new install of Windows, but it still seems to be happening. I have updated all my drivers, and my BIOS is v1.8, so it's up to date with the current stable release version. I still need to try individually testing my memory sticks, but if anyone has any other suggestions that might help, they would be very appreciated.
    Here's the hardware I'm using:
    MSI P67-GD65(B3)
    Intel Core i7 2600
    8GB (2x4) Corsair XMS3 Memory (CMX8GX3M2A1600C9)
    Corsair 750TX 750w PSU
    ASUS PCE-N13 PCI Express Wireless Adapter
    Western Digital Caviar Blue 1TB HDD
    MSI N560GTX-TI Twin Frozr II/OC GeForce GTX 560 Ti (Fermi) 1GB 256-bit GDDR5 Video Card
    Windows 7 64bit

    I'm not picking on these specific posts but there is something that needs to be said about the tendency to look for problems in the motherboard or other components when things go wrong.  It's really important to understand that a lockup, random reboot, BSOD, etc. is simply what happens when any of a thousand things go wrong with a computer build.  It's similar to a car that won't start - it could be a failed electrical system, mechanical system or it could just be out of gas.  Because of this, it doesn't help to search for a common thread, you need to look at each problem individually to understand the root cause.
    It's also important to understand why computers from Dell, HP or any other manufacturer doesn't have the same problems you see when you purchase your own parts to build a system.  These companies have research groups who are constantly working with different motherboards, RAM, video cards and other components to determine which ones are most reliable and more importantly, which ones work best together.  When developing a new model, these people carefully select from the parts they have tested to design the new model including all the different video card options, drive options, RAM, etc.  In addition, these systems are always configured to the safest specifications with no overclocking or anything else that could potentially cause a flood of support calls. Then each of these systems are built and tested using a long burn-in period with multiple copies of each system to make sure any potential issues are found and fixed.  All of this is done before a new computer is sold to the public by one of these companies.
    When you build your own system, you must perform these tasks yourself or your chances of success are very low.  You can't just buy components based on what is popular or appears to be the best in class.  You must carefully crosscheck every component to make sure they will (probably) work together.  Finally, you need a systematic approach for assembling and testing your system one step at a time so if a problem occurs you will know what has probably caused it.  
    Just like the companies that sell full computer systems, all reputable computer component companies are also experts at designing and testing the parts they sell.  They know that anytime a component has a problem there is lots of negative publicity, recalls and other consequences they all want to avoid (e.g. the recent Intel problems).  So when you have built a computer that is randomly failing in some way, don't start by looking for problems with the parts you bought.  This will only distract you from finding the real cause because 99.99% of all problems with new computer builds are caused by assembly errors or misconfiguration.  
    There are lots of people on this forum and others willing to help with build problems but you need to start with the assumption that something is wrong with your assembly or configuration and follow the posting guide.  A simple step-by-step troubleshooting approach will save a lot of time in the long run.  
    - D

  • P67A-GD65 Hard Lockups

    I recently built a Sandy Bridge system and I am having random sudden hard locks.  I will be browsing the net or playing a game and then...everything freezes up suddenly and I cannot do anything, like I'm stuck in a screen shot.  I am forced to manually hit the restart button.  Sometimes it will happen twice in an hour and sometimes it wont happen for a day.  I have updated BIOS to v1.7, turned on and off turbo mode, manually slightly increased my vcore, increased base clock to 101 (MHz), turned on and off power saving settings, tried sata 6 and sata 3 ports, ran MemTest, newest drivers from MSI site.  Also from day 1 the OC genie never worked, whenever I would try it it would freeze up at the windows loading screen.  I have been able to overclock manually and get it up to 4.7GHz and then got a blue screen while running 3dMark, but that was just for a short time while testing and have since reverted back to stock speeds and it still randomly hard locks.  My temps are always fine 32-50 C.  This is basically a core upgrade with some reused parts from last setup (which was rock solid always).
    Hardware:
    MSI P67A-GD65 (Flashed to V1.7)
    Intel i7-2600k
    COOLER MASTER Hyper N 520
    EVGA GTX 570
    4Gigs Patriot DDR3-1066 CAS 7-7-7-20 (from last pc)
    Zalman ZM850-HP PSU (from last pc)
    Western Digital Caviar Blue WD6400AAKS HD (from last pc)
    Windows 7 Pro 64bit
    Anyone have any ideas about how I could isolate what exactly the issue is? Bad mobo maybe? The lack of a stable system is really killing me.  Making this post from my laptop  

    I am having the same problems as you. Have not done all those tests that you have done tho. I have not overclocked or changed anything, its all default settings for me. I still run the default BIOS version. Was thinking of updating now but it seems like MSI has removed the v1.7 update.
    Normally it happens like this. Im in a game and suddenly all gets frozen. Then I am disconnected from the game server (I run online games) and then the game hangs. Still I can alt-tab in to windows. Then I try to open task manager to see whats going on but it never shows... computer starts running slowly. Mouse and keyboard input work for 4 seconds at a time, and then stops working for 4 seconds, then works for 4 seconds... after a while the computer comes to a complete halt.
    I have run chkdsk on my disks. I have checked all temperatures, all ok. I have a Corsair 850W which gives power to my:
    MSI P67A-GD65
    Intel i7-2600k
    ASUS GTX 570
    Noctua U-14
    8 GB Corsair memory CAS 9
    Intel SSD 80GB Gen2
    WD 2TB Storagedisk
    2xseagate 500GB disks in RAID1
    2xsamsung 1TB disks in RAID1.
    Currently I have removed all disks from port 2-5 in order to see if that is the issue, considering Intels pressrelease.

  • P67a-c43 boot problem

    hello i tryed to built my new computer. have a p67a-c43 motherboard, i5 2400 cpu , ati hd2400 grafikcard, 2*2 gb corsair xms3 memoris, and a i-cute 600w psu.
    my problem is the pc is working fine whit 1 pice of memory , but doesent want to boot whit dual, no beep ,nothing on the screen.

    With one stick of RAM, first thing I would try is to raise DRAM V. manually in the BIOS. If default is 1.472V's, I would recommend a bump to 1.521V's in BIOS DRAM V. setting. This should set it to about 1.504V's, shut down & add the second stick & give it a try.
    Quote
    but doesent want to boot whit dual
    Have you also tested the second stick in the primary slot to make sure it is ok?

  • MSI P67a-c43 rev B3 temperature problem?

    Hi, I've had my MSI P67a-c43 rev b3 since the spring of '11 and I've been very happy with it, haven't had any real problems with it at all actually.
    Recently, I did however install a program to monitor the heat of my parts after a odd bluescreen, and I was frightened about what I found.
    These temperatures were read after a intense gaming session (full load I guess)
    SpeedFan: Temp2: 172 celsius
    CPUID HWMonitor: TMPIN1: 127 celsius
    None of the other temperatures are hotter than 40-50 celsius
    After some googling around I found other users with the same MoBo having this issue, and it seems that the chipset which is located near the PCI-E port gets covered by the graphics card and either gets extremely hot or has a faulty temperature sensor.
    As I said I've been using this rig since spring '11 and I haven't had any problems, I have only checked the temperatures the last few days however, so it's either been this hot for every day for almost two years or something bad has happened recently.
    Wouldn't my MoBo have melted if a metal piece on it was over 100 degrees celsius, or atleast showed some issues?
    Setup:
    MSI P67a-c43 rev b3
    Intel i5-2500k 3,3 GHz
    Gigabyte GeForce GTX 460 1GB OC
    Corsair Vengeance 2x4096 1600 MHz CL9
    Win7 64-bit
    I haven't overclocked or otherwise tampered with anything but installed these RAM's since I originally bought it.
    So is there a heat problem or is there a malfunctioning sensor?

    Try taking the door off and pointing a fan at the mainboard and see if the temp changes.

  • MSI P67A-C43 problems

    Hey everyone. I recently bought a MSI P67A-C43 using a Intel i5 2500K and everything has been working great until recently. I realized it has a post beep every time you turn it on, which is the short beeps followed by a 5th beep and everything starts running after that. Well for some reason recently my computer turns on and the post beeps go 4 times and then it takes a good 3 minutes or more for the 5th beep to go through and everything starts up. I'm not sure what is going on with it and I'm hoping that the mother board doesn't have an issue.
    The System has in it:
    - MSI P67A-C43 (B3) Mainboard
     - Intel Core i5-2500K
     - COOLER MASTER Hyper 212 Plus HSF
     - XFX Black Edition P1-750B-CAG9 750W ATX12V v2.2 / ESP12V v2.91 SLI Ready CrossFire Ready 80 PLUS SILVER PSU
     - ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner
     - Western Digital Caviar Black WD1002FAEX 1TB 7200 RPM SATA 6.0Gb/s 3.5" HDD
     - AZZA Solano 1000 Black/Black Japanese SECC Steel/Metal mesh in front ATX Full Tower
     - EVGA GeForce GTX 560 Ti FPB 1024 MB GDDR5 PCI-Express 2.0 Graphics Card
     - Turtle Beach Montego DDL 7.1 Sound card
    Any idea what could be wrong?

    I'm not sure what it is, I could deal with it but I'm afraid one of these times I will go turn the computer on and it won't start up windows at all.
    Anyone have any advice on what might be going on?

  • Powermac 7500 Hard Lockups

    Since it runs OS 9, I see no way to read "logs" if there are any to begin with, unlike OS X (which I may run one day on this machine).
    First, It's a heavily G4 upgraded machine, with it's original 100MHz CPU removed and running a 1GHz G4 now. I've tried many operating systems, from 8.1 to OS 9.2.2 (yes, forced into it). I even tried removing the Radeon 7000 in it, AND the G4, and it'll still do this hard lockup.
    Now, when I say hard lockup, mouse cursor won't even move. I had a PowerMac 5500 at one time, that did this very same thing, and under the same random occurrence. I since got rid of that computer cause I got tired of the crashes. But with this 7500, I don't want to get rid of it, because I see it has potential to be a nice computer.
    I recorded this Youtube video of it, and it ran fine throughout the video just fine as you can see (with the G4 but onboard video), but what you didn't see, was after the video, when just going on AIM and sending someone a file, it hard locked, yet under the tougher situation of playing internet video via flash, it didn't lockup and did quite well actually. So it's not a stress situation, and no, it doesn't overheat.
    http://www.youtube.com/watch?v=4Vm13xQ02tk
    Any ideas as to why it can be doing this, and how I can tell? Can it be bad memory? Is there any memory testing apps? If I boot with extensions disabled, it will NEVER lock up, even with the G4.

    I asked because my ZIF carrier card (in an 8600) had that option. I settled on 48-49 MHz for stability. Are you using an internal SCSI hard drive or have you installed an ATA controller card for the boot drive? It could be a hard drive problem. I once had intermittent system hangs in a beige G3 and after testing the hard drive, determined that there was irreparable damage somewhere within the first 2 GBs. I partitioned the drive, with the first partition sized at 2 GBs. I deselected the "mount on startup" option for that partition with Drive Setup, so the problem area of the drive is no longer used/visible.

  • Hard lockup, no logs, how to debug?

    So I'm having some hard crashes lately. The only way to resolve is to hold the power button to shut down the machine. Nothing gets written to /var/log and the screen freezes. So, is it possible to find out what happens? Crashes don't happen on other OSes on the same machine so I don't think it's a hardware problem.

    I've been experiencing hard lockups since late last year. After loosing a significant amount of data I reinstalled Arch64, KDE and upgraded all packages but the freezing is still there. The thing is, Ubuntu runs very stable on the same machine and hardware.
    I ran a memtest without errors and at the time of the last crash there was no unusual behavior, high temps or ram usage. And obviously no logs. I just went with the linux-lts kernel because Ubuntu runs a 3.0 kernel, but it froze up again despite the change. It freezes randomly without activities like if I leave it on overnight it will crash at 3AM or during the day when I am away it will crash at 11AM or sometimes 5PM.
    It used to freeze while playing audio or video but this seems to be solved. The last time it locked up while I was actually sitting here was when I opened Chromium and although I rarely use it the system has crash maybe 3 times while opening Chromium. At least twice it locked up while loading archlinux.org in Opera and occasionally just clicking the mouse.
    One of the threads I've been folowing is here. I falsely narrowed it down to the kernel because many users have Gnome and/or ATI cards whereas I have KDE and nvidia, although I may try the nouveau driver just to be able to eliminate that. Another alternative is to install the 32-bit Arch unless someone can report lockups with it.

  • P67a-c43 boot loop after bios update

    Last night, I attempted to update the bios on my P67A-C43 (B3) board using the version 5.1 bios. After the BIOS installed, it restarted and came up with the "all settings were reset to default values. press f1 to run setup. press f2 to continue" I hit f2 and my system keeps resetting in an infinite boot loop. I was able to reset the BIOS using the reset button on the back of the board to get back to the bios prompt, but pressing either f1 or f2 puts it back into the boot loop. Any help would be appreciated.

    Quote from: ScunnyUK on 01-February-11, 16:08:59
    Hi,
    The blue screens started after a clean Bios flash to the 18b10 bios then eventually it stopped working complety (just doing the start up cycle over and over)
     I had tried reseting cmos and it doesnt make a difference, the motherboard will not post , boot , start up at all so default settings cant be set (although reseting cmos would set to default anyway)
     Each time the board goes through the start up cycle (i.e. upon pressing start button the board will start up with fans spinning for a second then shut down, start up again with fans spinning for a second then shut down, continuasly repeating until main power is removed) I have used a multimeter to measure the voltage read points on the board and they show that there is no vcore being suplied to the cpu but all other points show the voltage is being supplied to those componants, so imo that is where the problem lies and I would sugest that the other ppl who are having this issue to also try  measuring the voltage read points and see if the same thing is happening on thier boards .
     If others are getting the same results (no vcore) then the msi techs should be informed of this issue..(imo)
    1.8b10 still is a beta bios. I got random bluescreens with that one also at some point a blinking bios led. So I flashed back from secondary bios (using the first option (change disable in enable)in "security" in the EFI shell to allow flashing from secondary bios), blinking bios led now stopped, Then I flashed with 1.7, no issues sofar cpu now running stable at 4.5Ghz (already 2 days).

  • MSI P67A-C43 (B3) Trouble

    I have the MSI P67A-C43 (B3) motherboard with a Core i5 2500K, a 600w OCZ PSU, 1TB WD Black Caviar HDD, Radeon HD 4670, and some Corsair Vengeance RAM.
    I just put it together and it turns on, but nothing comes on to my screen. All of the fans start, the LEDs on the MB light up saying the CPU is on, CPU fan spins, and GPU fan spins. I don't know what's wrong with it, I switched the RAM around and also tried only using one stick and it gave me different errors, so I assume the RAM works. The speaker/buzzer made noises that went like this: mid mid high low low low low low
    MB:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16813130571
    CPU:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16819115072
    GPU:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16814161315
    PSU:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16817341017
    HDD:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16822136533
    RAM:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16820145348

    Quote
    i unplugged everything and then reassembled, testing along the way
    Have you tested the board outside the case on a non-conducting surface in barebone configuration? Yes or no?  If the answer is "no", then that is what you should do next/first.  Get rid of the case.  It is not needed for troubleshooting.
    Also, have you >>Cleares CMOS<<?
    Quote
    I've done as many tests as I know how to do.
    What did you test exactly? Please make a list that tells us your precise steps!
    Quote
    CPU doesn't even seems to have pins.
    Did you check the socket pins? Yes or no?  Check the CPU's contact pads for areas of poor, missing or double imprints from the board's socket pins!
    When you board is on a non-conducting surface (get rid of the case!) you can pretty much rule out short circuit problems.  In barebone configuration, the following parts should be involved:
    - board
    - CPU + cooler/heatsink
    - one stick of RAM
    - video card
    - PSU with all power connectors connected (--> 4/8 Pin +12V CPU, 24 Pin ATX, 6/8 Pin +12v PCI-E [video card])
    - keyboard
    Everything else should be unplugged completely!  Your video shows a hard drive/SATA device connected to the board.  Unplug that.  It is not needed for troubleshooting.
    Your problem could be caused by any of the components mentioned above, not necessarely the mainboard.
    Quote
    CPU+MB+PSU=shutdown right away
    CPU+MB+PSU+HDD=shutdown right away
    CPU+MB+PSU+HDD+RAM=BEEP CODE, same one as the above one
    When the board was inside the case when you did that, then the test is useless because a short circuit problem could still be at the bottom of this. Also, you need to check your socket pins and the contact pads. This could be a plain and simple pin-contact problem, caused by broken pins or a heatsink that is fastened to tight.

  • P67A-C43 (B3) minor weirdness.

    Hey all,
    Got a system here that's solid as a rock, except for a few small issues:
    1) Very occasionally, system refuses to POST on cold boot (hangs at status code A3 or B3).  I've had this about 3 times in the past 3 months, and a hard reboot always fixes it.  Could be high Vdroop on one of the rails, but I've never tested it.
    2) Recently (just noticed it about 2 days ago), USB keyboard/mouse aren't recognized for about 30 seconds after boot to Windows 7 login screen, can't toggle Numlock/Capslock either during this time.  I noticed that this only started to happen when I plugged the hub into one of the USB 3 ports, so it might just be the Renesas USB3 driver taking its time.  Weirdly, keyboard and mouse both work in getting to/using UEFI BIOS, regardless of where the hub is plugged in.
    Specs:
    2500K OC to 3.8GHz (stepping down to 3.6, 3.4, 3.2), Hyper212+ HSF
    P67A-C43 B3 fw. 1.B
    Corsair 8GB DDR3-1333 RAM
    EVGA GTX 560 Ti
    Crucial C300 128GB SSD (fw. upgraded to 0007 from 0006)
    Samsung Spinpoint F3 1TB HDD
    Bigfoot Killer 2100 NIC (latest fw)
    HTO Stryker 7.1 sound card
    Rosewill RCR-IC002 card reader
    Antec Earthwatts EA500 PSU
    Raidmax Smilodon case
    Rosewill RHUB-300 USB 2.0 Hub
    Microsoft Natural Ergonomic Keyboard 4000 w/IntelliType 5, driver ver. 8.20.409.0
    Logitech MX518 mouse w/SetPoint 6.32.7, driver ver. 5.33.14
    Trivial problems to be sure, but is there anything I can do about them?  I just put together this system, and it doesn't seem right for it to have even minor problems right off the bat.

    Quote
    Status code at time of hang was B4.
    Quote
    Rosewill RHUB-300 USB 2.0 Hub
    USB or USB compatibility problem of some kind.

  • MSI P67A-C43 (B3) USB not working but theres a twist! Help!

     :lol_anim:I Have built a new rig with the MSI P67A-C43 (B3) Motherboard, 16GB DDR3 PC3-10600 1333MHz Memory (4GB x 4), Intel Core i5-2500K 3.3GHz 6M LGA1155 Processor, 550 Watt 80 PLUS Bronze Power Supply,24x DVDRW, 3.5" Internal Card Reader with 2 USB ports,    500GB 7200RPM 3.5" SATA Hard Drive(which i plan on upgrading just didnt want to waste money on the shitty HD they had.....
    So down to the nitty gritty  . My computer is running Windows 7 64 Bit, i have downloaded all of the updates and all of the Chip-set drivers, Bios, etc... i ran a system registry tool to clean up any errors in my registry and i have ALL of my drivers up to date.
    I have my USB mouse and keyboard that connect fine and are recognized by my computer, sometimes they stop working and start back up within seconds but windows does display any type of error or disconnection "this may have been fixed due to the registry cleaner i used i haven't had any hiccups yet" so i have my USB mouse and USB keyboard working fine and dandy now i think. got a new headset and the windows finds the USB Headset and it works Perfectly fine. BUT and this is where my whole frustration comes out. Whenever i connect my I-Pod Touch, I-Pod Nano, My Cell phone to copy files to from my SD Card, or my External My Passport drive Windows says "USB Device was not recognized" notification and in the Device manager it shows the one device with a yellow exclamation point and says "Unknown Device" I have tried to uninstall the USB hubs and reinstalled them perfectly restarted windows, still non of the devices work. i have tried making sure that windows tries not to turn off the device to save power, when i say i have tried almost everything i mean everything that is related with USB Device not Recognized. So i do not know what to do now, i have contacted the Manufacturer and they don't know squat about it or what could be causing it. the only thing i can think of is there is some hardware maybe that is not compatible i do hear some beeps when i start up i will have to come back and update how many beeps" i saw another post that it means the motherboard is trying to tell me something maybe this could be the issue. but i have tried every single usb port and non of them Recognize the device but when i plus in my mouse and keyboard in diff ports they still work so i am a bit confused. my last step is to return the computer to the manufacturer for a replacement or repair w/e i do not want to do this cause this should be working. my friend has almost the exact same MB and equipment and his works fine so i am getting a little frustrated with the issue Someone Pls Help me out. And yes i have tried turning off the computer, unplugging it and pressing the power button, and waiting like 1 Hour etc and still nothing. Drivers are Up-to-Date and Mother board bios and chip-set drivers are Up-to-Date as well. I hope someone knows or has an answer to help me out!

    Yes the Bios is Up-to-Date and they are not plugged into the Blue USB 3.0 ports(x2). oh and forgot to mention already did a clean install again of Windows 7 64bit and still nothing.  Im also wondering if the power supply is enough?? maybe?

  • Random hard freezing issues, Windows 8 64-bit on Macbook Pro (Late 2008)

    Hi,
    I recently upgraded to OS X 10.8.3 and got a hold on copy of Windows 8 64-bit. As I'm running on my old trustworthy 15 inch Macbook Pro (Late 2008), my hardware is officially unsupported. Over the years I've had XP, Vista, Win7 32-bit and 64-bit running running on the same machine, and thought I'd give Win8 a chance.
    To be able to install Win8 on my unsupported hardware, I tricked the Bootcamp assistant that I was going to install Win7, and after the reboot and start of the Win7 installation, I exited the installer, rebooted, switched DVD to Win8 and did the installation from there. So far so good. For installing the Bootcamp drivers, I followed the instructions in https://discussions.apple.com/thread/4894920?tstart=90.
    Now, the machine runs just fine with Windows 8, and I've installed some basic third party applications (Firefox, Spotify, Steam). However, I get completely random hard freezes on the machine (sound looping, no other activity whatsoever) during normal use. These can occur 20 minutes after start, or 3-4 hours in. The freezing behavior is very much similar to how my model can behave under overheating conditions (which mostly have occured in past Windows versions while gaming), however overheating doesn't seem to be the issue here (based on simple palpation ).
    Have anyone experienced a similar problem, or know something about it? My current idea is that some weird things are going on with the Bootcamp drivers, so unless anyone comes up with a suggestion I might try doing a rollback to the point before I installed the drivers to see what I can make of it.
    Thanks!

    Had a few similar short system freezes, after installing Windows 8 x64 on 13” MacBook Pro Mid-2010 with BootCamp 5.0.5033.
    There is a suggestion that DisableDynamicTick may fix the problem: https://discussions.apple.com/message/21565295#21565295. There were similar topics at Microsoft forums: 1, 2, 3. It was said “that this will likely reduce system battery life, so it should be undone when you update your Windows build or if it doesn't resolve your issue”, and that “this problem is resolved in the release versions of Windows 8”.
    Another possibility is that there is indeed a buggy driver, within BootCamp 5.0.5033, or a 3rd party, like a wireless network driver in the following case http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/system-fr eeze-randomly-after-installing-windows-8/49488183-26cf-4389-af21-a85dc366c99a?pa ge=2#LastReply.
    The problem has been noticeable on my MacBook, but not annoying enough yet to spend time troubleshooting. If you find a robust solution, using the links above or other method, it would be interesting to know.
    HTH

Maybe you are looking for