P43NEO F - problems with booting up

I’m having real problems with my PC - which have been evident since I built it (my first attempt).
IT posts OK every time (takes about 45 seconds). However whilst I can get to the Windows splash screen it either goes through the “blue bars” about 20 times and then either freezes or is very inconsistent at entering Windows and finishing booting up.(takes over 1 minute to do so when it lets me)
I have changed the memory (previously Samsung 1 Gb) and graphics card (was a Gigabyte GS8400 512mb but tried about 13 different versions of the NVidia drivers at the time with no change to the problem. I have found that disabling the graphics driver in device manager rectifies the problem in that it boots quicker and always seems to enter XP without fuss.
I’ve tried a different CPU, graphics card and memory and also did a full reinstall of XP to no avail. (Mem test was OK for both makes when I ran it). Now have a new graphics card and memory installed. Also a couple of times the boot order in BIOS changed itself from the Maxtor HDD selected and saved to one of the USB card reader slots. Have also tried clearing CMOS but boot problem remains.
Can you help?
Thanks
Specs are as follows:
M/Board -MSI P43NEO F (serial no. 601-7519 020B0807593204)
Bios A7519IMS V1.3 062708
CPU - Intel Core 2 Duo P4600 2.4 GHz 800FSB
Graphics Card ASUS NVIDIA GE FORCE 9400GT/D1/1G(LP)
Driver 190.89 27/08/09
Memory – Kingston Value RAM DDR2 800 2x1GB KVR800D2N5K 2/2G
IDE Port Hard Drive Maxtor 6Y080P0 80Gb 7,200rpm Ultra ATA/133 8mb
(Windows XP SP 3 installed)
Also on IDE Port - LG GSA H22N DVD RW
SATA port 1 - Hard Drive Seagate Barracuda 7200.10 ST3250310AS 250GB 7200 RPM 8MB Cache
Icy Box IB 861S 4 port USB hub & Memory card reader connected to header on board (have tried different header but no change to problem)
PSU Tagan TG530 –U15 530 W
Quoted +3.3V @ 28A, +5V @ 48A, +5VSB @ 2.5A, +12V @ 20A, +12V (2nd) @ 20A, -5V @ 1A, -12V @ 0.8A
BIOS settings are default. It shows CPU temp 29 C, system temp 22 C
CPU V core 1.368V
3.3V: 3.312V
5V: 5.171V
12V: 12.144V

Must admit I had wondered about the BIOS but everything I'd read warned about the "dangers" of updating BIOS so was apprehensive about doing this.
I'll have a read of the link you've given and make sure I understand it before attempting to do it. Does that tell me which BIOS version to change to?
Thanks

Similar Messages

P35Neo2 FIR and problem with booting

So I have problem with booting my compie. Compie try to boot to the part of start windows, after that in case of switch into graphicis mobo going down and restarting (WinXP SP3). I think, that problem is not in PSU, cos i have 800W XILENCE (+3,3V 28A, +5V 32A, 4x+12V 20A, -12V 0,5A, 5VSB 3A), Board P35 Neo2 FIR, E7200 proc, bios 1.9 (updated). I have 5 disk and use raid function in bios. Graphic Radeon HD3650, Memory Zeppelin 4x1GB KIT 800Mhz.
I start with change of PSU from 550W to 800W but it didnt work, previus PSU had (+3,3V 30A, +5V 32A, 2x+12V 18A, -12V 0,8A, 5VSB 3A),
i try change memory, but no efect.
After update bios there was standard warning about bad cheksum, after resave Bios settings it was gone, and compie boot after that.
Any idea?
Thanks

So my problem is solved...but my feeling of this is not good...
I updated BIOS from 1.9 to 1.10, reset Bios settings, after restart i pressed F2 for load standart settings and i changed in Bios only that i am using RAID and disable disket and it works...i boot my compie into windows without any problem...
So i try change another things in Bios and my compie hangs in continous resets without booting into windows...no BSOD only restart and restart...
After reseting Bios settings and again Load to Default it works...and run windows...
There was only one new thing ... screen flick for the second with new screen about checking NVRAM ....this screen was not visible before (and maybe this is the problem), cos if i change something in BIOS about clocking and power management and other ones, this screen is by booting missing...and compie not run in Windows...
Next thing what i see, that in CPU multiplication dont work multiplication 9,5 and proc used frequency 2400 (9x) (it is E7200 on 2533)
i hope that this bios 1.10 fixed my problems...and my opinion is that P35 Neo 2 FIR is not ideal board for E7200 proc...so i m looking for another proc...and maybe another board...

Problem with boot / new install system ond SSD

Hi guys,
I have fresh installed system on my new SSD. I use my old HDD as external usb drive.
I have problem with boot when I dont have connected HDD to usb.
My system boot only to console no to KDE. When I connect external HDD to usb and reboot system, system boot normally.
Logs after boot.
Feb 26 16:46:39 arch systemd[1]: Reached target Login Prompts.
Feb 26 16:46:39 arch systemd[1]: Starting K Display Manager...
Feb 26 16:46:39 arch systemd[1]: Started K Display Manager.
Feb 26 16:46:39 arch systemd-logind[231]: New seat seat0.
Feb 26 16:46:39 arch systemd[1]: Started Login Service.
Feb 26 16:46:40 arch kernel: microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
Feb 26 16:46:40 arch kernel: platform microcode: Direct firmware load failed with error -2
Feb 26 16:46:40 arch kernel: platform microcode: Falling back to user helper
Feb 26 16:46:40 arch kernel: random: nonblocking pool is initialized
Feb 26 16:46:40 arch kernel: uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071)
Feb 26 16:46:40 arch laptop-mode[271]: enabled, not active
Feb 26 16:46:40 arch kernel: input: CNF7129 as /devices/pci0000:00/0000:00:1a.7/usb3/3-3/3-3:1.0/input/input16
Feb 26 16:46:40 arch kernel: usbcore: registered new interface driver uvcvideo
Feb 26 16:46:40 arch kernel: USB Video Class driver (1.1.1)
Feb 26 16:46:40 arch systemd[1]: Started Wicd a wireless and wired network manager for Linux.
Feb 26 16:46:40 arch systemd[1]: Starting Network.
Feb 26 16:46:40 arch systemd[1]: Reached target Network.
Feb 26 16:46:40 arch systemd[1]: Starting OpenSSH Daemon...
Feb 26 16:46:40 arch systemd[1]: Started OpenSSH Daemon.
Feb 26 16:46:40 arch systemd[1]: Starting NoMachine Server daemon...
Feb 26 16:46:40 arch sshd[373]: Server listening on 0.0.0.0 port 22.
Feb 26 16:46:40 arch sshd[373]: Server listening on :: port 22.
Feb 26 16:46:40 arch mtp-probe[404]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-2"
Feb 26 16:46:40 arch mtp-probe[404]: bus: 7, device: 2 was not an MTP device
Feb 26 16:46:40 arch kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 26 16:46:40 arch kernel: usbcore: registered new interface driver usbhid
Feb 26 16:46:40 arch kernel: usbhid: USB HID core driver
Feb 26 16:46:40 arch systemd[1]: Starting Sound Card.
Feb 26 16:46:40 arch systemd[1]: Reached target Sound Card.
Feb 26 16:46:40 arch systemd-udevd[145]: renamed network interface eth0 to enp3s0
Feb 26 16:46:40 arch kernel: psmouse serio4: elantech: assuming hardware version 2 (with firmware version 0x040101)
Feb 26 16:46:40 arch kernel: psmouse serio4: elantech: Synaptics capabilities query result 0x7e, 0x13, 0x0d.
Feb 26 16:46:40 arch kernel: i915 0000:00:02.0: irq 45 for MSI/MSI-X
Feb 26 16:46:40 arch kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 26 16:46:40 arch kernel: [drm] Driver supports precise vblank timestamp query.
Feb 26 16:46:40 arch kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 26 16:46:40 arch kernel: iTCO_vendor_support: vendor-support=0
Feb 26 16:46:40 arch kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
Feb 26 16:46:40 arch kernel: iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0860)
Feb 26 16:46:40 arch kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 26 16:46:40 arch kernel: input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input15
Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event2 (Lid Switch)
Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event1 (Sleep Button)
Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event3 (Power Button)
Feb 26 16:46:41 arch kernel: microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
Feb 26 16:46:41 arch kernel: platform microcode: Direct firmware load failed with error -2
Feb 26 16:46:41 arch kernel: platform microcode: Falling back to user helper
Feb 26 16:46:41 arch kernel: input: 2.4G Wireless Wireless Receiver as /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.0/input/input17
Feb 26 16:46:41 arch kernel: hid-generic 0003:1915:0F01.0001: input,hidraw0: USB HID v1.11 Keyboard [2.4G Wireless Wireless Receiver ] on usb-0000:00:1d.1-2/input0
Feb 26 16:46:41 arch kernel: input: 2.4G Wireless Wireless Receiver as /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18
Feb 26 16:46:41 arch kernel: hid-generic 0003:1915:0F01.0002: input,hidraw1: USB HID v1.11 Mouse [2.4G Wireless Wireless Receiver ] on usb-0000:00:1d.1-2/input1
Feb 26 16:46:41 arch kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Feb 26 16:46:41 arch kernel: IP: [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
Feb 26 16:46:41 arch kernel: PGD b650b067 PUD b650a067 PMD 0
Feb 26 16:46:41 arch kernel: Oops: 0000 [#1] PREEMPT SMP
Feb 26 16:46:41 arch kernel: Modules linked in: mousedev(+) hid_generic iTCO_wdt iTCO_vendor_support ath9k(+) usbhid ath9k_common hid ath9k_hw ath uvcvideo mac80211 microcode(+) videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media evdev psmouse serio_raw pcspkr cfg80211 lpc_ich i915(+) atl1e snd_hda_codec_via snd_hda_intel drm_kms_helper snd_hda_codec drm snd_hwdep snd_pcm snd_page_alloc i2c_algo_bit i2c_core snd_timer asus_laptop snd battery ac soundcore sparse_keymap acpi_cpufreq rfkill video input_polldev thermal intel_agp intel_gtt shpchp processor button ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod atkbd libps2 ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common i8042 serio
Feb 26 16:46:41 arch kernel: CPU: 1 PID: 227 Comm: acpid Not tainted 3.13.5-1-ARCH #1
Feb 26 16:46:41 arch kernel: Hardware name: ASUSTeK Computer Inc. K50IJ /K50IJ , BIOS 217 12/04/2009
Feb 26 16:46:41 arch kernel: task: ffff88007ffeda00 ti: ffff8800b6516000 task.ti: ffff8800b6516000
Feb 26 16:46:41 arch kernel: RIP: 0010:[<ffffffffa06c1317>] [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
Feb 26 16:46:41 arch kernel: RSP: 0018:ffff8800b6517c10 EFLAGS: 00010202
Feb 26 16:46:41 arch kernel: RAX: 0000000000000000 RBX: ffff8801390f5800 RCX: ffff8801390f5868
Feb 26 16:46:41 arch kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
Feb 26 16:46:41 arch kernel: RBP: ffff8800b6517c28 R08: 0000000000000000 R09: ffff88013b001600
Feb 26 16:46:41 arch kernel: R10: 0000000000000000 R11: 0000000000000004 R12: 0000000000000000
Feb 26 16:46:41 arch kernel: R13: ffff8801390f5880 R14: ffff8800b3287558 R15: ffff880138c8f600
Feb 26 16:46:41 arch kernel: FS: 00007f8de7e14700(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
Feb 26 16:46:41 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 16:46:41 arch kernel: CR2: 0000000000000000 CR3: 00000000b6507000 CR4: 00000000000407e0
Feb 26 16:46:41 arch kernel: Stack:
Feb 26 16:46:41 arch kernel: ffff88013926e400 ffff8801390f5800 ffff8801390f5878 ffff8800b6517c60
Feb 26 16:46:41 arch kernel: ffffffffa06c20cc ffff8801390f5b48 ffff8800b3287558 ffff880138c8f600
Feb 26 16:46:41 arch kernel: ffffffffa06c2e80 ffff880138c8f610 ffff8800b6517c98 ffffffff811a834f
Feb 26 16:46:41 arch kernel: Call Trace:
Feb 26 16:46:41 arch kernel: [<ffffffffa06c20cc>] mousedev_open+0xcc/0x150 [mousedev]
Feb 26 16:46:41 arch kernel: [<ffffffff811a834f>] chrdev_open+0x9f/0x1d0
Feb 26 16:46:41 arch kernel: [<ffffffff811a19e7>] do_dentry_open+0x1b7/0x2c0
Feb 26 16:46:41 arch kernel: [<ffffffff811aedc1>] ? __inode_permission+0x41/0xb0
Feb 26 16:46:41 arch kernel: [<ffffffff811a82b0>] ? cdev_put+0x30/0x30
Feb 26 16:46:41 arch kernel: [<ffffffff811a1e01>] finish_open+0x31/0x40
Feb 26 16:46:41 arch kernel: [<ffffffff811b1bf2>] do_last+0x572/0xe90
Feb 26 16:46:41 arch kernel: [<ffffffff811af0b6>] ? link_path_walk+0x236/0x8d0
Feb 26 16:46:41 arch kernel: [<ffffffff811b25cb>] path_openat+0xbb/0x6b0
Feb 26 16:46:41 arch kernel: [<ffffffff811b3cda>] do_filp_open+0x3a/0x90
Feb 26 16:46:41 arch kernel: [<ffffffff811c05c7>] ? __alloc_fd+0xa7/0x130
Feb 26 16:46:41 arch kernel: [<ffffffff811a2fd4>] do_sys_open+0x124/0x220
Feb 26 16:46:41 arch kernel: [<ffffffff811a30ee>] SyS_open+0x1e/0x20
Feb 26 16:46:41 arch kernel: [<ffffffff8152142d>] system_call_fastpath+0x1a/0x1f
Feb 26 16:46:41 arch kernel: Code: c0 6e e5 e0 5b 44 89 e0 41 5c 41 5d 5d c3 66 0f 1f 44 00 00 4c 89 ef 41 bc ed ff ff ff e8 a2 6e e5 e0 eb e0 48 8b 15 c9 21 00 00 <8b> 02 8d 48 01 85 c0 89 0a 75 c6 48 8b 05 37 1f 00 00 48 3d 60
Feb 26 16:46:41 arch kernel: RIP [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
Feb 26 16:46:41 arch kernel: RSP <ffff8800b6517c10>
Feb 26 16:46:41 arch kernel: CR2: 0000000000000000
Feb 26 16:46:41 arch kernel: ---[ end trace 76aa0cbb67cf77f6 ]---
Feb 26 16:46:41 arch kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Feb 26 16:46:41 arch systemd[1]: acpid.service: main process exited, code=killed, status=9/KILL
Feb 26 16:46:41 arch systemd[1]: Unit acpid.service entered failed state.
Feb 26 16:46:41 arch kernel: [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
Feb 26 16:46:41 arch systemd[1]: Started Laptop Mode Tools.
Feb 26 16:46:41 arch nxserver[374]: NX> 161 Enabled service: nxserver.
Feb 26 16:46:42 arch kernel: fbcon: inteldrmfb (fb0) is primary device
Feb 26 16:46:42 arch kernel: ath: phy0: Enable LNA combining
Feb 26 16:46:42 arch kernel: ath: EEPROM regdomain: 0x60
Feb 26 16:46:42 arch kernel: ath: EEPROM indicates we should expect a direct regpair map
Feb 26 16:46:42 arch kernel: ath: Country alpha2 being used: 00
Feb 26 16:46:42 arch kernel: ath: Regpair used: 0x60
Feb 26 16:46:42 arch kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Feb 26 16:46:42 arch kernel: ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90011e80000, irq=17
Feb 26 16:46:42 arch systemd-udevd[139]: renamed network interface wlan0 to wlp2s0
Feb 26 16:46:42 arch kernel: Console: switching to colour frame buffer device 170x48
Feb 26 16:46:42 arch kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Feb 26 16:46:42 arch kernel: i915 0000:00:02.0: registered panic notifier
Feb 26 16:46:42 arch kernel: ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
Feb 26 16:46:42 arch kernel: acpi device:38: registered as cooling_device2
Feb 26 16:46:42 arch kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input19
Feb 26 16:46:42 arch nxserver[374]: NX> 161 Enabled service: nxnode.
Feb 26 16:46:42 arch nxserver[374]: NX> 161 Enabled service: nxd.
Feb 26 16:46:42 arch systemd[1]: Started NoMachine Server daemon.
Feb 26 16:46:42 arch systemd[1]: Starting Multi-User System.
Feb 26 16:46:42 arch systemd[1]: Reached target Multi-User System.
Feb 26 16:46:42 arch systemd[1]: Starting Graphical Interface.
Feb 26 16:46:42 arch systemd[1]: Reached target Graphical Interface.
Feb 26 16:46:42 arch systemd[1]: Startup finished in 1.241s (kernel) + 3.231s (userspace) = 4.473s.
Feb 26 16:46:46 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Feb 26 16:46:48 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 26 16:46:49 arch wicd[226]: dhcpcd[1383]: dhcpcd not running
Feb 26 16:46:49 arch dhcpcd[1383]: dhcpcd not running
Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: wlp2s0 error: No such file or directory
Feb 26 16:46:49 arch wicd[226]: dhcpcd[1389]: dhcpcd not running
Feb 26 16:46:49 arch dhcpcd[1389]: dhcpcd not running
Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: enp3s0 error: No such file or directory
Feb 26 16:46:49 arch wicd[226]: dhcpcd[1397]: dhcpcd not running
Feb 26 16:46:49 arch dhcpcd[1397]: dhcpcd not running
Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: wlp2s0 error: No such file or directory
Feb 26 16:46:51 arch systemd[1]: Starting Getty on tty2...
Feb 26 16:46:51 arch systemd[1]: Started Getty on tty2.
Feb 26 16:46:52 arch kernel: wlp2s0: authenticate with 08:86:3b:7f:86:08
Feb 26 16:46:52 arch kernel: wlp2s0: send auth to 08:86:3b:7f:86:08 (try 1/3)
Feb 26 16:46:52 arch kernel: wlp2s0: authenticated
Feb 26 16:46:52 arch kernel: ath9k 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use
Feb 26 16:46:52 arch kernel: wlp2s0: associate with 08:86:3b:7f:86:08 (try 1/3)
Feb 26 16:46:52 arch kernel: wlp2s0: RX AssocResp from 08:86:3b:7f:86:08 (capab=0x411 status=0 aid=4)
Feb 26 16:46:52 arch kernel: wlp2s0: associated
Feb 26 16:46:52 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Feb 26 16:46:53 arch dhcpcd[1416]: version 6.2.1 starting
Feb 26 16:46:54 arch dhcpcd[1416]: DUID 00:01:00:01:1a:96:a5:70:1c:4b:d6:a2:1f:ad
Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: IAID d6:a2:1f:ad
Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: soliciting an IPv6 router
Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: ipv6nd_sendrsprobe: sendmsg: Cannot assign requested address
Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: rebinding lease of 192.168.2.3
Feb 26 16:46:55 arch kernel: type=1006 audit(1393429615.096:2): pid=1406 uid=0 old auid=4294967295 new auid=0 old ses=4294967295 new ses=1 res=1
Feb 26 16:46:55 arch login[1406]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Feb 26 16:46:55 arch systemd[1]: Starting user-0.slice.
Feb 26 16:46:55 arch systemd[1]: Created slice user-0.slice.
Feb 26 16:46:55 arch systemd[1]: Starting User Manager for 0...
Feb 26 16:46:55 arch kernel: type=1006 audit(1393429615.106:3): pid=1477 uid=0 old auid=4294967295 new auid=0 old ses=4294967295 new ses=2 res=1
Feb 26 16:46:55 arch systemd[1]: Starting Session 1 of user root.
Feb 26 16:46:55 arch systemd[1]: Started Session 1 of user root.
Feb 26 16:46:55 arch systemd-logind[231]: New session 1 of user root.
Feb 26 16:46:55 arch systemd[1477]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 26 16:46:55 arch login[1406]: ROOT LOGIN ON tty2
Feb 26 16:46:55 arch systemd[1477]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
Feb 26 16:46:55 arch systemd[1477]: Mounted /sys/kernel/config.
Feb 26 16:46:55 arch systemd[1477]: Stopped target Sound Card.
Feb 26 16:46:55 arch systemd[1477]: Starting Default.
Feb 26 16:46:55 arch systemd[1477]: Reached target Default.
Feb 26 16:46:55 arch systemd[1477]: Startup finished in 7ms.
Feb 26 16:46:55 arch systemd[1]: Started User Manager for 0.
Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: leased 192.168.2.3 for 283824000 seconds
Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: adding route to 192.168.2.0/24
Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: adding default route via 192.168.2.1
Feb 26 16:46:59 arch dhcpcd[1416]: forked to background, child pid 1522
Feb 26 16:47:10 arch kdm[238]: X server startup timeout, terminating
Feb 26 16:47:12 arch systemd-udevd[131]: worker [140] /devices/pci0000:00/0000:00:02.0 timeout; kill it
Feb 26 16:47:12 arch systemd-udevd[131]: seq 1255 '/devices/pci0000:00/0000:00:02.0' killed
Feb 26 16:47:12 arch systemd-udevd[131]: worker [146] /devices/platform/i8042/serio4/input/input15 timeout; kill it
Feb 26 16:47:12 arch systemd-udevd[131]: seq 1659 '/devices/platform/i8042/serio4/input/input15' killed
Feb 26 16:47:12 arch systemd-udevd[131]: worker [148] /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18 timeout; kill it
Feb 26 16:47:12 arch systemd-udevd[131]: seq 1679 '/devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18' killed
Feb 26 16:47:12 arch kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Feb 26 16:47:12 arch systemd-udevd[131]: worker [140] terminated by signal 9 (Killed)
Feb 26 16:47:12 arch systemd-udevd[131]: worker [148] terminated by signal 9 (Killed)
Feb 26 16:47:12 arch systemd[1]: Starting Load/Save Screen Backlight Brightness of acpi_video0...
Feb 26 16:47:12 arch systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0.
Feb 26 16:47:12 arch kernel: input: failed to attach handler mousedev to device input15, error: -4
Feb 26 16:47:12 arch systemd-udevd[131]: worker [146] terminated by signal 9 (Killed)
Feb 26 16:47:12 arch kernel: input: failed to attach handler mousedev to device input18, error: -4
Feb 26 16:47:12 arch kernel: mousedev: PS/2 mouse device common for all mice
Feb 26 16:47:13 arch kdm[238]: X server for display :0 cannot be started, session disabled
Feb 26 16:48:56 arch kernel: usb 7-2: USB disconnect, device number 2
Feb 26 16:48:56 arch laptop-mode[1782]: Laptop mode
Feb 26 16:48:56 arch laptop-mode[1783]: enabled, not active
Feb 26 16:48:56 arch laptop-mode[1834]: Laptop mode
[xx@arch Desktop]$ uname -a
Linux arch 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux
Could you please someone help me with this?
Thanks

Sorry to bump this, but I'm having the exact same error tonight on my HTPC, any chance you found out what the problem was ?
To make matters worse, it's not happening every single time, but maybe every 4 out of 5 boots (same kernel, no changes in between.)
I thought this was a kernel issue related to this:
https://lkml.org/lkml/2014/3/10/359
I've tried adding atkbd and psmouse to my mkinitcpio.conf MODULES section and rebuilt, but no change.
I changed the NVidia driver from nvidia-304xx to nvidia-full-beta-all ( 334.21 ) from AUR but it had the same error at the same place.
Here's the part from `dmesg` where it borks:
[ 3.229195] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:04.0-3/input2
[ 3.236312] input: Logitech Unifying Device. Wireless PID:400e as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input6
[ 3.237230] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:04.0-3:1
[ 3.279150] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 3.280083] IP: [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
[ 3.280810] PGD c99ea067 PUD c9f4a067 PMD 0
[ 3.281266] Oops: 0000 [#1] PREEMPT SMP
[ 3.281668] Modules linked in: mousedev(+) nvidia(PO+) snd_hda_codec_realtek hid_logitech_dj usbhid hid usb_storage coretemp evdev microcode pcspkr serio_raw snd_hda_intel(+) snd_hda_codec shpchp snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore i2c_nforce2 i2c_core wmi processor button r8169 mii ext4 crc16 mbcache jbd2 sd_mod ata_generic pata_acpi ahci libahci libata ohci_pci ohci_hcd ehci_pci ehci_hcd scsi_mod usbcore usb_common psmouse atkbd libps2 i8042 serio
[ 3.281820] CPU: 1 PID: 211 Comm: acpid Tainted: P O 3.13.6-1-ARCH #1
[ 3.281820] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./MCP7A-ION, BIOS 080015 10/10/2009
[ 3.281820] task: ffff8800ca5c1b00 ti: ffff8800c97f0000 task.ti: ffff8800c97f0000
[ 3.281820] RIP: 0010:[<ffffffffa1cbc317>] [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
[ 3.281820] RSP: 0018:ffff8800c97f1c10 EFLAGS: 00010202
[ 3.281820] RAX: 0000000000000000 RBX: ffff8800c9987000 RCX: ffff8800c9987068
[ 3.281820] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
[ 3.281820] RBP: ffff8800c97f1c28 R08: 0000000000000000 R09: ffff8800cf401600
[ 3.281820] R10: 0000000000000000 R11: 0000000000000004 R12: 0000000000000000
[ 3.281820] R13: ffff8800c9987080 R14: ffff8800c0260058 R15: ffff8800c9f2a500
[ 3.281820] FS: 00007f8f12f05700(0000) GS:ffff8800cfa80000(0000) knlGS:0000000000000000
[ 3.281820] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 3.281820] CR2: 0000000000000000 CR3: 00000000ca93e000 CR4: 00000000000007e0
[ 3.281820] Stack:
[ 3.281820] ffff8800c9940000 ffff8800c9987000 ffff8800c9987078 ffff8800c97f1c60
[ 3.281820] ffffffffa1cbd0cc ffff8800c9987348 ffff8800c0260058 ffff8800c9f2a500
[ 3.281820] ffffffffa1cbde80 ffff8800c9f2a510 ffff8800c97f1c98 ffffffff811a83ef
[ 3.392372] Call Trace:
[ 3.398245] [<ffffffffa1cbd0cc>] mousedev_open+0xcc/0x150 [mousedev]
[ 3.398245] [<ffffffff811a83ef>] chrdev_open+0x9f/0x1d0
[ 3.398245] [<ffffffff811a1a87>] do_dentry_open+0x1b7/0x2c0
[ 3.398245] [<ffffffff811aee61>] ? __inode_permission+0x41/0xb0
[ 3.398245] [<ffffffff811a8350>] ? cdev_put+0x30/0x30
[ 3.398245] [<ffffffff811a1ea1>] finish_open+0x31/0x40
[ 3.398245] [<ffffffff811b1c92>] do_last+0x572/0xe90
[ 3.398245] [<ffffffff811af156>] ? link_path_walk+0x236/0x8d0
[ 3.398245] [<ffffffff811b266b>] path_openat+0xbb/0x6b0
[ 3.508083] random: nonblocking pool is initialized
[ 3.398245] [<ffffffff811b3d7a>] do_filp_open+0x3a/0x90
[ 3.398245] [<ffffffff811c0617>] ? __alloc_fd+0xa7/0x130
[ 3.398245] [<ffffffff811a3074>] do_sys_open+0x124/0x220
[ 3.398245] [<ffffffff811a318e>] SyS_open+0x1e/0x20
[ 3.398245] [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
[ 3.556729] Code: 40 c1 85 df 5b 44 89 e0 41 5c 41 5d 5d c3 66 0f 1f 44 00 00 4c 89 ef 41 bc ed ff ff ff e8 22 c1 85 df eb e0 48 8b 15 c9 21 00 00 <8b> 02 8d 48 01 85 c0 89 0a 75 c6 48 8b 05 37 1f 00 00 48 3d 60
[ 3.556729] RIP [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
[ 3.556729] RSP <ffff8800c97f1c10>
[ 3.556729] CR2: 0000000000000000
[ 3.563412] ---[ end trace 590b482a8704c6ac ]---
[ 3.980300] input: HDA NVidia HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:08.0/sound/card0/input7
Here's the output on a good boot:
[ 3.415791] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:04.0-3/input2
[ 3.422256] input: Logitech Unifying Device. Wireless PID:400e as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input6
[ 3.422644] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:04.0-3:1
[ 3.434861] mousedev: PS/2 mouse device common for all mice
[ 3.853639] input: HDA NVidia HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:08.0/sound/card0/input7
Here's my mkinitcpio.conf
: grep -v ^\# /etc/mkinitcpio.conf
MODULES="atkbd psmouse"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
Last edited by corpdecker (2014-03-19 02:47:30)

Problems with Boot Camp - PLEASE HELP!

I'm having problems with Boot Camp. Here's what's happening. I ran Boot Camp Assistant, partitioning a 32GB BOOTCAMP drive. I insert my copy of XP and start the installation. My MBP restarts and boots into the Windows Setup. I let it run through the initial actions. I press ENTER to proceed, F8 to accept the license agreement, then when I get to the part where I should be able to select the Partition 3 BOOTCAMP drive (as it says in the Apple Boot Camp Manual) there is only a Partition 1 Unknown drive. It is the only drive to choose from and its a C: drive. I can't figure out why after I run boot camp the partitioned drive doesn't appear as an option in the windows installation. Please help!!!
Message was edited by: CarlConti08

Boot into Leo, start Disk Utility and you should see two partitions, your Leo partition and a Fat32 partition of 32GB at the end of the drive.
If not, boot camp didn't create it for some reason. If it is there then check it with DU and make sure its OK.
While your in there give it a name so you can easily identify it in your windows installer.
If there is no partition, create one using Disk Utility at the END if the drive. make sure you create it as a msdos (Fat32) partition and give it a name. The name cannot be more than 11 characters must be comprised of numbers and/or letters (no special characters).
Verify it before exiting DU.
Put in windows install disk, reboot - hold option key after the chime until you see the boot screen - select windows CD to begin install.
Don't forget to install Leo windows drivers after installing windows.
Kj

875P NEO FIS2R problems with booting at power-up

Having problems with booting at power-up.
Recently, with no apparent modification to system - at power up the system will often not boot. About 80% of time systems seems to go into a loop with CD/DVD drive light blinking a few times, then the floppy drive light comes on and can hear the FDD run – within 30 seconds or so, this process starts over again. Power switch LED is on and HDD LED is on (continuously). All fans are running (power supply fan, case fan, CPU fan and Intel Canterwood 875 fan ).
Monitor power on light is in power save mode (amber) when system does not boot. When boot is successful the monitor power light turns green immediately.
After pressing the reset button several times (varies between pressing reset button 1 time to 30 or more times) system will then boot OK or go into set up.
Once running there is no apparent problem.
This mainboard comes with D Bracket containing 2 USB 2.0 ports, and 4 diagnostics LEDs - when boot problem occurs the diagnostic LEDs, give a code that in the MSI mainboard manual states “Initializing Keyboard Controller” and diagnostic LEDs stays in this mode until via reset button provides a successful boot and start up.
Have reseated all connectors.
SYSTEM
Mainboard – MSI 875P Neo FIS2R (MSI 6758)
BIOS – AMI v1.8 (has not been updated)
CPU – Intel P4 2.6 GHz - system bus 800 MHz 512 KB L2 Cache
Memory – 1.5 gb (2 x 256 mb and 2 x 512mb)
Power Supply – Antec 380 watt
HDD – IED WD 160 GB and IED WD 40 GB
Video Card – ATI Radeon 9600 (128 RAM)
Operating System – MS Windows XP Pro (sp2)

Quote from: BOSSKILLER on 17-May-08, 03:34:12
Have you done >>Clear CMOS Guide<<?
Cleared CMOS - no change same problem. Also, re-seated all connectors at same time.
Quote from: Wonkanoby on 17-May-08, 09:06:54
have you just added the second wd drive
are they jumpered right
jumperless if alone on ide
jumpered master /slave if two on it
No, second 40GB HDD was installed months before this issue started and is jumpered as slave drive. Also, no other additional hardware installed for several months before issue.

Problems with Booting and Reliability

Hi all I just recently purchased an AMD 64 3400 and an MSI K8T NEO mobo. First off I have had nothing but problems. This was an upgrade from an old Athlon 1700XP and a Gigabyte board so I expected some hiccups. First I had some boot problems from the start. That ended up being a PSU problem and I am now the proud owner of an Antec True Power 550. Boot problem solved.
Next I began experiencing stability problems. It started out being a stutter here or there during the occasional gaming session. It eventually got worse. Mostly freezes no hard crashes or BSOD.
Well it got so bad that the computer would no longer POST reliably. So began the long troubleshooting process. I have had some heat issues in the past so that is where I began. I cleaned up cables, re-routed several, and added a PCI slot fan. This made a smidge of improvement and I thought that my problem was video card related as my GeForce4 4600ti is beginning to show its age but I was even having problems surfing the internet.
Well after reading several post on these forums and the AMD forums I realized that my old DDR266 PC2100 RAM may be the problem.
When I purchased the system in spring 2002 I bought 512 megs of Samsung RAM according to the chips on the stick anyways (I admit I do not know the actual manufacturer of the stick). Well this did not seem to be enough for games such as Star Wars Galaxies so I bought another stick of DDR266 PC2100 512 megs (again not sure of the stick maker but the chips are Infineon). So this is where I began trouble shooting. I swapped wo sticks for one with no luck. Then I tried swapping the sticks and I got a POST beep (beepage good!) and the computer booted. So I thought problem solved. Well it would last for anywhere between 10 minutes and several hours before another freeze.
Well today I stopped into Worst Buy and picked up a stick of Crucial PC3200. With trepidation I plugged the stick in and no POST...nothing. With the Samsung stick I am able to get a proper boot about 10% of the time.
I have seen lots of posts regarding newer faster RAM and compatibilty issues with them. I dont see any problems with older RAM. My question is: Is my problem RAM related or am I barking up the wrong tree (tree...RAM stick...get it?). Even with the newer Crucial PC3200 I am still having problems. If anyone could assist me I would greatly appreciate it.
Thanks in advance.

Quote
next put ram in slot 1 and 3 if you onlly have 2 sticks.
try limiting ram speed to 333 see if that helps.
try using only one stick
disable onbaord stuff you dont need, l
i wasnt having much luck with onboard network , that was 1st to go.
ike parallel ports, if you have a usb printer,
if heat is an issue try running with case cover off.
unless your cpu cooler was not mounted well (rubed off thermal pad having trouble locking it). but i doubt that and would lead to more trouble checking , becuse you would have to remout with artic silver or something.
Well my original RAM is only 266 so the limiting to 333 wont help that. Using one stick is the only way that I can actually get the thing to boot at all but with limited reliability.
I run with the cover off constantly because I am constantly fiddling with the thing. I have taken the HSF off, cleaned it, put new paste on and replaced. My CPU temps have never been above 43 degrees celsius. I have replaced the stocker HSF with a Thermal Take Venus 12.
Thanks for the reply.

Help! problems with boot...

My system has worked fine for a week, but I have been unable to get the usb in front of my computer to work so I tried again today. I booted right after that but a strange noice came, sounded like electrisity and I got a bad CMOS message and the machine refused to boot. I tried to run flash recovery but for some reason both my floppy and keyboard does not seem to work/boot. I have tried another keyboard but nothing happends. I have tried to reset bios and to take out the cmos-battery but it made no change. any ideas of what I can do?

Quote
Originally posted by Jocko
Hi
The differance between this mobo and others, is the useage of the +12v, the CPU and mobo need at least 12amps to post. That leaves nothing for HDDs, Cds, fans, Graphic Card, etc. Your system will not be able to cope for long.
jocko
Taraquin these guys told me the same thing a few weeks ago about my PSU. My system was working fine, so I was like no that can't be right. but after some research on the net. I found that Jocko, SAB, and tiresmoke was dead on the money about the PSU.
From what I read and put together from several resources was that this mobo, CPU combo all by it's self pull heavily on the PSU. you add a Vid card, like an ATI 9800, a few cd roms and floppy and a few hard drives and use something different than the on board sound. What would be considered an average to good PSU just will not cut it with this system. after reading all of this I purchased an Antec true 550. you can believe what you like. but my system that i thought was having no problems, Now boots smoother, I have kept a check on my voltages they don't fluctuate like they did before. and the over performance of the system is better. I remember reading somewhere and I can't remember if it was here or else where that on the 12+ side you need a minimum of 24A for this system to operate well. DeMaxx

I have a problem with boot camp and maybe macbook pro?

I am having issues with boot camp here is what I did.
I attempted to partition for windows then this message popped up after 2 minutes:
Verification failed. this disk could not be partitioned.
Use Disk Utility to repair this disk.
so I used the disk utility to repair the problem then this message came:
First Aid failed
Disk Utility stopped verifying “Macintosh HD” because the following error was encountered:
The underlying task reported failure on exit
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file Temp File
(It should be 13 instead of 0)
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume bitmap.
pair",0)
Checking volume information.
Invalid volume free block count
(It should be 23087569 instead of 23087570)
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
So let me explain something. I just got the macbook pro put some music on it and pictures. so what do I do to fix this problem? please let me know.

Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) 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 installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If you are unable to repair the drive then you will need to reformat the drive using Disk Utility. Of course this will erase all your files so have a backup before you start.
Basic Backup
Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
7. SuperDuper! (Commercial)
The following utilities can also be used for backup, but cannot create bootable clones:
1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
2. Toast
3. Impression
4. arRSync
Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore. Also read How to Back Up and Restore Your Files.

[nVidia Series] Problems with boot time for p4n sli

I have spent a couple of hours digging trying to find out some information.
I bought the p4n sli (not diamond) and everything seems to work fine, BUT the boot time is very long. It seems to try to access the dvd drive for 30 to 45 seconds and then it will boot. Once it starts to boot I get 4 error code beeps and one that sounds as if it would be the normal everything is good beep (the fifth beep is always different and usually in the middle of the four same tone beeps).
I have a intel 630 cpu, a nvidia 6800gt vid card, one gig of corsair dual channel memory and 1 gig of geil dual channel memory (I get the same errors without the different memory), I have a 450 thermaltake psu, a maxtor 120 gig sata drive and a 160 gig ide drive.
I have no problems with anything once the computer is booted up. It just takes a lot longer to even start to boot than I have seen with modern computers.
The beep codes thread stated that
4 beeps - Timer not operational - bad motherboard
5 beeps - Processor error - bad processor
Would I still be able to run this computer if either of these was true? I would love any advice. I do not want to burn up anything.

Quote from: hcoshawn on 11-January-06, 05:21:01
hey LtDano38,
Im sure that the beeps that you are hearing are on account of the amount of USB devices that you have hooked up. You should get one for every device, the low tone one that you hear is the bios beep saying that everything is normal. The USB beeps should come before the different tone one at the end.
As for the boot time, i would try a different cd-row to see if it does the same. Also is the drive IDE or SATA?
GL and post back.
ok, I do have four usb devices, a flight stick, a nostromo, and usb mouse and keyboard, I have one ide hd, one sata hd and an ide dvd. I tried slaving the dvd off of the hd and with it by itself on the other ide channel. My os is on the ide hd. One last question, can I use anymore abbreviations?

Problem with Boot Camp - Help!!

Hi everyone,
So I just got a new MacBook and installed Windows XP Home Edition through Bootcamp. I followed the computer certification guidelines of my college (so that I can connect to the network), i.e., I installed Symantec Antivirus and Windows Defender (required), and also Firefox and MS Office, and for good measure, I installed AdAware and Spybot (both free versions). I did not use the internet at all and scanned the totally-unadultered computer, deleting the very few things that popped up on Adaware and Spybot.
However, the very next morning, Windows Explorer kept getting closed by "Data Execution Prevention" every time I tried to start Windows. (It says, "Instruction at 'Ox8bb9ed475' referenced memory at 'Ox8b9ed465'. Memory could not be 'written'".) Essentially, I can't use Windows and no amount of restarting remedies this.
I took my MacBook to the Genius Bar at an Apple store and they said the problem was most likely Symantec Antivirus - apparently, Symantec has lots of problems with Bootcamp; they also recommended using Parallels instead. But since Penn requires Symantec to certify a computer, I don't know what to do about this (not to mention Windows won't run anyway)! To be sure, the Apple guys were very rushed and seemed to be speculating, so I'm not sure how to take their advice.
Does anyone know what might be wrong? I remember reading that some current students at my school run Bootcamp just fine, and the tech dept. suggests using it as well. Any help would be GREATLY appreciated; I just don't want problems to occur once I start classes. Thanks so much.

Perhaps you should post this question in the Boot Camp forum rather than here. This is not the proper forum for dealing with Boot Camp or Windows installation problems.
I would consider reinstalling Windows. After verifying that it is working you can install Symantec AntiVirus and Defender, but I would not install anything else until you are sure the system is working properly. Note that you must turn off antivirus programs when you install new software. Failing to do so can result in defective installations.
Be sure you have carefully read the Boot Camp documentation before installing anything.

Time, date and settings problems with boot camp

I have recently installed Windows XP using boot camp on my macbook, and everything seemed to be working fine for a while. However, after a couple of weeks, i am now getting date and time errors every time i shut down Windows and boot back into Mac OS. Upon restart the date always resets it self to December 2000, and this causes multiple programs to stop working. Also, airport forgets my wireless settings and no longer connects to my base station until i re-enter the passwords, so the date wont correct itself using the internet. The only way i have been able to set the correct time and date is to either set it manually, or to use the ethernet cable as it requires no passwords, which is inconvenient as my base station is in a awkward place.
After resetting the time, date and internet settings, my macbook works perfectly again until the next time i use boot camp. I have also had exactly the same problem with another macbook i have, and cannot figure out how to stop this from happening.

FAT32 will accessible from both Windows and OS X
If you don't want to reformat your ext drive you need something like http://www.paragon-software.com/home/hfs-windows/ or http://www.mediafour.com/products/macdrive/

Problem with boot camp and windows 8

I have a Macbook late 2009 with Mountain Lion. I want to install windows 8 with boot camp but when I am asked to enter drivers, windows 8 don't find them. I have downloaded drivers from boot camp assistant but they don't work. When Apple will provide ???

Obviously Boot Camp does not support Win 8 at this time. When and IF Apple decides to do that no one here knows. This is a user to user forum. Perhaps you should call Apple support and ask them.

Problems with Boot Camp - HELP!!

Hi everyone,
So I just got a new MacBook and installed Windows XP Home Edition through Bootcamp. I followed the computer certification guidelines of my college (so that I can connect to the network), i.e., I installed Symantec Antivirus and Windows Defender (required), and also Firefox and MS Office, and for good measure, I installed AdAware and Spybot (both free versions). I did not use the internet at all and scanned the totally-unadultered computer, deleting the very few things that popped up on Adaware and Spybot.
However, the very next morning, Windows Explorer kept getting closed by "Data Execution Prevention" every time I tried to start Windows. (It says, "Instruction at 'Ox8bb9ed475' referenced memory at 'Ox8b9ed465'. Memory could not be 'written'".) Essentially, I can't use Windows and no amount of restarting remedies this.
I took my MacBook to the Genius Bar at an Apple store and they said the problem was most likely Symantec Antivirus - apparently, Symantec has lots of problems with Bootcamp; they also recommended using Parallels instead. But since Penn requires Symantec to certify a computer, I don't know what to do about this (not to mention Windows won't run anyway)! To be sure, the Apple guys were very rushed and seemed to be speculating, so I'm not sure how to take their advice.
Does anyone know what might be wrong? I remember reading that some current students at my school run Bootcamp just fine, and the tech dept. suggests using it as well. Any help would be GREATLY appreciated; I just don't want problems to occur once I start classes. Thanks so much.

Hello and welcome to Apple Discussions...
I typed "Data Execution Prevention" into Google's search bar ... here are the results: Something to do with Windows XP and Service Pack 2. Go here:
http://www.google.com/search?client=safari&rls=en&q=DataExecutionPrevention&ie=UTF-8&oe=UTF-8
One thing that might not be helping matters is using AdAware and Spybot. They can cause more problems then they can find.
Hopefully the Google search will at least get you started in the right direction!
Carolyn

Problem with boot camp

Hi, how are you all
I have a problem since 3 months
I tried something in boot camp and ended up doing something wrong
Now every time I want to start my iMac I need to hold alt and choose MAC, or else it will take me to black screen that shows "no driver found to boot...."
I thought it wasn't that big deal, I don't need windows anymore, and it is not that hard to hold alt key while imac starts
but today I tried to install windows, because I upgraded ram to 12gb and wanted to try them, but I couldn't
I did devoid the hard disk successfully, but when I want to install windows 7 the computer restart, this is normal I know, but then it takes me to the white screen again where I can either hold down alt button and it will take me back to snow leopard, or don't hold any key which will take me again to that black screen I mentioned before
This is really frustrating
I live in UAE so there is no apple store here, and no offense but every authorized apple reseller has stupid people that don't know a bit about MAC, just hired to sell with no knowledge, I asked them about the problem and no one knew what I was talking about and brought the imac and no one knew how to solve it.
So hopefully ill find answer here
Please if you know the answer tell me, want to try the RAM
Thanks, Ahmad

Redo your install.
As in Boot from Windows 7 and do a clean install, format the drive which is already NTFS.
Installation Guide Instructions for all features and settings.
Boot Camp FAQ Get answers to commonly asked Boot Camp questions.
Windows 7 FAQ Answers to commonly asked Windows 7 questions.
Discussions forums Discuss Boot Camp topics with other users.
Troubleshooting
iMac displays a black screen during installation of Windows 7
Symptoms
When installing Microsoft Windows 7 on an iMac (27-inch, Late 2009) and iMac (21.5-inch, Mid 2010) using Boot Camp, a black screen may appear. This can happen because the Windows 7 installer does not include the necessary graphics or Bluetooth drivers for your Mac.
http://www.apple.com/support/bootcamp/
Pay attention to any Apple tips and articles above that deal with your Mac.
Have your OS X DVD ready for after Windows is installed.
Tip: Most geniuses have mixed or limited or wrong information about Windows and installing on Mac, using Boot Camp tools. The above page and articles are good starting place, should be directed to when questions come up.
And take everything with a grain of salt. Good luck.

Problems with Boot Camp and Drive Partition

First of all, let me preface this by saying I have in the past successfully partitioned my drive and installed Windows, but it was a while back and I can remember it was frustrating, but I don't remember the exact details. Also, I apologize for the rambling nature of this problem, but I'm trying to give as much relevant information as possible and walk through the steps I took to get where I am now.
Feel free to skip ahead to the end, the main problem seems to be I tried to create a 300 GB partition, but it didn't take or something. Now my storage is reflecting I've lost 300 GB, but it won't recognize the existence of the new partition.
Let me just walk through what I did. I deleted my previous partition because I was having some difficulties with a few programs and the partition ended up being too small and I wanted to make a bigger one anyway. I only use it for gaming and didn't care about any of the saved games so I just deleted the partition and figured I'd start over from scratch.
Before I begin, some technical details about the computer I'm working with. I don't know how much of this is necessary, but here it is:
It's a 27-inch late 2012 iMac with a 3.4 GHz Intel Core i7 processor with 24GB RAM running OSX 10.9.4
The storage space is a little more difficult as that is part of the problem I'm running into, which I'll get to in a minute.
Anyway, I have a Windows 7 Professional install DVD and a burned CD called Boot Camp, which I think is the drivers from last time I installed Windows (a year and half ago?), but since I needed Superdrive for the install DVD I just used an XHD I had to put the drivers on (like I said, I don't remember how I did it last time). I go through Boot Camp and look at how much space I have and how big I want to make my partition.
Side note: Last time I made my partition, I'm fairly certain I set it to 200 GB, but the partition size actually came out to something like 112 GB or something significantly less. I didn't know what happened, but figured it would still be enough space and it had been such a hassle I didn't bother doing it again.
Supposedly I have a 1 TB HD, and I can't remember exactly what it said when I partitioned the drive this time, but it definitely said I was using less than half of my capacity and I had plenty of room, so I opted to go for a 301 GB partition (the slider wouldn't let me do exactly 300) which still left me with around 300 GB of space left over on my Mac partition I want to say. I went ahead with it and it started partitioning the drive with the blue line moving very slowly and after an hour or so it was like 80% across but no longer making progress. I looked online and people said that shouldn't happen. I cancelled the partition and the Disk Utility showed the partition, but said it was unmounted or something.
I restarted my computer thinking maybe I'd try and see what would happen if I tried to boot it up as if I had Windows installed. I also at that moment remembered that I'd had a similar problem last time because I had my XHD plugged into my USB port so I unplugged that and held down OPT. It then showed me my Mac HD drive and a CD icon that said Windows, so I clicked on that figuring maybe I could install it after all.
It led me through a Install manager and it got to the point where it asked what drive/partition do you want to install Windows in, I recognized the screen and remembered I was supposed to choose a certain one, but couldn't remember which one and none of the sizes seemed to match the storage I had allocated to the partition. One was about 200 GB and since the last time I did it my partition came out 100 GB smaller than I had set it for I thought maybe that was it.
However, it said I couldn't install on that drive for some reason (I can't remember exactly what it said). So I restarted again and figured I'd go back and see what I did wrong and start over. When I check Disk Utility it no longer sees any partition (mounted or unmounted or anything) and that the entirety of my HD is dedicated to Mac HD.
The problem is, now I'm getting weird reports about the size of my drive, the amount used, and the space available. Disk Utility tells me I have 1.12 TB capacity, 301 GB available, and 819 GB used. That doesn't even add up. Furthermore, when I click get info on Macintosh HD, it tells me I have 810 GB capacity, 364 GB available, and 446 GB used. When I click on About this Mac and go to System Report and storage I get this:
Macintosh HD
Available: 364 GB
Capacity: 810 GB
Logical Volume Group:
     Name: Macintosh HD
     Size: 1.12 TB
     Freespace: 301 GB
Physical Volumes:
     disk0s2:
   size: 121 GB
     disk1s2:
     size: 999 GB
Now I really don't know what to make of it. That 301 GB free space makes sense as the partition I tried to create and if I add that to the 446 GB used on my Mac partition, plus the 364 GB available, that adds up to 1.12 TB (roughly, I've rounded off these numbers).
But how come Disk Utility doesn't recognize the partition then? What should I do from here?
I couldn't find anyone asking this exact type of question or running into this same problem before, so I hope I'm not asking about something that's already been answered. If that's the case, if you could direct me to where I can find the answer I'd be appreciative.
Otherwise, any help or light that can be shed would be most appreciated.
Thanks!

The problem seems to have gone away. I did click on repair disk in Disk Utility, I'm not sure if that did anything, but now when I run Boot Camp Assistant it is showing me the correct free space, so I don't know what happened. Oh well.
Still having trouble getting the **** thing to partition, but that topic is covered extensively elsewhere.

P43NEO F - problems with booting up

Similar Messages

Maybe you are looking for