E eirikb New member Joined Sep 8, 2015 Posts 1 Sep 8, 2015 #1 Hello, I am getting blue screens all the time after upgrading from Windows 7 to Windows 10 on my Imac. The questions: · OS - Windows 10 · x64 ? · What was original installed OS on system? Windows 7 · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail · Age of system (hardware) 4-5 years · Age of OS installation - have you re-installed the OS? Upgraded to Windows 10 in August · CPU Intel Core i5-2400S 2.5GHz · Video Card · MotherBoard - (if NOT a laptop) · Power Supply - brand & wattage (if laptop, skip this one) · System Manufacturer Apple · Exact model number: Imac 24" · Laptop or Desktop? Desktop I have attached the two files that were recommended. I am very thankful for any help. Regards, Eirik Attachments perfmon.zip 182.1 KB · Views: 2
Hello, I am getting blue screens all the time after upgrading from Windows 7 to Windows 10 on my Imac. The questions: · OS - Windows 10 · x64 ? · What was original installed OS on system? Windows 7 · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail · Age of system (hardware) 4-5 years · Age of OS installation - have you re-installed the OS? Upgraded to Windows 10 in August · CPU Intel Core i5-2400S 2.5GHz · Video Card · MotherBoard - (if NOT a laptop) · Power Supply - brand & wattage (if laptop, skip this one) · System Manufacturer Apple · Exact model number: Imac 24" · Laptop or Desktop? Desktop I have attached the two files that were recommended. I am very thankful for any help. Regards, Eirik
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,239 Location %systemroot% Sep 8, 2015 #2 Code: BugCheck 19, {20, ffffe0010f6b2350, ffffe0010f6b2410, c0c001d} Probably caused by : MacHALDriver.sys ( MacHALDriver+1714 ) One of your MAC OS drivers appears to be causing problems, I highly doubt that it is compatible with Windows 10, and thus leading to the BSODs your experiencing. Is this a dual boot system, or have you installed Windows on a Apple Mac completely? Code: 0: kd> lmvm MacHALDriver start end module name fffff800`3f760000 fffff800`3f76a000 MacHALDriver T (no symbols) Loaded symbol image file: MacHALDriver.sys Image path: \??\C:\Windows\system32\drivers\MacHALDriver.sys Image name: MacHALDriver.sys Timestamp: Thu Mar 17 08:31:31 2011 (4D81C6E3) CheckSum: 00015456 ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 The issue appears to be lie with how the operating system is handling pool allocations, the POOL_HEADER structure appears to be corrupt. This is possibly due to a incorrect release of memory. Code: 0: kd> dt nt!_POOL_HEADER +0x000 PreviousSize : Pos 0, 8 Bits +0x000 PoolIndex : Pos 8, 8 Bits +0x002 BlockSize : Pos 0, 8 Bits +0x002 PoolType : Pos 8, 8 Bits +0x000 Ulong1 : Uint4B +0x004 PoolTag : Uint4B +0x008 ProcessBilled : Ptr64 _EPROCESS +0x008 AllocatorBackTraceIndex : Uint2B +0x00a PoolTagHash : Uint2B The call stack: Code: 0: kd> knL # Child-SP RetAddr Call Site 00 ffffd000`239e7858 fffff801`9bc90fe8 nt!KeBugCheckEx 01 ffffd000`239e7860 fffff801`9ba66b45 nt!ExFreePool+0x320 02 ffffd000`239e7940 fffff801`9ba68471 nt!IopCompleteRequest+0x75 03 ffffd000`239e7a40 fffff800`3f761714 nt!IopfCompleteRequest+0x411 04 ffffd000`239e7b00 00000000`00000001 MacHALDriver+0x1714 05 ffffd000`239e7b08 00000000`c0000000 0x1 06 ffffd000`239e7b10 ffffe001`0f6eaac0 0xc0000000 07 ffffd000`239e7b18 00000000`00000000 0xffffe001`0f6eaac0
Code: BugCheck 19, {20, ffffe0010f6b2350, ffffe0010f6b2410, c0c001d} Probably caused by : MacHALDriver.sys ( MacHALDriver+1714 ) One of your MAC OS drivers appears to be causing problems, I highly doubt that it is compatible with Windows 10, and thus leading to the BSODs your experiencing. Is this a dual boot system, or have you installed Windows on a Apple Mac completely? Code: 0: kd> lmvm MacHALDriver start end module name fffff800`3f760000 fffff800`3f76a000 MacHALDriver T (no symbols) Loaded symbol image file: MacHALDriver.sys Image path: \??\C:\Windows\system32\drivers\MacHALDriver.sys Image name: MacHALDriver.sys Timestamp: Thu Mar 17 08:31:31 2011 (4D81C6E3) CheckSum: 00015456 ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 The issue appears to be lie with how the operating system is handling pool allocations, the POOL_HEADER structure appears to be corrupt. This is possibly due to a incorrect release of memory. Code: 0: kd> dt nt!_POOL_HEADER +0x000 PreviousSize : Pos 0, 8 Bits +0x000 PoolIndex : Pos 8, 8 Bits +0x002 BlockSize : Pos 0, 8 Bits +0x002 PoolType : Pos 8, 8 Bits +0x000 Ulong1 : Uint4B +0x004 PoolTag : Uint4B +0x008 ProcessBilled : Ptr64 _EPROCESS +0x008 AllocatorBackTraceIndex : Uint2B +0x00a PoolTagHash : Uint2B The call stack: Code: 0: kd> knL # Child-SP RetAddr Call Site 00 ffffd000`239e7858 fffff801`9bc90fe8 nt!KeBugCheckEx 01 ffffd000`239e7860 fffff801`9ba66b45 nt!ExFreePool+0x320 02 ffffd000`239e7940 fffff801`9ba68471 nt!IopCompleteRequest+0x75 03 ffffd000`239e7a40 fffff800`3f761714 nt!IopfCompleteRequest+0x411 04 ffffd000`239e7b00 00000000`00000001 MacHALDriver+0x1714 05 ffffd000`239e7b08 00000000`c0000000 0x1 06 ffffd000`239e7b10 ffffe001`0f6eaac0 0xc0000000 07 ffffd000`239e7b18 00000000`00000000 0xffffe001`0f6eaac0
U usasma Retired Admin Joined Feb 20, 2012 Posts 2,126 Sep 8, 2015 #3 Check this article to make sure that your system is compatible with W10 in BootCamp: https://support.apple.com/en-us/HT204990 The MacHALDriver dates from 2011, so I'd have to wonder if it's compatible w/Win10 I haven't been able to locate the driver download for BootCamp 6 - I suspect it's all automatically downloaded when installing W10 but will have to do more research to see
Check this article to make sure that your system is compatible with W10 in BootCamp: https://support.apple.com/en-us/HT204990 The MacHALDriver dates from 2011, so I'd have to wonder if it's compatible w/Win10 I haven't been able to locate the driver download for BootCamp 6 - I suspect it's all automatically downloaded when installing W10 but will have to do more research to see