Blue screen on windows using imac

When im on windows, after a while my screen freezes and it crashes and i get a blue screen. How do i fix it?

Are you able to post a photograph of your screen?

Similar Messages

Blue screen error "windows has recovered from a unexpected shutdown"

Hi guys
I am using laptop & everyday it will unexpectedly shutdown and shows Blue screen error "windows has recovered from a unexpected shutdown"...Pls help me to resolve this issue.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: 00000030
BCP2: 00000002
BCP3: 00000000
BCP4: 8F2DA8A5
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062614-23836-01.dmp
C:\Users\Venkateshwara swamy\AppData\Local\Temp\WER-74552-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

It could be some driver compatibility issues.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx
http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

MacBook Pro won't boot (question mark folder) after blue screen on windows bootcamp

Hi,
So, I was on windows, using bootcamp, and I was creating partitions on a pen drive with it, and then it asks me that it needs to restart to apply changes.
But then, while restarting, a blue screen occurred (**** windows).... And I forced the shutdown pressing the power key.
Then, I simply turned the MacBook on, trying to boot on my snow leopard and I got a flashing folder with a question mark on it.
Now I can't access any partitions on it, if I press option key on startup I get a blank window!
I tried to reset PRAM, repair the MacOs partition using the snow leopard DVD (it shows up fine, along with windows partition and EFI partition), and I still don't get my startup disk showing up...
How can I fix this? I can't loose my files and I need to work with it :/

I just fixed it!
For future reference, what I did was:
- Booting from OSX DVD, go to disk utility
- Erase windows partition (yap, I lost it...)
- Do a "repair disk" on every partition of my hard drive
- Restart
And it just worked ;)
Thankfully I had no important files on my windows partition, now I will just reinstall it.

Recurring Physical Memory Dump and Blue Screen on Windows 7

I recently built a PC and have been getting pretty frequent blue screens whenever I use it. Today I got about 5 within an hour and have finally tried to fix it. I got Windows Debugger and have analyzed the .dmp files and the most common one that I have gotten
is this one:
* Bugcheck Analysis
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800d062028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
STACK_TEXT:
fffff880`031dfb58 fffff800`0320ea3b : 00000000`00000124 00000000`00000000 fffffa80`0d062028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`031dfb60 fffff800`02da3463 : 00000000`00000001 fffffa80`0cc9f9a0 00000000`00000000 fffffa80`0cc9f9f0 : hal!HalBugCheckSystem+0x1e3
fffff880`031dfba0 fffff800`0320e700 : 00000000`00000728 fffffa80`0cc9f9a0 fffff880`031dff30 fffff880`031dff00 : nt!WheaReportHwError+0x263
fffff880`031dfc00 fffff800`0320e052 : fffffa80`0cc9f9a0 fffff880`031dff30 fffffa80`0cc9f9a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031dfd50 fffff800`0320df0d : 00000000`00000008 00000000`00000001 fffff880`031dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031dfd90 fffff800`03201e88 : 00000000`00000000 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031dfdc0 fffff800`02c8b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dfdf0 fffff800`02c8b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dff30 fffff880`053889c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
It looks like it's happening because of a system update I may have done? I'm not sure what to make of this or how to fix it.
Any help would be greatly appreciated.
Thanks

Mike
Virtual all of these are hardware related so I would start there. This type of crash is called a BCC124 and 99 times out of 100 it is hardware related.
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

My laptop become blue screen after windows logo, after i update the graphic ati and intel driver

I have constant blue screen after windows logo and i have updated all drivers. i was upset the blue screen didn't go away and i did the factory reset. For my suprise, it didn't solve the problem and then i repair it at the comp shop. it was installed with windows 7 home premium 64 (pavilion g4 1006tx) bit as the pre installed windows and activated with the key back on sticker. I updated all drivers and i noticed every time i update the ati and intel driver it will go blue screen after windows logo. after i uninstall it at in safe mode it can load normally. My question is there any solution for my graphic card or is it already damaged? or any other hardware problem? please because i have to use high graphic as i use photoshop

hii
make sure you download and update correct driver version of graphic
and know spec
more:
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-g4-Notebook-PC-series/5046252/model/5068...
try to instal "AMD High-Definition Graphics Driver" only
and uninstal "Intel High-Definition (HD) Graphics Driver"
Wisnu Suryandi

Blue screen in windows 7

I have been getting the blue screen after windows has been running for a while. Sometimes it happens when I am trying to install something. I have uploaded minidump files to the sky drive but I can't seem to read them, I tried copying and pasting them to
the desktop and opening them as notepad files but all I get is gibberish, at least it is to me. I need to know how to make these accessible to the pros so I can repair this problem. I have the Technical information from the blue screen here:
A clock interrupt was not received on a secondary processor within the allocated time interval.
*** stop 0x000000101 (0x0000000000000031, 0x0000000000000000, 0xFFFFF88002FD3180, 0x0000000000000003)
Don't know if this helps but there it is.
I am running Windows 7 P 64 bit desk top
Gigabyte MB GA-MA78Gm-S2H Rev 1.0
4GB Crucial Ballistix PC6400 800 Mhz 2Volt BL2CP25664A80A
AMD PHENOM 9750 2.4Ghz QUAD CORE
CPU temp was 32-34 degrees C last time I checked.
Disk error check was inconclusive ( I walked away and when I returned windows had loaded ) I assume this means that no errors were found.
RAM scanned and no errors were found.
https://skydrive.live.com/?mkt=en-US#cid=74B3C1D7DE3540EC&id=74B3C1D7DE3540EC!130

Alan
These worked but were inconclusive 0oease run driver verifier to pin down the misbehaving driver.
These crashes were related to memory management (probably caused by a driver).
Please run these tests to verify your memory and find which driver is causing the problem. Since this appears to be a driver I would start with driver verifier.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
1-Memtest. (You can read more about running memtest here)
2-Driver verifier (for complete directions see our wiki here)
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag

Skype causing Blue Screen on Windows 7

I just recently acquired a new computer and after installing Skype the second I log in it causes a blue screen of my computer. I tried a few times and the same happened everytime. Anyone else sharing this problem?

Blue screen on Windows 7? Wow. I've never managed to get BSOD on any of my Win7 PCs.
But what may cause this - no idea, really.
Добавляйте баллы, если моё сообщение вам помогло. Спасибо!
Возврат денег | Система обновления подписок | Заблокировали/взломали аккаунт? | Пропали контакты? | Не зайти в Skype/не добавляются контакты? | Не удалось загрузить базу данных?
Подписки | Цены

TS1367 I have MacOS 10.5.8. It is not booting. It stops at the blue screen. I used the disc utility - verify disc. I get the following message - Invalid sibling link. Volume check failed. Error: Filesystem verify or repair failed. Please give a solution a

I have MacOS 10.5.8. It is not booting. It stops at the blue screen. I used the disc utility - verify disc. I get the following message - Invalid sibling link. Volume check failed. Error: Filesystem verify or repair failed. Please give a solution anybody?

Many times I tried to simply update from 10.5.8 without any success. It starts and after few minutes ...
I used many different install disks (I bought ofiicial release from Mac seller), so I think this is not a problem with wrong version or bad install disk. A few days ago I've got back my computer from Apple technical support and technician told me he had this same problem with system installation

Windows 7 blue screen on Mid 2010 iMac running 10.8

I had previously had the 64 bit version of Windows 7 Home Premium running on my mid 2010 iMac running 10.7. However, after upgrading to 10.8, my Windows installation would blue screen after booting. I suspect this was due to upgrading to 10.8 as I didn't make any changes to my Windows install because I only use it for gaming.
I've since removed the Windows partition, and tried a clean install via the Boot Camp Assistant. Windows installs just fine and boots cleanly. However, after installing the Apple Boot Camp drivers (freshly downloaded during the Boot Camp Assistant process), Windows blue screens upon booting. I can repair the Windows install using the built in process, but any attempt to install Apple's drivers results in blue screening. I've tried a clean Windows install and redownloading Apple's drivers several times with no luck.
Does anyone else have any suggestions on how to resolve this problem? Thank you for your help!

I do see this. And I suspect Windows updates. Not Apple (though I would be the first to suspect those too).
iMac graphic drivers for Windows seem touchy and common. The April Windows monthly patch updates hit a few iMac users.
One person found that if they only did updates in smaller steps and not all at once they were fine.
Tuesday this week was another Patch Tuesday.
Games, heat, disk blocks, even RAM errors - one person recently we went round and round... bad blocks not heat, new disk drive and they were 100% stable and rock solid but was hard to rule out. Windows though is easier to test RAM and sectors. And Lion was not even aware or sensitive to those bad sectors and read errors OR RAM errors that Memtest clearly showed (run in OS X).
One person had upgraded RAM, low and behold the new DIMMs were just not fully pushed in and seated and making good contacts.
Try to rule out hardware. Maybe you stumbled on bad block being used now. Run chkdsk if nothing else.
And when updating or preparing to, run Registry cleaner in CCleaner first, Go To %TEMP% and remove everything there. Make a system backup image to another disk drive (NTFS) or with WinClone 3 (HFS, $20) or CampTune ($20).
Or it could just be uninstall one driver at a time, start with GPU, look at what was last installed. Windows drivers are not desireable for GPU. Get the one from AMD or Nvidia instead.

D20 Blue Screen loading Windows 7-64bit using Intel controller and Marvell enabled

Hi, Help,
Hardware:
D20, 4158, Four 500GB Seagate SATA drives configured as a RAID10 1TB virtual disk (partitioned into five logical drives).
Goal:
Recover or repair a degraded RAID array.
I want to be able to launch Windows 7-64bit using the Intel controller and have it access the virtual disk of the degraded RAID array attached to the Marvell controller. Subsequently, I want to use the Marvell MRU utility to repair/recover the situation.
Situation/Issue:
Things ran well for two years and two months until yesterday. Now, when booting I see:
1962: No operating system found. Press F1 to repeat boot sequence.
If I use the Windows 7 installation CD and load the Marvell driver, the attempt to recover the operating system reports that the MBR is corrupt and cannot be repaired.
If I boot with the Marvell controller disabled in the D20 BIOS, using a Windows 7 installation (with Marvell drivers) attached to the Intel controller, everything works except (of course) I cannot access the RAID drives.
If I reboot with the Marvell controller enabled, using the same Windows 7 installation via Intel controller, I see a "Starting Windows" announcement followed by a flash of the blue screen of death.
The BSOD message is unspecific, no error code, just...
"A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this Stop error screen,
restart your computer..."
Additional information:
If I access the Marvell BIOS (ctrl-M) and look at Devices, one of the four Seagate drives has status FREE instead of status ASSIGNED. If I run the Marvell BIOS verify disk utility diagnosic on that FREE status disk, I get a fault error after about 30 minutes of scanning. So, one Seagate disk is sour and somehow the MBR was corrupted at the same time.
History:
Two years ago, during the intial configuration, I could access the Marvell RAID disks from this Intel-controller-booted Windows 7 installation, but my fuzzy memory is that I had to change something in the D20 BIOS, such as the AHCI setting or similar.
Status:
Today, using the Intel controller to boot Windows 7 with the Marvell controller enabled is just BSOD. What am I missing or failing to do or set?
Thank you in advance for any help and ideas.
-John
Solved!
Go to Solution.

Update:
I replaced the 500GB Seagate disk with a new 500GB Seagate. I ran the Marvell BIOS verify disk utility on the new disk drive and it passed with no errors. Following the steps given in the Marvell MRU online help, I rebuilt the virtual disk. Upon completion (which took a little more than an hour to complete), I rebooted. Before the Seagate disk went south yesterday, the Marvell virtual disk contained one primary partition (C, and four NTFS drives (D:, E:, F:, and Z. Now it contains three primary NTFS drives (C:, F:, and Z. An extended partition contains D: (an unformatted volume of size 199.30MB) and an unused space of 199.30GB.
Event log:
Looking at the event log, Windows reports that the disk in question raised a warning yesterday. Three messages share the same timestamp (all from mv64xx (a Marvell process):
"Physical disk 16 is plugged out."
"Virtual disk 0 is degraded."
"Physical disk 16 is plugged in."
Eight seconds later, UserPnp logs:
"Driver Management has concluded the process to add Service disk for Device Instance ID SCSI\DISK&VEN_SEAGATE&PROD_ST3500418AS&REV_CC38\5&248BBE23&0&000100 with the following status: 0"
One second later, UserPnp logs:
"Driver Management concluded the process to install driver FileRepository\disk.inf_amd64_neutral_10ce25bbc5a9cc43\disk.inf for Device Instance ID SCSI\DISK&VEN_SEAGATE&PROD_ST3500418AS&REV_CC38\5&248BBE23&0&000100 with the following status: 0x0."
Questions:
Is it possible that UserPnp corrupted the Marvell virtual disk after an intermittent physical disk unplugged/plugged-in event that happened when the Seagate hardware went failed. It looks to me like my D: and E: are toast despite RAID 10.
Any ideas? Is there anyway to recover the Marvell virtual disk configuration to the state prior to the hardware failure? If not, what good is RAID 10?
My apologies for the long posting, but I am an old software guy who does not understand the intricacies of RAID and disk management.
Thank you in advance for any leads toward a solution,
-John

My computer running on Windows 7 blue screens often whenI use Firefox since I installed latets version

I have been using Mozilla for a long time. On one computer where I am running Windows 7, I suddenly started having problems after I downloaded the latest upgrade to Firefox 7.0.1 . not only does silverlight not work-always crashes, but firefox often (several times a day) stops responding and my computer blue screens. None of this was happening until this latest upgrade.
I am not currently sending this from my computer with the problem because I cannot get Firefox to open

Updating this thread...
I see some people talking about Forms 6i and SQL Plus crashing when connecting to a database:
APPCRASH Problem for plus80 and forms 6i builders
Forms Developer 6i will crash if you try connecting to a database running the AL32UTF8 character set. Older systems require the UTF8 character set.
Here are several very old threads with similar issues:
<p>connecting form 6i to oracle database 10G express edition
<br>Forms 6i X 10g Database (the solution is here)
More info: In Windows 7, I am running Forms 6i WITHOUT compatibility mode set to XP. It all seems to be running fine. I have had no problems with it since I first installed last year.
Unfortunately, I don't have an Oracle 11 database available to try connecting to. I have only used this setup with Oracle 9 and 10 databases.

Blue Screen on Windows 7 Boot

I repartitioned the hard drive on a computer running only Windows 7. This was done using non Windows utilities that have proven to be very reliable in the past. The utilities in question are all on the System Rescue CD and include (GParted, and
ntfsclone). Insofar as it appears to me that the software supplied by Windows will not allow any movement of partitions it is necessary to use other software for this purpose. There are many articles in this forum which indicate that such software
must be used for such partition management activity.
The affect of the repartitioning is that the primary partition that contains the Windows 7 operating system is now the third one on the drive rather than the second one. I was able to add an entry in the BCD for the boot manager to use to find the
new partition. The boot manager seems to work fine. It appears to me as though the Windows 7 boot loader (WinLoad.exe) does execute and the kernel is loaded. However, before there is any opportunity to interact with Windows the blue screen
occurs. On my computer you only see the blue screen error messages momentarily and then the computer reboots. This amounts to the deadly embrace. Is there some kind of setting that will allow me to learn what the error message says?
I have tried starting in "safe mode".
I'm pretty confident that the partition was moved correctly. In that, the new partition is an exact copy of the original. This technique is something that I've done repeatedly and works very well with Windows XP even though there are registry
updates that are necessary to complete the task. The difference being that Windows XP does boot satisfactorily which allows this to be done. What do I need to do to get Windows to boot successfully?

Hi,
Seems the PC is completely unbootable at this moment, I would suggest you use startup repair or the Last known good configuration under advanced startup options and check if it can bring the PC back to normal.
You can see guide in the link below
http://windows.microsoft.com/en-hk/windows/advanced-startup-options-including-safe-mode#1TC=windows-7
Regards
Yolanda Zhu
TechNet Community Support

Photoshop CC and 2014 spot healing brush tool causing blue screen on windows 8.1

Hi,
The problem is when I'm using spot healing brush tool soon as apply it it causing fatal error on my windows. I have all suite up to date.
please advice.

First thing to do is check you have all the latest device drivers for all your devices and all windows 8 updates. Printer drivers, Display Drivers, Network drivers etc. It is not possible for an Application program like Photoshop.exe to cause a Blue Screen. However Applications use devices and device drivers are able to do things application programs can not do.

FB 4 crashed to blue screen on windows - what to do?

issue: when i am installing flash builder 4 to system - at step of installation where it calculates required time before placing files - it crashes to blue screen of OS.
version of flash builder 4 trial downloaded today from Adobe.
system configuration very shortly:
windows xp sp3+++
proc: Intel Core2 Duo E8400 3 GHz
motherboard: MSI P41T
Ram 2 GB
I can make small dump of memory, it display some wrong memory read in win32k.sys
Where to search for source of issue?
I cant find in google..
Thanks

Thanks for reply.
i am using other Adobe software like Adobe CS4 package, and it installed and works correctly.
so this issue with crash to blue screen is only with this installation of Flash Builder.
I may will try to install some previous version of FB ,
ps.
I am using Comodo internet security premium as anitivirus

Can't get past blue screen on Windows partition

I have been using bootcamp for a little over a month now. It had been working great. But suddenly today, Windows will not boot up- It stays on a blue screen, and gives me options to restart (which does nothing) and Advanced Options (which none of the methods help)- and basically it won't start up.
That makes me wonder, if there is anything I can do to fix the problem- or must I delete the bootcamp partition, and then start all over again? Good news is that my Windows 8.1 is the Full version, and not an OEM version.
Thanks for any advice

My mistake, Safe Mode disables DVD player...
Perhaps re-installing 10.5.8 Combo Update while in Safe Mode might help.
-mj

Blue screen on windows using imac

Similar Messages

Maybe you are looking for