Boot issue with Z77A-GD65

I have a Z77A-GD65 board with 16GB of DDR3 RAM (4x4GB DIMMS) and an I5 Ivy Bridge CPU, Samsung 830 128GB SSD and 2x 4TB HDD's.
Last night my system was working perfectly. Today it won't boot into an OS.
When I would power up the system this morning, it started went through the Intel Matrix RAID BIOS fine then did a few status codes in the bottom right and ended up on A2 as the current code and sat there forever... I let it set for 15 minutes about no change.
I pulled the HDD's and SSD off first, same code
I pulled the USB and ethernet now the code changed to D0 still nothing, just hangs there.
I switched the BIOS switch to the second one, same result.
I pulled the BIOS battery and power and let it sit for a while, plugged it back in and put the battery back in... same result..
What's going on? I'm not sure where to go nor do I know the exact meaning of the codes given

Quote from: Svet on 15-September-14, 23:25:51
what is your bios version?
The BIOS that went nuts was A.B0, I did get it to boot though, just not with that BIOS...
I pulled all the cards, all the memory, anything plugged in HDD/SDD etc.. only thing left was onboard DVI and keyboard... cleared the CMOS again with the back button and it went into a never ending reboot loop.... switched it to the second bios via the switch on the motherboard, cleared the CMOS again, and bingo it booted... I think that BIOS 1 is corrupt... not sure what caused it, haven't done any updates or anything since A.B0 came out. And haven't made any hardware changes in that time either... worked great until this morning turned it on and boom It was stuck at A2 on the BIOS startup.
My question now is, how do I reflash BIOS 1? I read somewhere before I think that I have to do a multi bios update, but not sure how to go about doing that.

Similar Messages

Boot Loop Issues - MSI Z77A-GD65 - Solved

Picked myself up an MSI Z77A-GD65 as well as some Kingston 2x 4GB RAM sticks with a i5 2500k.
After getting everything installed, it just boot-loops on me showing me no boot menu, with a debug code of 55.
If I take out one of the RAM sticks and just use the #2 slot, it boots fine (but after starting windows, it flashes some blue screen and it boots again. I'm thinking that's only because I haven't installed any drivers and still have the old drivers from my motherboard. Yes/No?).
But as soon as I put the second stick in, it will not boot (swapped sticks and it boots fine with one stick). I've tried 1/3 and 2/4 and the only slot that seems to work is #2 (#4 slot won't boot with one stick in it). Tried each stick in each slot. 1/2 work, but 3/4 will not
I'm guessing this isn't a RAM issue but a MOBO issue? I sense an RMA in my future....

Quote from: XFM on 24-December-12, 08:29:56
Can you take a good quality, in focus hi-rez picture of the socket and post it so we can see what you are talking about?
I would if I could. Best way I can describe it is that the pins are all kind of bent at an angle (imagine an L shape, but upside down). Now take the bottom of the L (where it's small and turns) and kind of bend that facing the ceiling. It's kind of like that...
Quote from: Froggy Gremlin on 24-December-12, 08:30:08
Why is this thread in the Intel duo/quad section?
What are the amps on the PSU +12V rail(s)? And how old is it? Suggest to keep just the one RAM stick in the primary DIMM slot and do a fresh OS install with the Mode set to AHCI. BTW, what is the OS? 32 or 64 bit?
Good question. I think I was very tired/annoyed when I made this, and I guess I didn't look properly. If any mods can move it, or need me to take it down, I can.
PSU - http://www.newegg.com/Product/Product.aspx?Item=N82E16817703005
I don't have a problem doing a fresh install, but would like to make sure it's nothing else before hand. If I do a fresh install, and I still have to RMA the board, I would have to do another one to put all my old stuff back in, and I wouldn't really have a PC until the new board came (I mean I could still use it, but would have to re-install stuff and it seems like a bit of a pain if I don't *have to).
64-bit OS

Serious boot issues with Powerbook G3 (Wallstreet II, OS 9.2.2)

Hello,
I have major issues with a Powerbook Wallstreet II I got recently. When it's finally running, it works just as well as Wallstreet Powerbooks usually do, no errors, no crashing, smooth performance, everything fine.
But booting it up is, to put it mildy, a bloody pain. First off, it does not power up, when it's only connected to batteries. I have two of them, both working fine for several hours when put in after bootup, but no matter if I place one or both of them in any bays, nothing happens when pressing or holding the power button (apart from screen flickering and speaker crackling). I'm always forced to connect the power adapter, which immediatly (without pressing the power button) causes the power LED to light and the cooling fan insanely spins up for a mere couple of split seconds until everything wents silent again.
Having reached this point, I can disconnect the power supply (if at least one battery is in) and usually hear a nice "BONG" when pressing the power button once again. Thereafter, nothing happens for a oppressive 30 seconds, then, the screen finally lits and shows the Mac OS 9.2.x splash screen on monochrome background. Sadly, this is already the end of most of my first boot up tries, because at this point, I usually get told by a dialogbox that a bus error has just happened. The box also has a nice "Reboot" button, which I cannot click as the trackpad hangs as well.
Pressing ShiftFn+CrtlPower works here in about one out of three time, so in most cases, I have to go through the same procedure. Pull out power sources, give a shot via PSU, have it iddling for 30 secs. In most cases, this second try lets me pass splash screen, loader, yes, it even lets me see the desktop, the taskbar, the HDD icon and... pouf. Success is so close but no, it has to suddenly drop into sleep mode and
a short press on power proves the apprehension true, that it won't be easy to wake it up again. Hrmph. But I don't give that easily. So pulling everthing out for the second time, connect PSU for the third time and look there, it fully boots.
Three tries to successfully boot is about average at first try series. Afterwards, it seems to be "warmed up" and things get easier. I made a log recently with 5 test series, made at very frequent intervals:
Series 1:
1. Bootup: Bus Failure (Hard reboot fails) (bays empty)
2. Bootup: Sleep Mode (bays empty)
3. Bootup: Sleep Mode (bays empty)
4. Bootup: Sleep Mode (both batteries)
5. Bootup: Bus Failure (Hard reboot successful)(both batteries)
6. Bootup: Success (left battery, right bay empty)
Series 2:
1. Bootup: Success(left battery, right bay empty)
Series 3:
1. Bootup: Bus Failure (!!!) (left battery, right bay empty)
2. Bootup: Success (bays empty)
Series 4:
1. Bootup Success (left bay empty, right battery)
Series 5:
1. Bootup Success (both batteries)
Thanks in advance for any helpful suggestions.

jpl,
Thank you for continuative support.
If you plan on buying a 256MB memory module, the Wallstreet requires
a 256 specifically made for it (and the early iMac
and Lombard). Modules 128MB and smaller can be
generic if they meet the Wallstreet's specs.
Thanks for this information.
You might find it useful to disassemble the 'book to the PMU, carefully remove/reseat the PMU card, then test.
Well, to be honest, I don't have the time to perform this very labour-intensive work. However, I pulled out the large PMU connector (the one that can be reached by lifting the keyboard) and reseated it, without any results. Shouldn't that suffice? Or is there another connection that could need maintenance?
Regarding sleep: There is no display position sensor, only a simple magnet in the right display bezel approximately 4" from the bottom...you can stick a paperclip to it. When the display closes, it triggers a sleep switch located next to the delete key in the side rail.
Ah, okay.
According to Apple, if the powerbook will not run on battery, it could be the charge card or PMU board or power supply card or logic board. However, your 'book apparently runs on battery once started via power adapter.
Actually, it does not allow me to power up, if I attach the adapter right after an unsuccessful try to operate from battery. Even if I remove the batteries (after adapter connection).
It's like it is "crashed" before it's even running. Which means, I have to pull all power sources to be able to perform the resuscitating power up via adaptor.
A normal power manager reset on the Wallstreet is this:
1. If the computer is on, turn it off.
2. Simultaneously press Shift-Fn (function)-Ctrl >(control)-Power.
3. Wait 5 seconds.
4. Press the Power button to restart the PowerBook >computer.
A successful reset will briefly flash the sleep light plus >spin up the fan for a second. If a reset does not solve the >startup and sleep issues, then you will have to look >elsewhere.
I can see the sleep LED and I do hear the fan, however, this didn't help in most cases. After perfoming this action (in a freeze situation), I usually only got rattling noises out of the speakers or screen flashes when trying to power up.
Be sure the powerbook only freezes when closing the display to sleep it.
Well, I noticed it sometimes also freezes when left idle directly after start up (and power save is activated). Later, it comes right back again.
- Is the sleep light blinking before you open the display?
Yes.
- When the display is opened, does the sleep light continue to blink? (It should.)
Yes.
- When you press the power button, do you hear a 'buzz' or some similar noise? If you do, you may have another issue to explore.
No. I usually only hear speaker noise when trying to power up from battery. But oddly enough, the lenght of the sleep light blinks changes when power button is hold down in "frozen sleep".
I would also go to the System Folder > Preferences folder and drag the Energy Saver Preferences to the Trash, close all windows, then restart...a new preference file will be created on restart. You can reset the Energy Saver to your like, then test sleep.
Done.
-Does sleep/wake always work when NOT closing the display? Try this after resetting the power manager and trashing the pref file mentioned below.
If I initiate sleep, yes. If it suspends automatically, well, usually. But not always (see above).

PXE Boot issues with Latitude E5450.

Our SCCM 2012 is SP1 and it does not support Windows 8.1.
I had tried to capture the OS through network but there were issues connecting and smsts.log indicated share not reachable. Hence, I captured the OS in the D:\ of the machine.
Now after creating TS and deploying the OSD machine boots to PXE and starts to download boot image files and instantly restarts to Windows. I have performed below steps..
1. Got the network drivers and updated the boot image with the same
2. Checked the BIOS settings and time is updated correctly
3. Used an old boot image that was used to capture another model laptop with Windows 8.1 and still same issue.
Getting the below errors in smsts.log
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
Failed to download pxe variable file. Code(0x00000001)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
PxeGetPxeData failed with 0x80004005 TSPxe
3/26/2015 6:29:17 PM 792 (0x0318)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1416)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2623)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)
TSPxe 3/26/2015 6:29:17 PM
792 (0x0318)
Exiting with return code 0x80004005 TSPxe
3/26/2015 6:29:17 PM 792 (0x0318)
Any advise would be helpful..

Our issue with the Latitude E5450 ended up being due to a boot image that wasn't being properly updated and/or pointed to during the task sequence set up. There also seemed to be some strangeness with the replication because the WIM file listed on
the server file system was showing as, for example, boot.XXXX.XXXX.wim (double name). As a result, when we would update the boot image with the correct NIC driver, the system was still pointing to, for example, boot.XXXX.wim.
We ended up re-creating the boot image from scratch using our base boot.wim image and using the 19.2.0.0/12.12.50.4 driver version for the I218-LM NIC, found at the download link below. If you recreate the boot image, don't forget to re-add all of the
NIC drivers, redistribute the boot image, and change which boot image your Task Sequence will be pointing to.
http://www (dot) dell (dot) com/support/article/us/en/19/SLN294178/EN

PXE boot issues with Windows Deployment Services

I am trying to move from FOG to WDS after running in to serious UEFI issues with FOG.Right now I'm stuck with machines PXE booting to WDS server.I keep getting the message ProxyDHCP service didn't reply to request on port 4011.WDS and DHCP are on different servers. There are plenty of IP addresses available, and they are on the same subnet. I did originally configure DHCP option 60, but deleted that option after troubleshooting. I have configured Windows Firewall to allow inbound and outbound connections on UDP ports 67-69 and 4011 on both DHCP server and WDS server. I have also tried just using IP address in DHCP option 66. As for option 67, I don't even know the right bootfile name to use at this point, figured I'd tackle that if I ever get past this error message.I have tried restarting the WDS service several times, as well as the...
This topic first appeared in the Spiceworks Community

After working with many companies in their Office 365 Change Management and End User Adoption strategies, we’ve found that companies who make it fun have very high success rates. So what can you to make it fun?Host an Office 365 Showcase.We’ve helped companies produceOffice 365 Showcases, which have a lively, trade show flair. Kiosks are set up in a cafeteria, meeting room or other convenient location. Hosting each kiosk is a departmental Office 365 Power User who demonstrates a unique aspect of the software to everyone who stops by.Read more about how to make Office 365 Change Management and End User Adoption Fun

Weird gray screen/freeze boot issue with 2008 Macbook Pro

Early 2008 MBP. Gray boot screen with apple logo and spinning gear freezes. Now for the odd part. In the background I can hear iChat log in, and I can see the associated account as available via Bonjour so I know that behidn the scenes, the laptop is indeed logging in and launching the desktop. I also managed to remote in and can see the desktop normally. The screen remains frozen.
I was able to initially get it working by resetting PRAM and NVRAM but that is no longer working either. Also tried an SMC reset.
Can't boot from CD or recovery partition (same result..gray Apple Logo boot screen freeze).
Booting it in target disc mode allows full access to the HD without issue. HD was checked (no issues) as well as permissions the one time I did get a desktop.
Any ideas?

Was able to pull this info from the kernel log.
Feb 8 21:02:38 Username kernel[0]: NVDA: rmStart failed
Feb 8 21:02:38 Username kernel[0]: NVDA,Display-B: Not usable
Any suggestions? It appears that the video is not initializing properly. Not sure at this point if it's a hardware failure or not. I tried reinstalling when I managed to get to recovery console, but that doesn't seem to have helped either. That only overlayed the files on the partition though. Perhaps I should just try a complete reformat?

New P7N SLI Platinum Boot Issue with PS/2 Keyboard [Solved but RAID problem now]

This issue taken me back !!!! Never thought I might face issue with a PS/2 Keyboard.
Here it is.. I just assembled my new system...
P7N SLI Platinum Motherboard
E8400 CPU
EVGA 256-P2-N751-TR GeForce 8600 GT Video Card
Creative Soundblaster Audio Card
So, before I boot, I connected good old PS/2 Keyboard. The POST Screen comes up that says Press DEL to enter BIOS Setup... but then, it reboots.. indefinitely... I have no idea why it does that. However, if I boot the PC with no PS/2 Keyboard connected, POST screen comes up and that's it.. (no reboot). So, you see, I cannot proceed further in anyway.... I cannot go beyond POST without a keyboard, but then with the keyboard it reboots indefinitely... kinda catch 22 situation
Any suggestion / ideas that anyone can offer here???

Hello Folks... it took long time to "solve the issue that had to begin with"....
I purchased a cheapo Celeron processor to get into the BIOS and update it... but it didn't even work... I couldn't boot at all. So, I called MSI and they asked me to RMA it. They replaced my MOBO with the latest BIOS - which was good news
So, now, I'm able to boot - good news...
Now, this is an upgrade for me.... from my previous MOBO. My boot drive was RAIDed (RAID 0). So, now, I will have to RAID my drives again and run Win XP repair. I was able to RAID my drives and all good... now, I went into Windows installation and did F6 to install NVIDIA Raid.... but, here is my problem, when the prompt asks me to input the floppy drive, and when I did it.... it re-prompts me to put the floppy drive again... I see that the floppy drive is read... but, for some reason it doesn't detect the files in there properly.... I downloaded nVidia C72+MCP55 SATA RAID / AHCI Driver (For floppy driver) for windows xp 32-bit and copied the sataraid folder contents into the floppy. Now, here I am stuck again....
Anybody experienced this problem?

Boot issues with Win98. Safe Mode Boot only. Not all drives detected...

Hello guys! This is a great source of information and I've learned a TON browsing this place (on company time, hehe), but I've hit a road block that I can't maneuver around.
System Config
Neo K8T Neo Fisr mobo
Athlon64 3200+ CPU
1 Gig Kingston RAM
Ti4200 64 MB video card
520 Watt Antec Power Supply (after getting schooled by Bas's great posts on the importance of PSUs, I found out my lame-o 350 watt (!!!!) PSU, errr, ain't gonna quite cut it.)
Problem:
Windows98 won't boot all the way to normal mode. It only boots to safe mode. Apparently a driver issue?
Symptoms/Clues:
- Only detects my Western Digital harddrive (and only after some finegling)
- Wierdness with my 1.44 3.5" floppy (A:) drive. At first the BIOS would tell me the A: drive was there, regardless of whether it was plugged in. Then I plugged in the A: drive and Win98 in safe mode couldn't read from it. Right now, I don't have my A: drive connected and it's not in my Boot Order sequence (hard drive only for now).
- BIOS doesn't detect my new CD-ROM (SONY) drive at all. Note, this is a brand new drive that was NOT on my old system.
- I disabled the S.ATA controller. (This was confusing because there's an option to disable some SATA thing under an "Integrated Peripherals" menu. However, there's another setting to disable s SATA thing under a PCI Controller's menu. Seemed vague to me,, but then it's been a while since I've done this sort of thing.)
- I cleared the CMOS earlier because of wierdness were the system would hang on bootup and would ask me about starting a "Flash Recovery" process, upon which it would just sit there ( I left it running overnight once).
Call for help
Unfortunately I have no boot floppies, so I was hoping this was something I could fix without one, perhaps by changing some BIOS settings. Maybe it's a RealTek Boot Agent thing?
Any help is appreciated!
BamaBoy

Im running win 98se with no real problems, and its doing so well that I still dont even feel like trying anything else..........
I'd say RE-clear your c-mos , using the jumper, and unplugging the power for 5 seconds..... then reset your bios settings.......Also, maybe just reinstall the via 4-in1 chipset drivers...... I remember fiddling with some bios setttings before, like the acpi by os or by bios etc.... that helped.....but its been awhile......The great thing about 98 is that you CAN tweak so much.......
You can reinstall over itself also, which can help redetect the hardware, yyou should always have the 98 files on the hard drive so you dont need the floppy or cd...... So many things you can try....... Resolve yourself to trying as many as possible , its fun when you get it right........... My prob. is that I never remember what I did to fix stuff heheheheh.......good luck
ps, the "flash recovery" thingy has to do with the realtek ethernet lan thingy....which you should disable in its bios.....I forgot how to get to it, I think F11 or something like that while it shows when you are booting....Then it will still ask when you boot, but wwont hang......

Sudden booting issues with K8TNeo

MSI K8T Neo
AMD Athlon 64 3000+
ATI 9200 All-In-WOnder AGP
512 GB DDR 400MHz Ram
450W Powersupply (new)
Maxtor SATA HD
DVD burner
I'm having a bit of trouble getting my system to boot. I've pretty well narrowed it down to the motherboard based on some tests. I'm not the biggest techie in the world so please bare with me here.
Basically durring normal operation, the computer had suddenly turned off. Not the first time its happened either. I attempted to start the computer back up, nothing.
I popped the top and took a closer look at what was going on. The CPU fan moves a bit when I first try to power on the system, but the system never really powers up. I began disconnecting components and trying alternatives to see if anything where causing a problem.
So I ended up with a barebones PC, with pretty well nothing in it, and nothing boots. I was beginning to suspect power problems. Then I noticed the wierdest thing. If the 4 pin 12v connector is NOT connected to the motherboard, the computer will power on. It won't post and the JLED diagnostics pannel shows 4 red, but thats understandable behavior because the 12v isn't in. If I reconnect the 12v, and try to power on, its dead in the water and doesn't budge. Infact I need to unplug the powersupply and reconnect it up to even give it another try. Thinking it might be the powersupply, I swapped it out with a known-working 400w one, but it did exactly the same thing.
So I'm a bit at a loss exactly where the problem lies. Its odd that I need to disconnect and reconnect the powersupply if I try to turn the computer on when the 12v connector is connected, and its even wierder that the motherboard will only power on if the 12v is unplugged (even with any configuration of hardware, including bare with just CPU and fan).
So I'm lost here. Is the board itself damaged, and needs to be replaced? CPU or power problems perhaps? I would be very happy if anyone would be able to give me a hand. Thanks.

I am also having this exact same issue.
At work we use these boards for all our office systems, all the office systems have the same specs and it seems as though after about 12 months or so of perfect running we seem to get this issue all of a sudden.
As soon as I disconnect the 12v connector everything in the system powers fine.
I've tried using a PSU with a higher rated rail 12v > 26a and it hasnt made a difference.
I currently have about 7 boards sitting here with the same thing (K8N Neo3)
Any suggestions?

Very wierd SSD Issue with Z87 GD65 Gaming

Hey guys,
I got a gd65 gaming and couple of days ago i started having this problem. basically when i turn my pc on it says insert boot media and just keep saying that no matter how many times i reset. however when it is booting up, if i go to bios and save it (without changing anything) the pc obviously restarts and boots fine into windows. any ideas how can i solve this?
PC specs
i7 4770k (stock)
Mushkin chronos 120Gb SSD
GD65 Gaming Motherboard
Crucial Blastix Tactical 4 X 4 GB (1866 MHZ)
Seagate Barracuda 500GB (not a system drive)
Western Digital Green 3TB (not a system drive)
GTX 560 ti

Problem is most likely your Sandforce based SSD and problematic compatibility with Z87:
https://forum-en.msi.com/index.php?topic=170135.0

Boot issues with x79a-gd45 (8d) and n680gtx 4gd5/0c no bios splash screen

I have system
with
x79a-gd45 (8d) and
n680gtx 4gd5/0c
16gb ram out of 4 modules
vertex3 ssd
win7 64 en updated everything to the latest version.
during boot i get b2 b4 and 92 messages but not bios splash screen.
When doing a test with an old ati card the system shows splah screen all is fine.
I have 4 systems like this all behaving the same
any ideas

Hello I updated the bios, was not neccesarry but problems remains.
cleared the cmos several times.
I have to inform you that i'm building 4 similar systems all suffering from the same problem.
During boot there is a black boot screen not splash screen. and on the top left a cursor and in the bottom right b2 b4 and 92 messages.
When I install and old ati x1050pro all is ok during boot I see the splash screen and i'm able to enter the bios.
boot time approx 20 sec.
when running the system with the msi n680gtx boot times are back to 2 min and a long period with only the black boot screen and the bios codes.
As suggested I tested the card in a other system. Motherboard is asus. And voila I get a splash screen.
STRANGE THING IS THAT THIS SCREEN IS NOT RESISED BUT IS I GUESS 800 X 600 AND CENTERED IN THE SCREEN.
Also after several reboots I could not get a screen filled splash screen.
Can this be a video card bios issue ?
grt michel
detals of my system are
===================================================
GPU Caps Viewer v1.17.2
===================================================
===================================[ System / CPU ]
- CPU Name: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
- CPU Core Speed: 3600 MHz
- CPU logical cores: 8
- Family: 6 - Model: 13 - Stepping: 7
- Physical Memory Size: 16384 MB
- Operating System: Windows 7 64-bit build 7601 [Service Pack 1]
- PhysX Version: 9120604
===================================[ Graphics Adapters / GPUs ]
- Current Display Mode: 1280x1024 @ 75 Hz - 32 bpp
- Num GPUs: 1
- GPU 1
- Name: NVIDIA GeForce GTX 680
- GPU codename: GK104
- Device ID: 10DE-1180
- Subdevice ID: 1462-2822
- Driver: 9.18.13.697 (R306.97)
- Branch: r306_41-13
- Bus Id: 2
- Shader cores: 1536
- Texture units: 128
- ROP units: 32
- TDP: 195W
- BIOS version: 80.04.47.00.4f
- Memory size: 4096MB
- Memory type: GDDR5
- Memory bus width: 256-bit
- GPU base clock: 1058 MHz
- GPU boost clock: 1124 MHz
- GPU power target: 100 % TDP
- GPU min power target: 70 % TDP
- GPU max power target: 132 % TDP
MSIHQ: Information detected by MSIHQ Tool ver: 1.24h
MSIHQ: Report generated in Sun 11/04/2012 at 10:28:19.27
Mainboard: X79A-GD45 (8D) (MS-7760)
PCB Version: 2.0
BIOS Version: VA.6 (aka Version: V10.6)
BIOS Date: 7/6/2012
corsair ram 2x 2 paired 8gb 1600mhz cml8gx3m2a1600c9
i7-3820 @3.60 ghz
no overclock or simmilar

PXE boot issue with DHCP and SCCM server on different subnets

I'm working with a client on the operating system deployment module of SCCM.
Their network configuration currently has a single large subnet for client
computers with a DHCP server on the same subnet. The SCCM subnet is
configured on a seperate subnet with no DHCP server on the subnet. We want to
configure client computers to be able to boot using the PXE client to deploy
OS images to the machines but can not get PXE-boot to work correctly.
Also, the client does not want to make changes to their network
infrastructure routers or switches to remedy this problem. Are there settings
on the DHCP or SCCM servers we can implement to make this work? If so, what
needs to be installed or configured on each server. We currently already have
WDS installed on the SCCM server and the SCCM server is configured as a PXE
Service Point within SCCM. Both WDS and the PXE Service Point seem to be working fine.
Any help would be appreciated.
Thanks,
Gary

I am Brazilian,
sorry for wrong english
My DHCP is on linux,
in my own structure VLANS
The system center is on the network
10.0.4.0/24
The machines on the network 10.0.5.0/24
The problem is that the machines that
are not on the same network system center
can not boot
I tried configuring / etc/dhcp3/dhcpd.conf
follows
option vendor-class-identifier "PXEClient";
option bootfile-name "\
\ SMSBOOT \ \ x86 \
\ wdsnbp.com";
option tftp-server-name
"10.0.4.101"; ---->
IP server
But it did not work, anyone know
how to configure?

Boot issue with External HDD since OSX 10.10

Hi
Wanted to share my experience and I hope someone can help me here. I have a 2TB USB3.0 LaCie Minimus HDD that worked just fine on OSX 10.9 and even Windows 8.1. However since Yosemite (10.10) every single Mac (MacPro, MacBookPro) that I plug the HDD to will not longer boot-up normally (cold boot) IF the HDD is turned on. Power off the HDD every Mac on 10.10 will boot normally. However reboot and wake-up from sleep work fine.
To make sure I explained my self correctly.
Power off your mac on OSX 10.9, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and no problems.
Power off your PC with Win 8.1, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your PC. then power it on back and no problems.
Power off your mac on OSX 10.10, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and the Mac boot will be stuck until your power off the 2TB USB3.0 LaCie Minimus HDD.
Also note that Rebbot and wake from sleep work just fine in every situation and OSs. I reseted the PRAM, SMC, and tested the HDD on a Fresh 10.10 install as well as on a 10.10 upgrade and a Old 10.9.X MacBookPro.
To make sure it was not a partition problem I formatted the drive and removed all partitions (EFI) several times on each OSs... Same result.
Finally I contacted LaCie and I am waiting for their feedback.
Message was edited by: Akiba-Seattle

Here you are!
PS Thanks for helping. In My case it was disk2
XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk0
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Bootable</key>
<false/>
<key>BusProtocol</key>
<string>PCI</string>
<key>CanBeMadeBootable</key>
<false/>
<key>CanBeMadeBootableRequiresDestroy</key>
<false/>
<key>Content</key>
<string>GUID_partition_scheme</string>
<key>DeviceBlockSize</key>
<integer>512</integer>
<key>DeviceIdentifier</key>
<string>disk0</string>
<key>DeviceNode</key>
<string>/dev/disk0</string>
<key>DeviceTreePath</key>
<string>IODeviceTree:/PCI0@0/RP05@1C,4/SSD0@0/PRT0@0/PMP@0</string>
<key>Ejectable</key>
<false/>
<key>FreeSpace</key>
<integer>0</integer>
<key>GlobalPermissionsEnabled</key>
<false/>
<key>IOKitSize</key>
<integer>251000193024</integer>
<key>Internal</key>
<true/>
<key>LowLevelFormatSupported</key>
<false/>
<key>MediaName</key>
<string>APPLE SSD SM0256F Media</string>
<key>MediaType</key>
<string>Generic</string>
<key>MountPoint</key>
<string></string>
<key>OS9DriversInstalled</key>
<false/>
<key>ParentWholeDisk</key>
<string>disk0</string>
<key>RAIDMaster</key>
<false/>
<key>RAIDSlice</key>
<false/>
<key>SMARTStatus</key>
<string>Verified</string>
<key>SolidState</key>
<true/>
<key>SupportsGlobalPermissionsDisable</key>
<false/>
<key>SystemImage</key>
<false/>
<key>TotalSize</key>
<integer>251000193024</integer>
<key>VolumeName</key>
<string></string>
<key>WholeDisk</key>
<true/>
<key>Writable</key>
<true/>
<key>WritableMedia</key>
<true/>
<key>WritableVolume</key>
<false/>
</dict>
</plist>
XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk2
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Bootable</key>
<false/>
<key>BusProtocol</key>
<string>USB</string>
<key>CanBeMadeBootable</key>
<false/>
<key>CanBeMadeBootableRequiresDestroy</key>
<false/>
<key>Content</key>
<string>GUID_partition_scheme</string>
<key>DeviceBlockSize</key>
<integer>512</integer>
<key>DeviceIdentifier</key>
<string>disk2</string>
<key>DeviceNode</key>
<string>/dev/disk2</string>
<key>DeviceTreePath</key>
<string>IODeviceTree:/PCI0@0/PEG0@1/BR00@0/BR13@1/XHC1@0</string>
<key>Ejectable</key>
<true/>
<key>FreeSpace</key>
<integer>0</integer>
<key>GlobalPermissionsEnabled</key>
<false/>
<key>IOKitSize</key>
<integer>2000398934016</integer>
<key>Internal</key>
<false/>
<key>LowLevelFormatSupported</key>
<false/>
<key>MediaName</key>
<string>ST2000DM 001-1ER164 Media</string>
<key>MediaType</key>
<string>Generic</string>
<key>MountPoint</key>
<string></string>
<key>OS9DriversInstalled</key>
<false/>
<key>ParentWholeDisk</key>
<string>disk2</string>
<key>RAIDMaster</key>
<false/>
<key>RAIDSlice</key>
<false/>
<key>SMARTStatus</key>
<string>Not Supported</string>
<key>SupportsGlobalPermissionsDisable</key>
<false/>
<key>SystemImage</key>
<false/>
<key>TotalSize</key>
<integer>2000398934016</integer>
<key>VolumeName</key>
<string></string>
<key>WholeDisk</key>
<true/>
<key>Writable</key>
<true/>
<key>WritableMedia</key>
<true/>
<key>WritableVolume</key>
<false/>
</dict>
</plist>
XXXs-Mac-Pro:~ XXX$ diskutil cs list
No CoreStorage logical volume groups found
XXXs-Mac-Pro:~ XXX$
XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 490234751
      start       size index contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 488555536      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
488965176    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
490234712          7
490234719         32         Sec GPT table
490234751          1         Sec GPT header
XXXs-Mac-Pro:~ XXX$
XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk2
gpt show: /dev/disk2: mediasize=2000398934016; sectorsize=512; blocks=3907029168
gpt show: /dev/disk2: PMBR at sector 0
gpt show: /dev/disk2: Pri GPT at sector 1
gpt show: /dev/disk2: Sec GPT at sector 3907029167
       start        size index contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640 3906357344      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
3906766984      262151
3907029135          32         Sec GPT table
3907029167           1         Sec GPT header

IMac / 10.7.5 serious boot issue with OSX (neither with Bootcamp nor with Recovery)

Hey guys,
I'm a bit feeling low. I was working on my iMac and wanted to restart my device. But since then nothing's the same. It gets stuck on grey screen with spinning circle.
Here is what I tried so far:
1. Tested to boot into Bootcamp (Win7) - it works! I'm copying some files at the moment. Will check later if they're okay
2. Booted into Recovery, used DiskUtil.. No problems were found
3. Tried safe boot (with shift) and advanced safe boot (shift + cmd + v) - did not work
I'm not able to boot my OSX (and I've got no backup at the moment). Are there other hints to try to boot or to get information about what fails?
And is there a way to make a backup (maybe clone) or somekind of Time Machine without accessing OSX? I never used it before. I'm waiting for my NAS to do this - that seems to be the payback -.-
If it's helpful I've got a Macbook Air here to on which I'm writing right now.
Maybe you've got an idea!
Thanks

Reinstalling Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

Dual boot issues with P67A-GD55 (B3)

Set up a dual boot and from a cold start now the system boots directly into the default OS even though I have it set to display the options for 15 seconds. When this happens I do a soft reset and then the 2 OS choices are there. This is on the 1.C BIOS (latest). Would expect to always see the 2 OS choices on cold boot as well.

yes, I have several HDDs and an SSD. The 2 OSs are on the SSD. The original OS was on the SSD then I created free space on the SSD and installed another OS. I set the original OS as the default and the newer OS as the secondary. The SSD is now and always has been the primary boot disk in BIOS. Again, it's an easily repeatable issue, upoon cold boot there is no option of OS displayed, it just boots right into the default OS. If I reboot then I see the 2 OSs.
Quote from: Bernhard on 08-July-11, 23:12:06
>>Posting Guide<<
Do you have more than one hard drive ? Did your boot priority change in the BIOS after your BIOS flash ? If so, change it back to the HDD/partition where you initially created the dual boot.

Boot issue with Z77A-GD65

Similar Messages

Maybe you are looking for