MacHALDriver.sys is corrupt?

With Vista Ultimate working (as well? as it could anywhere) in Boot Camp, I've been getting this message from Windows event logs & wonder if it matters?
Oops, maybe should have posted to Boot Camp
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
File Name: \Device\HarddiskVolume3\Windows\System32\drivers\MacHALDriver.sys

Thank you. I did not know there where different forums, no need for sarcasm.

Similar Messages

Corrupt SPLDR.SYS Windows 8.1 Pro 64-bit won't boot

Hi!
I'm running Windows 8.1 Pro 64-bit full Norwegian version bought at a local store. My PC consists of:
MB: Asrock Z97 Extreme4
Proc.: Intel i7 4790
RAM: 4 x 8 GB Crucial Ballistix Sport 1866Mhz 10CL
Video: Gainward GeForce GTX 770 4GB
SSD: Kingston HyperX SH100S3 240GB (system disk)
RAID5: 3 x Seagate Barracuda 7200.12 1TB + 1 x Seagate Barracuda 7200.11 1TB(configured using Intel RAID BIOS utility - only used for user files)
Optical: Lite-On IHOS104-37 + LG BD-R BH10
eSATA: Samsung Story Station Plus 1.5 TB (This had to be set as internal SATA drive in UEFI otherwise it refuses to wake up form sleep)
1394a: Lycom PCI-E PE-101
PS: Corsair HX750W
The optical drives are connected to the onboard ASMedia ASM1061 controller, the others to connectors controlled by the Intel Z97 chipset. I also have an M-AUDIO Firewire Solo external sound card connected to the 1394a expansion card. This is powered
by the Firewire bus and is occasionally a little "tricky". I believe it's because there is no driver available for Win 8 so I had to use the one for Win 7 64-bit.
This rig was set up about a month ago and has worked without any
serious problems except that I sometimes experience that the eSATA drive doesn't always wake from sleep.
All suggested updates has been installed.
My issue is this:
2 days ago I was installing a Silverlight
plug-in for Mozilla when I got a message that the installation routine couldn't update the registry and then the system
froze. After rebooting,
I was informed that Windows had become
corrupt. Attempting to run the
repair routine was no use - I just got
a message that Windows couldn't undertake
the repair. I suspected problems
with the system disk and started the
command prompt using the installation DVD.
It turned out that the C drive suddenly
had becomeE drive. The RAID "disk" showed up under the command prompt as C:\.
I ran bootrec (Sorry, I can't remember what parameter I used)
that reported that some errors were
repaired but that it couldn't repair everything.
Then I ran sfc offline.
In the srttrail.txt log file (that was written to the correct path on the E drive) I see that
SPLDR.SYS is corrupt and attempt
to repair failed (error code 0x2
and 0x490).
I was advised by a support engineer on the Microsoft Community forum to try and run chkdsk /p - which turned out to be an invalid parameter - and chkdsk /r which reported that everything was OK.
The support engineer suggested that I should perform a system restore from WindowsRE. This is what happened:
At first there seemed to be only one restore point available dated two days earlier but when I looked for more restore points there were 4 alltogether the oldest one dated 14 days earlier. I klicked the button "Look for the
affected programs" (or something like that - I've translated this from the Norwegian version I use.) and there were listed a lot of programs and utilities that had been installed on this disk before but not as long as it had been in
this rig! (I used this SSD as system disk in another PC earlier.) This is strange: when I installed the disk in my new rig I chose to repartition it and as far as I know that means that old data is erased. OK, I chose the newest restore point anyway
and klicked Next. In the following dialog there was a yellow exclamation mark and a list of two drives. Both drives were called Local drive (C:), the first one with (System) as well. Under Status on this first one it said "You
must enable system protection on this drive." Status of the second one was "Cannot find the drive" (Again translated from the Norwegian version.) The checkbox to the left
of both of the listings were greyed out and because I couldn't choose any of them, the Next-button was grayed out as well.
As I mentioned before the drives have chanched letters. When I use old DOS commands from the command prompt and switch from the X: drive (which seems to be the Windows installation DVD) to C: it shows the RAID I mentioned before. Likewise, the
system disk (i.e. the SSD I'm having trouble with) is now D:. And that sort of explains why the system recovery can't find the drive... But it doesn't explain why the old programs show up in the new restore points... (I've checked that the SSD
still is set to be boot disk in UEFI.)
The support engineer suggested that I post my query on the TechNet forum.
Do you have any suggestions what to do?
I'm a little nervous considering what could happen
with the files on the data disk if I make a mistake... :-)
Regards,
Morten Ericson

Hi!
Please read both this reply and the next one in conjunction.
I've done some research on my own after following your advices (Please look at my last reply below.).
First of all: bootrec /scanos does not report any Windows installations.
Running bcdedit /enum reports:
Windows Boot Manager
identifier: {bootmgr}
device: partition=D:
path: \bootmgr
description: Windows Boot Manager
locale: nb-NO
default: {default}
displayorder: {default}
timeout: 30
Windows Boot Loader
identifier: {default}
device: partition=D:
path: \Windows\system32\winload.exe
description: Windows 7 Ultimate
locale: nb-NO
recoverysequence: {db9ccd8a-43de-11e4-85a8-8169ad6c7c9f}
recoveryenabled: Yes
osdevice: partition=D:
systemroot: \Windows
bootmenupolicy: Standard
I must admit that I don't know how these things go together but there are a few things that makes me wonder:
First of all this has to be the reason why Windows 7 Ultimate comes up as the only option when I try to run System Restore. But is it really a Windows 7 installation? A lot of the files (logs and so on) in the Windows folder and subfolders are dated
mid August when I installed Windows 8.1. I just wonder...
I've been googling a bit about system installation and recovery and I read somewhere that there are some special precautions when installing Windows on a UEFI-based system. I can not remember that there were any options or warnings about that when
I installed Windows 8.1 on my system. But I belive I saw somewhere that a UEFI-based installation creates other partitions than an installation on an ordinary BIOS based system. The fact that the SSD has been used in a BIOS based system with Windows
7 Ultimate before explains in my mind why there is no reserved partition.
BTW: I don't know if this is important but the strings that were reported by the bootsect command were {e59cd65f-170a-42c4-927d-8ce8a94989a3} for the C:-disk and {cf240c96-43dc-11e4-85a8-806e6f6e6963} for the D:-disk.
Regards,
Morten

G72-b66US Notebook DVD RW AD-7586H cdrom.sys corrupt How can I download another

I have a
HP G72-b66US Notebook PC
with a hp DVD RW AD-7586H
cdrom.sys is corrupt.
How can I download another
cdrom.sys?

You may be infected, this file was a target of malware, scan your system.
Go here, download the software to another PC and make a boot CD or flash drive, boot from this on the problem PC and do a full system scan, remove anything it finds. When done, restart the PC

I keep getting blue screen and error message to remove this file from system. spooldr.sys

HP Officejet 4500 Wireless All-in-One Printer - G510n    w/operating system     Windows XP Professional
I installed the printer in February and the disk did not finalize the setup process. I went online and
down loaded the drivers and software that was offered from the HP website.
The printer works, but as the months have gone along, I keep getting updates for the printer and
the system needs to reboot and it does automatically.
Now I am getting a blue screen with a critical dump error message. HP error reporting keeps sending
the same message back to restore to earlier date before the updates. That worked for awhile. Now
HP Error system says that malware has corrupted and needs to remove system file     spooldr.sys
Is this in your driver software. Spooldr is the system that caches pages of data for printing in chronological
order....
Can I uninstall my software and drivers and change to the plain & simple, print and scan to prevent the
spool driver from loading to my system?

Thank you for your input. But, It is amazing that you can tell me that I was infected with rootkit.
Without information as to how to fix, your information is after the fact and useless.
I used the Safety Scanner provided to me by HP.  A full scan didn't detect any Malware in any files on my system. But the last screen dump provided the information that   spooldr.sys was corrupted and needed
to be removed.
Coming into HP Form, I did read on the HP website that my system Windows XP Professional was not listed
and noted that the software may have not been just what I needed. This was the reason for the question
about uninstalling and reinstalling less of the program. I really don't need my printer to print backward and
that is all I see that it is doing that other printers don't.
Besides, Kudos goes to the person from HP who sent the email, suggesting I used the HP Update software and drives recommended for my computer system. Computer, printer is working, back to normal and hasn't taken a dump since, I uploaded software and drives for Windows XP Professional.

Help with the Error "The file HPZius12.sys on HP CD is needed.. Please

I am working on my fiance's mother printer doing some testing as to why the printer will not communicate with her computer..
Her computer runs Windows 7.
The computer I am testing with runs Windows XP.
I am trying to install the drivers that I got from:
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=228&lc=en&cc=us&dlc=en&sw_lang=&product=31125...
for my Windows XP computer..
While during the installation.. I got the error "The file HPZius12.sys on HP CD is needed."
Well, she does not have the CD(Which is why I downloaded off the website).. But this error came up.. I downloaded the full package driver(About 340+ MB).
I can understand about this error coming up with a CD that may have been corrupted or something.. But How can I fix it if the Driver came straight from the HP site???
Can anyone help?

Hello countryboyofal,
It does seem as if the file HPZius12.sys is corrupted or missing. Check out the link below to resolve this issue. The directions are not for your exact printer, and are for a cd installation, but the concept should work all the same:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01047975&lc=en&cc=us&dlc=ru&product=3311754&lan...
Let me know if you need further assistance.
If I have helped in any way, just click the Kudos star on the left. Also, if your issue has been resolved, don't forget to select Accept as Solution

Config\system corrupted

I have a Satellite 5205-S503 which won't boot gets msg config sys error /corrupted. I can get to safe mode screen, but it gives me same error no matter what boot option I pick. I cannot get the BIOS screen to open and it will not boot off the factory recovery disks (Seems the boot option might be set for HDD only?) I have tried to boot with F2, F8, F12, 0 (ZERO) - in fact every F key and get the same safe modes option screen which no matter what I choose gives me the same error. I can access the HDD if I remove it and use an ext USB cable to another PC, altho it tells me there is disk errors (which running the scan & repair doesn't fix. Anyway I can get the correct config files and manually copy them to the HDD in the ext USB setup? Win XP SP3.

Satellite 5205-S503
I cannot get the BIOS screen to open and it will not boot off the factory recovery disks (Seems the boot option might be set for HDD only?) I have tried to boot with F2, F8, F12, 0 (ZERO)
Try the Esc key.
BIOS Setup / BIOS settings -- access instructions
-Jerry

BSOD controlling Nanotec servo (Labview+visa+Daqmx)

I'm using a set-up where I control a servo with Labview. I run the VI, set some speeds to the servo, and within minutes, Windows gets a BSOD. I would like to know the cause of the problem and a fix please.
What am I using?
- Windows 8.1 (and windows XP before)
- Labview Student Ed 2014
- NI Visa
- NI Daq mx
- USB to RS-485/422/232 Converter
- Nanotec servo
- Nanotec Labview example: http://en.nanotec.com/support/application-notes/labview-example/
What happens?
I open the VI, set the com port. Run the VI and set some motor speeds. Within minutes windows 8.1 gives a Blue Screen, with the error MULTIPLE_IRP_COMPLETE_REQUESTS. In Windows XP, this gave the error IRQL_NOT_LESS_OR_EQUAL. After rebooting, windows 8.1 shows Automatic Repair. 'Automatic repair couldn't repair your PC', and refers to C:\WINDOWS\system32\Logfiles\Srt\SrtTrail.txt.
This is 'Startup Repair diagnosis and repair log'. This gives some actions that take 0ms, untill finally:
Boot critical file c:\windows\system32\drivers\nipbcfk.sys is corrupt.
Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 8546 ms
Opening that file in notepad shows this: http://pastebin.com/dwp2X5er
Can anyone spot why Windows goes into a BSOD, and how this can be prevented?

It sounds like the installation of some NI drivers failed on your system. Can you please re-install those? I recommend to uninstall the current installed ones first.
Also, please try to install the latest driver versions. If you are using old drivers (e.g. from an out-dated driver DVD), it is possible that you have drivers installed which were never tested with Windows 8.1.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Mac only boots into Windows, then blue screen, then shuts down

I just got a new MacBook Pro in January (and this is my first Mac) and purchased Windows 7 to run on it. I've successfully run it since then, but just last week my computer froze and now when I try to restart it, it goes to the black "starting windows" screen and then immediately flashes to a blue screen for only a few seconds that says:
CACHE_MANAGER
If this is the first time you'v eseen this stop error screen, restart your computer. If this screen appears again, follow these steps.
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manfuacturer for any windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to selected Advanced Startup Options, and then select Safe Mode.
Technical Information:
* STOP: 0x00000034 (0x00000107, 0x00000420, 0x00000000, 0x00000000)
Collecting data for crash dump...
Initializing disk for crash dump...
Beginning dump of physical memory...
Dumping physical memory to disk: 100
I tried booting my computer up in safe mode, but it doesn't work - goes to the same blue screen and crashes. I also tried the "startup repair" tool, which did not find anything to repair, and the option to restore the computer to a previous time when it operated, but that didn't work either. I tried the memory diagnostic and it did not find any problems.
When I boot it up, I try holding down the option key, I only get the option to start up in the Windows partition of my drive. There is no option to start my computer using the Mac OSX drive. I think this is an issue with Windows, but I'm not sure if it could be an issue with my Mac operating system or hardware.
I appreciate any help someone can provide!

I'm suffering from the same bug, and I think it's related to Apple_HFS driver.
Here is what I have found in Minidump:
* Bugcheck Analysis *
CACHE_MANAGER (34)
See the comment for FATFILESYSTEM (0x23)
Arguments:
Arg1: 00000107
Arg2: c0000420
Arg3: 00000000
Arg4: 00000000
Debugging Details:
* WARNING: Unable to verify timestamp for AppleHFS.sys
* ERROR: Module load completed but symbols could not be loaded for AppleHFS.sys
* WARNING: Unable to verify timestamp for SiWinAcc.sys
* ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
EXCEPTION_RECORD: c0000420 -- (.exr 0xffffffffc0000420)
.exr 0xffffffffc0000420
ExceptionAddress: 00000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: VISTADRIVERFAULT
BUGCHECK_STR: 0x34
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LASTCONTROLTRANSFER: from 82ecec24 to 82f1ad10
STACK_TEXT:
9a1931b0 82ecec24 00000034 00000107 c0000420 nt!KeBugCheckEx+0x1e
9a193230 83089142 88473ea8 9a193274 000068a2 nt!CcPinFileData+0x258
9a1932a4 89212a4e 87208e20 00000000 000068a2 nt!CcPinRead+0xc6
WARNING: Stack unwind information not available. Following frames may be wrong.
9a1932dc 8921496d 87208e20 4ed8230c 00000000 AppleHFS+0x4a4e
9a193310 89214b68 87208e20 68a795a6 9a193340 AppleHFS+0x696d
9a193358 89215119 87208e20 9a193388 00000208 AppleHFS+0x6b68
9a193594 8921516f 872095b0 00000002 00000000 AppleHFS+0x7119
9a1937d4 892180b3 872095b0 00000002 9a193838 AppleHFS+0x716f
9a1938a4 892182c1 87792628 8720a6f0 8720a6f0 AppleHFS+0xa0b3
9a1938c0 82e7a4bc 86bf5a00 8720a6f0 8720a8c0 AppleHFS+0xa2c1
9a1938d8 8919ca56 13007228 86bf6748 8720a6f0 nt!IofCallDriver+0x63
9a193938 8919cc5b 86bf6748 8720a6f0 8720a8c0 fltmgr!FltpFsControlMountVolume+0x180
9a193968 82e7a4bc 86bf6748 8720a6f0 8720a8e4 fltmgr!FltpFsControl+0x5b
9a193980 891c9030 9a902742 8720a6f0 86bf58c0 nt!IofCallDriver+0x63
9a1939c8 82e7a4bc 86bf58c0 8720a6f0 82f74d80 SiWinAcc+0x1030
9a1939e0 82ff6015 82e0a870 86c98e20 82e0a900 nt!IofCallDriver+0x63
9a193a44 82eda424 86c98e20 87223a01 00000000 nt!IopMountVolume+0x1d8
9a193a7c 8307df5f 87223a48 9a193ba8 9a193b40 nt!IopCheckVpbMounted+0x64
9a193b60 8305f21f 86c98e20 a533d8a8 8721f008 nt!IopParseDevice+0x7c9
9a193bdc 8308528d 00000000 9a193c30 00000040 nt!ObpLookupObjectName+0x4fa
9a193c38 8307d5eb 00f4e018 8533d8a8 82fa7301 nt!ObOpenObjectByName+0x159
9a193cb4 83088ef6 00f4e030 00100180 00f4e018 nt!IopCreateFile+0x673
9a193d00 82e8144a 00f4e030 00100180 00f4e018 nt!NtCreateFile+0x34
9a193d00 773764f4 00f4e030 00100180 00f4e018 nt!KiFastCallEntry+0x12a
00f4f050 00000000 00000000 00000000 00000000 0x773764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
AppleHFS+4a4e
89212a4e ?? ???
SYMBOLSTACKINDEX: 3
SYMBOL_NAME: AppleHFS+4a4e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AppleHFS
IMAGE_NAME: AppleHFS.sys
DEBUGFLR_IMAGETIMESTAMP: 4b37c744
FAILUREBUCKETID: 0x34_AppleHFS+4a4e
BUCKET_ID: 0x34_AppleHFS+4a4e
Followup: MachineOwner
eax=82f7517c ebx=88473e00 ecx=0000001a edx=00000000 esi=82f67d20 edi=00000000
eip=82f1ad10 esp=9a193198 ebp=9a1931b0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
nt!KeBugCheckEx+0x1e:
82f1ad10 cc int 3
ChildEBP RetAddr Args to Child
9a1931b0 82ecec24 00000034 00000107 c0000420 nt!KeBugCheckEx+0x1e
9a193230 83089142 88473ea8 9a193274 000068a2 nt!CcPinFileData+0x258
9a1932a4 89212a4e 87208e20 00000000 000068a2 nt!CcPinRead+0xc6
WARNING: Stack unwind information not available. Following frames may be wrong.
9a1932dc 8921496d 87208e20 4ed8230c 00000000 AppleHFS+0x4a4e
9a193310 89214b68 87208e20 68a795a6 9a193340 AppleHFS+0x696d
9a193358 89215119 87208e20 9a193388 00000208 AppleHFS+0x6b68
9a193594 8921516f 872095b0 00000002 00000000 AppleHFS+0x7119
9a1937d4 892180b3 872095b0 00000002 9a193838 AppleHFS+0x716f
9a1938a4 892182c1 87792628 8720a6f0 8720a6f0 AppleHFS+0xa0b3
9a1938c0 82e7a4bc 86bf5a00 8720a6f0 8720a8c0 AppleHFS+0xa2c1
9a1938d8 8919ca56 13007228 86bf6748 8720a6f0 nt!IofCallDriver+0x63
9a193938 8919cc5b 86bf6748 8720a6f0 8720a8c0 fltmgr!FltpFsControlMountVolume+0x180 (FPO: [SEH])
9a193968 82e7a4bc 86bf6748 8720a6f0 8720a8e4 fltmgr!FltpFsControl+0x5b (FPO: [2,6,0])
9a193980 891c9030 9a902742 8720a6f0 86bf58c0 nt!IofCallDriver+0x63
9a1939c8 82e7a4bc 86bf58c0 8720a6f0 82f74d80 SiWinAcc+0x1030
9a1939e0 82ff6015 82e0a870 86c98e20 82e0a900 nt!IofCallDriver+0x63
9a193a44 82eda424 86c98e20 87223a01 00000000 nt!IopMountVolume+0x1d8
9a193a7c 8307df5f 87223a48 9a193ba8 9a193b40 nt!IopCheckVpbMounted+0x64
9a193b60 8305f21f 86c98e20 a533d8a8 8721f008 nt!IopParseDevice+0x7c9
9a193bdc 8308528d 00000000 9a193c30 00000040 nt!ObpLookupObjectName+0x4fa
start end module name
80bd0000 80bd8000 kdcom kdcom.dll Tue Jul 14 03:08:58 2009 (4A5BDAAA)
82e07000 82e3e000 hal halmacpi.dll Tue Jul 14 01:11:03 2009 (4A5BBF07)
82e3e000 8324e000 nt ntkrpamp.exe Sat Feb 27 08:33:35 2010 (4B88CACF)
83a2d000 83aa5000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 03:06:41 2009 (4A5BDA21)
83aa5000 83ab6000 PSHED PSHED.dll Tue Jul 14 03:09:36 2009 (4A5BDAD0)
83ab6000 83abe000 BOOTVID BOOTVID.dll Tue Jul 14 03:04:34 2009 (4A5BD9A2)
83abe000 83b00000 CLFS CLFS.SYS Tue Jul 14 01:11:10 2009 (4A5BBF0E)
83b00000 83bab000 CI CI.dll Tue Jul 14 03:09:28 2009 (4A5BDAC8)
83bab000 83be4000 dxgmms1 dxgmms1.sys Tue Jul 14 01:25:25 2009 (4A5BC265)
88e22000 88e93000 Wdf01000 Wdf01000.sys Tue Jul 14 01:11:36 2009 (4A5BBF28)
88e93000 88ea1000 WDFLDR WDFLDR.SYS Tue Jul 14 01:11:25 2009 (4A5BBF1D)
88ea1000 88ee9000 ACPI ACPI.sys Tue Jul 14 01:11:11 2009 (4A5BBF0F)
88ee9000 88ef2000 WMILIB WMILIB.SYS Tue Jul 14 01:11:22 2009 (4A5BBF1A)
88ef2000 88efa000 msisadrv msisadrv.sys Tue Jul 14 01:11:09 2009 (4A5BBF0D)
88efa000 88f24000 pci pci.sys Tue Jul 14 01:11:16 2009 (4A5BBF14)
88f24000 88f2f000 vdrvroot vdrvroot.sys Tue Jul 14 01:46:19 2009 (4A5BC74B)
88f2f000 88f40000 partmgr partmgr.sys Tue Jul 14 01:11:35 2009 (4A5BBF27)
88f40000 88f48000 compbatt compbatt.sys Tue Jul 14 01:19:18 2009 (4A5BC0F6)
88f48000 88f53000 BATTC BATTC.SYS Tue Jul 14 01:19:15 2009 (4A5BC0F3)
88f53000 88f63000 volmgr volmgr.sys Tue Jul 14 01:11:25 2009 (4A5BBF1D)
88f63000 88fae000 volmgrx volmgrx.sys Tue Jul 14 01:11:41 2009 (4A5BBF2D)
88fae000 88fb5000 pciide pciide.sys Tue Jul 14 01:11:19 2009 (4A5BBF17)
88fb5000 88fc3000 PCIIDEX PCIIDEX.SYS Tue Jul 14 01:11:15 2009 (4A5BBF13)
88fc3000 88fc4400 AppleMNT AppleMNT.sys Sun Dec 27 21:44:49 2009 (4B37C741)
88fc5000 88fdb000 mountmgr mountmgr.sys Tue Jul 14 01:11:27 2009 (4A5BBF1F)
8902d000 89107000 iaStor iaStor.sys Fri Jun 05 03:42:33 2009 (4A287809)
89107000 89110000 atapi atapi.sys Tue Jul 14 01:11:15 2009 (4A5BBF13)
89110000 89133000 ataport ataport.SYS Tue Jul 14 01:11:18 2009 (4A5BBF16)
89133000 8914a000 SI3132 SI3132.sys Wed Oct 03 20:41:04 2007 (4703E240)
8914a000 89170000 SCSIPORT SCSIPORT.SYS Tue Jul 14 01:45:55 2009 (4A5BC733)
89170000 89179000 amdxata amdxata.sys Tue May 19 19:57:35 2009 (4A12F30F)
89179000 89183000 msahci msahci.sys Tue Jul 14 01:45:50 2009 (4A5BC72E)
89183000 891b7000 fltmgr fltmgr.sys Tue Jul 14 01:11:13 2009 (4A5BBF11)
891b7000 891c8000 fileinfo fileinfo.sys Tue Jul 14 01:21:51 2009 (4A5BC18F)
891c8000 891cb100 SiWinAcc SiWinAcc.sys Fri Jun 15 02:02:27 2007 (4671D713)
89200000 8920e000 pcw pcw.sys Tue Jul 14 01:11:10 2009 (4A5BBF0E)
8920e000 89219e80 AppleHFS AppleHFS.sys Sun Dec 27 21:44:52 2009 (4B37C744)
8921a000 89223000 Fs_Rec Fs_Rec.sys Tue Jul 14 01:11:14 2009 (4A5BBF12)
89234000 89363000 Ntfs Ntfs.sys Tue Jul 14 01:12:05 2009 (4A5BBF45)
89363000 8938e000 msrpc msrpc.sys Tue Jul 14 01:11:59 2009 (4A5BBF3F)
8938e000 893a1000 ksecdd ksecdd.sys Tue Jul 14 01:11:56 2009 (4A5BBF3C)
893a1000 893fe000 cng cng.sys Tue Jul 14 01:32:55 2009 (4A5BC427)
8940c000 894c3000 ndis ndis.sys Tue Jul 14 01:12:24 2009 (4A5BBF58)
894c3000 89501000 NETIO NETIO.SYS Tue Jul 14 01:12:35 2009 (4A5BBF63)
89501000 89526000 ksecpkg ksecpkg.sys Fri Dec 11 05:04:22 2009 (4B21C4C6)
89526000 89553000 rdyboost rdyboost.sys Tue Jul 14 01:22:02 2009 (4A5BC19A)
89553000 89585000 fvevol fvevol.sys Sat Sep 26 04:24:21 2009 (4ABD7B55)
89585000 89596000 disk disk.sys Tue Jul 14 01:11:28 2009 (4A5BBF20)
89596000 895bb000 CLASSPNP CLASSPNP.SYS Tue Jul 14 01:11:20 2009 (4A5BBF18)
895c8000 89600000 e1e6032 e1e6032.sys Tue Mar 24 19:16:11 2009 (49C9236B)
89600000 89618000 sbp2port sbp2port.sys Tue Jul 14 01:11:28 2009 (4A5BBF20)
89618000 89628000 mup mup.sys Tue Jul 14 01:14:14 2009 (4A5BBFC6)
8962b000 89774000 tcpip tcpip.sys Tue Jul 14 01:13:18 2009 (4A5BBF8E)
89774000 897a5000 fwpkclnt fwpkclnt.sys Tue Jul 14 01:12:03 2009 (4A5BBF43)
897a5000 897e4000 volsnap volsnap.sys Tue Jul 14 01:11:34 2009 (4A5BBF26)
897e4000 897ec000 spldr spldr.sys Mon May 11 18:13:47 2009 (4A084EBB)
897ec000 897f4000 SiRemFil SiRemFil.sys Wed Jun 20 22:06:09 2007 (467988B1)
897f4000 897fc000 hwpolicy hwpolicy.sys Tue Jul 14 01:11:01 2009 (4A5BBF05)
8c813000 8c86d000 afd afd.sys Tue Jul 14 01:12:34 2009 (4A5BBF62)
8c86d000 8c89f000 netbt netbt.sys Tue Jul 14 01:12:18 2009 (4A5BBF52)
8c89f000 8c8a6000 wfplwf wfplwf.sys Tue Jul 14 01:53:51 2009 (4A5BC90F)
8c8a6000 8c8c5000 pacer pacer.sys Tue Jul 14 01:53:58 2009 (4A5BC916)
8c8c5000 8c8d3000 netbios netbios.sys Tue Jul 14 01:53:54 2009 (4A5BC912)
8c8ec000 8c8f2480 HIDPARSE HIDPARSE.SYS Tue Jul 14 01:50:59 2009 (4A5BC863)
8c8f5000 8c908000 wanarp wanarp.sys Tue Jul 14 01:55:02 2009 (4A5BC956)
8c908000 8c918000 termdd termdd.sys Tue Jul 14 02:01:35 2009 (4A5BCADF)
8c918000 8c959000 rdbss rdbss.sys Tue Jul 14 01:14:26 2009 (4A5BBFD2)
8c959000 8c963000 nsiproxy nsiproxy.sys Tue Jul 14 01:12:08 2009 (4A5BBF48)
8c963000 8c96d000 mssmbios mssmbios.sys Tue Jul 14 01:19:25 2009 (4A5BC0FD)
8c96d000 8c971900 ElbyCDIO ElbyCDIO.sys Fri Jan 01 18:20:32 2010 (4B3E2EE0)
8c972000 8c97e000 discache discache.sys Tue Jul 14 01:24:04 2009 (4A5BC214)
8c97e000 8c996000 dfsc dfsc.sys Tue Jul 14 01:14:16 2009 (4A5BBFC8)
8c996000 8c9a4000 blbdrive blbdrive.sys Tue Jul 14 01:23:04 2009 (4A5BC1D8)
8c9a4000 8c9b8a80 archlp archlp.sys Thu Aug 13 05:30:52 2009 (4A8388EC)
8c9b9000 8c9da000 tunnel tunnel.sys Tue Jul 14 01:54:03 2009 (4A5BC91B)
8c9da000 8c9ec000 intelppm intelppm.sys Tue Jul 14 01:11:03 2009 (4A5BBF07)
8de00000 8de85000 HTTP HTTP.sys Tue Jul 14 01:12:53 2009 (4A5BBF75)
8de85000 8dec0000 mrxsmb10 mrxsmb10.sys Sat Feb 27 08:32:21 2010 (4B88CA85)
8dec0000 8dedb000 mrxsmb20 mrxsmb20.sys Sat Feb 27 08:32:11 2010 (4B88CA7B)
8df12000 8df31000 cdrom cdrom.sys Tue Jul 14 01:11:24 2009 (4A5BBF1C)
8df31000 8df38000 Null Null.SYS Tue Jul 14 01:11:12 2009 (4A5BBF10)
8df38000 8df3f000 Beep Beep.SYS Tue Jul 14 01:45:00 2009 (4A5BC6FC)
8df3f000 8df4b000 vga vga.sys Tue Jul 14 01:25:50 2009 (4A5BC27E)
8df4b000 8df6c000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 01:25:49 2009 (4A5BC27D)
8df6c000 8df79000 watchdog watchdog.sys Tue Jul 14 01:24:10 2009 (4A5BC21A)
8df79000 8df81000 RDPCDD RDPCDD.sys Tue Jul 14 02:01:40 2009 (4A5BCAE4)
8df81000 8df89000 rdpencdd rdpencdd.sys Tue Jul 14 02:01:39 2009 (4A5BCAE3)
8df89000 8df91000 rdprefmp rdprefmp.sys Tue Jul 14 02:01:41 2009 (4A5BCAE5)
8df91000 8df9c000 Msfs Msfs.SYS Tue Jul 14 01:11:26 2009 (4A5BBF1E)
8df9c000 8dfaa000 Npfs Npfs.SYS Tue Jul 14 01:11:31 2009 (4A5BBF23)
8dfaa000 8dfc1000 tdx tdx.sys Tue Jul 14 01:12:10 2009 (4A5BBF4A)
8dfc1000 8dfcc000 TDI TDI.SYS Tue Jul 14 01:12:12 2009 (4A5BBF4C)
8f60e000 8f652000 usbhub usbhub.sys Tue Jul 14 01:52:06 2009 (4A5BC8A6)
8f652000 8f663000 NDProxy NDProxy.SYS Tue Jul 14 01:54:27 2009 (4A5BC933)
8f663000 8f66cd80 avc avc.sys Tue Jul 14 01:51:27 2009 (4A5BC87F)
8f66d000 8f678000 hidusb hidusb.sys Tue Jul 14 01:51:04 2009 (4A5BC868)
8f678000 8f68b000 HIDCLASS HIDCLASS.SYS Tue Jul 14 01:51:01 2009 (4A5BC865)
8f68b000 8f696000 monitor monitor.sys Tue Jul 14 01:25:58 2009 (4A5BC286)
8f696000 8f6ad000 usbccgp usbccgp.sys Tue Jul 14 01:51:31 2009 (4A5BC883)
8f6ad000 8f6b8000 mouhid mouhid.sys Tue Jul 14 01:45:08 2009 (4A5BC704)
8f6b8000 8f6c3000 KeyMagic KeyMagic.sys Wed Mar 18 22:00:24 2009 (49C160E8)
8f6c3000 8f6cf000 kbdhid kbdhid.sys Tue Jul 14 01:45:09 2009 (4A5BC705)
8f6cf000 8f6e1000 BTHUSB BTHUSB.sys Tue Jul 14 01:51:36 2009 (4A5BC888)
8f6e1000 8f745000 bthport bthport.sys Tue Jul 14 01:51:30 2009 (4A5BC882)
8f745000 8f769000 rfcomm rfcomm.sys Tue Jul 14 01:51:41 2009 (4A5BC88D)
8f769000 8f776000 BthEnum BthEnum.sys Tue Jul 14 01:51:35 2009 (4A5BC887)
8f776000 8f791000 bthpan bthpan.sys Tue Jul 14 01:51:43 2009 (4A5BC88F)
8f791000 8f7ac000 luafv luafv.sys Tue Jul 14 01:15:44 2009 (4A5BC020)
8f7ac000 8f7c6000 WudfPf WudfPf.sys Tue Jul 14 01:50:13 2009 (4A5BC835)
8f7c6000 8f7d6000 lltdio lltdio.sys Tue Jul 14 01:53:18 2009 (4A5BC8EE)
8f7d6000 8f7e9000 rspndr rspndr.sys Tue Jul 14 01:53:20 2009 (4A5BC8F0)
8f7e9000 8f7fb000 mpsdrv mpsdrv.sys Tue Jul 14 01:52:52 2009 (4A5BC8D4)
8f7fb000 8f7fdd00 MacHALDriver MacHALDriver.sys Sat Jan 16 07:13:08 2010 (4B5158F4)
8fc00000 8fc23000 mrxsmb mrxsmb.sys Sat Feb 27 08:32:02 2010 (4B88CA72)
8fc30000 8fc7b000 USBPORT USBPORT.SYS Tue Jul 14 01:51:13 2009 (4A5BC871)
8fc7b000 8fc8a000 usbehci usbehci.sys Tue Jul 14 01:51:14 2009 (4A5BC872)
8fc8a000 8fcb6000 1394ohci 1394ohci.sys Tue Jul 14 01:51:59 2009 (4A5BC89F)
8fcb6000 8fcce400 AnyDVD AnyDVD.sys Wed Jun 09 22:41:02 2010 (4C0FFC5E)
8fccf000 8fcd4280 GEARAspiWDM GEARAspiWDM.sys Mon May 18 14:16:53 2009 (4A1151B5)
8fcd5000 8fce2000 CompositeBus CompositeBus.sys Tue Jul 14 01:45:26 2009 (4A5BC716)
8fce2000 8fcf4000 AgileVpn AgileVpn.sys Tue Jul 14 01:55:00 2009 (4A5BC954)
8fcf4000 8fd0c000 rasl2tp rasl2tp.sys Tue Jul 14 01:54:33 2009 (4A5BC939)
8fd0c000 8fd17000 ndistapi ndistapi.sys Tue Jul 14 01:54:24 2009 (4A5BC930)
8fd17000 8fd39000 ndiswan ndiswan.sys Tue Jul 14 01:54:34 2009 (4A5BC93A)
8fd39000 8fd51000 raspppoe raspppoe.sys Tue Jul 14 01:54:53 2009 (4A5BC94D)
8fd51000 8fd68000 raspptp raspptp.sys Tue Jul 14 01:54:47 2009 (4A5BC947)
8fd68000 8fd7f000 rassstp rassstp.sys Tue Jul 14 01:54:57 2009 (4A5BC951)
8fd7f000 8fd8c000 kbdclass kbdclass.sys Tue Jul 14 01:11:15 2009 (4A5BBF13)
8fd8c000 8fd99000 mouclass mouclass.sys Tue Jul 14 01:11:15 2009 (4A5BBF13)
8fd99000 8fd9a380 swenum swenum.sys Tue Jul 14 01:45:08 2009 (4A5BC704)
8fd9b000 8fdcf000 ks ks.sys Tue Jul 14 01:45:13 2009 (4A5BC709)
8fdcf000 8fddd000 umbus umbus.sys Tue Jul 14 01:51:38 2009 (4A5BC88A)
8fddd000 8fdf6000 bowser bowser.sys Tue Jul 14 01:14:21 2009 (4A5BBFCD)
91a00000 91a11000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 01:12:47 2009 (4A5BBF6F)
91a11000 91a12700 USBD USBD.SYS Tue Jul 14 01:51:05 2009 (4A5BC869)
91a13000 91a14680 KeyAgent KeyAgent.sys Sat Dec 12 10:37:21 2009 (4B236451)
91a15000 91a16500 regi regi.sys Mon Apr 16 17:19:05 2007 (462393E9)
91a18000 91cba6c0 RTKVHDA RTKVHDA.sys Fri Sep 11 15:44:25 2009 (4AAA5439)
91cbb000 91cea000 portcls portcls.sys Tue Jul 14 01:51:00 2009 (4A5BC864)
91cea000 91d03000 drmk drmk.sys Tue Jul 14 02:36:05 2009 (4A5BD2F5)
91d03000 91d0d000 Dxapi Dxapi.sys Tue Jul 14 01:25:25 2009 (4A5BC265)
91d0d000 91d1a000 crashdmp crashdmp.sys Tue Jul 14 01:45:50 2009 (4A5BC72E)
91d1a000 91df4000 dump_iaStor dump_iaStor.sys Fri Jun 05 03:42:33 2009 (4A287809)
91df4000 91dff780 61883 61883.sys Tue Jul 14 01:51:27 2009 (4A5BC87F)
92000000 9201f000 HDAudBus HDAudBus.sys Tue Jul 14 01:50:55 2009 (4A5BC85F)
9201f000 9202a000 usbuhci usbuhci.sys Tue Jul 14 01:51:10 2009 (4A5BC86E)
9202a000 92b31fc0 nvlddmkm nvlddmkm.sys Sun Apr 04 02:37:04 2010 (4BB7DF30)
92b32000 92b33040 nvBridge nvBridge.kmd Sun Apr 04 02:21:35 2010 (4BB7DB8F)
92b34000 92beb000 dxgkrnl dxgkrnl.sys Fri Oct 02 02:48:33 2009 (4AC54DE1)
960e0000 9632a000 win32k win32k.sys Sat May 01 16:49:02 2010 (4BDC3F5E)
96340000 96349000 TSDDD TSDDD.dll Tue Jul 14 02:01:40 2009 (4A5BCAE4)
96370000 9638e000 cdd cdd.dll unavailable (00000000)
96390000 963dd000 ATMFD ATMFD.DLL Thu May 27 05:49:36 2010 (4BFDEBD0)
9ea2f000 9eac6000 peauth peauth.sys Tue Jul 14 02:35:44 2009 (4A5BD2E0)
9eac6000 9ead0000 secdrv secdrv.SYS Wed Sep 13 15:18:32 2006 (45080528)
9ead0000 9eaf1000 srvnet srvnet.sys Tue Dec 08 09:05:06 2009 (4B1E08B2)
9eaf1000 9eafe000 tcpipreg tcpipreg.sys Tue Jul 14 01:54:14 2009 (4A5BC926)
9eafe000 9eb4d000 srv2 srv2.sys Tue Jul 14 01:14:52 2009 (4A5BBFEC)
9eb4d000 9eb9e000 srv srv.sys Tue Dec 08 09:05:37 2009 (4B1E08D1)
9eb9e000 9ebc8000 fastfat fastfat.SYS Tue Jul 14 01:14:01 2009 (4A5BBFB9)
Unloaded modules:
8c8d3000 8c8eb000 parport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
91a13000 91a15000 BthKicker.sy
Timestamp: unavailable (00000000)
Checksum: 00000000
895bb000 895c8000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
8de27000 8df01000 dump_iaStor.
Timestamp: unavailable (00000000)
Checksum: 00000000
8df01000 8df12000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
8c8f3000 8c8f5000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
8c8d9000 8c8ec000 HIDCLASS.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
8c8d3000 8c8d9000 aiptektp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog2.txt
Please help, this a horror...

Win 7 x64 - Need to repair a single driver, but can't use System Restore

Basic Info - an HP/Compaq Elite 8200 Convewrtible Minitower with 2 extra SATA drives & a Creative SoundBlaster card installed.
Background: My system had begun going into Blue Screen (BS hereafter) every couple of days with a message that the BIOS was not "fully ACPI compliant." I contaced HP and was able to obtain & install the needed BIOS upgrade. Following this, I decided to do some housekeeping & checked for out-of-date drivers. I installed these one at a time, as I had a previous bad experience with updating too many drivers, particularly Intel chipset drivers, at a single time. When I finished the last update, which involved two drivers labeled IntStrA and IntStrB, if I recall correctly (I'm posting this from my PC at work, so I may have the names off by a character or so) my system began going BS after ~10 minutes or so. Nearly every BS referenced the MicroSoft system driver wdf01000.sys.
It is my belief that either wdf01000.sys became corrupted, or the last 2 updates were having a negative impact on the M S driver. Unfortunately, if I try to use System Restore to roll back the suspect updates, the system will BS ~1-2 minutes after the m essage "Restore is initializing" appears.
The only solution I can get from the HP Tech is to back up my data and then use the "Erase, Reformat & Reinstall" function from the Recovery Disks. Unfortunately, with a system that goes B S every 10 minutes, it is impossible to perform a reliable back-up for all 3 disks, while the Recovery Disk is only willing to back up my drive F:\, not my primary OS Drive, C:\ or my other drive, G:\ (the HP Recovery partition is drive D:\).
My questions are:
1. If the problem is a corrupted WDF01000.sys is it possible to obtain a reliable copy of & replace it? (The HP tech warned about the danger of obtaining a copy of a MicroSoft sysem file from the internet - a danger of which I was fully aware - but, isn't there at least one system in HP's possession running Windows 7 x64 professional? I should think a file supplied from HP would be sufficiently safe. However, when I raise the possibility with the tech, there is no response.)
2. If the problem stems from the last 2 Intel driver updates, is there a way to get a functional OS loaded from DVD that would peremit System Restore to run? My last system had Win 7 installed from MS media and, as I recall, once loaded, the use of System Restore was one of the repair options. The HP Recolvery disks only offer 2 choices - back-up (which would only cover drive F:\, with <10% of my 4+ years worth of data) or "Erase, Reformat & Reinstall." Following this course would put at risk ~90% of my data, not to mention the grief of reinstalling a great deal of software.
3. The HP tech tells me that, since Recovery is only willing to back up drive F:\, this is where the Recovered OS would be installed. This would give me the independently loaded OS I sought in question 2. However, I greatly fear that drive where recovery operated would be my primary OS drive, C:\. If this were the case, the result would be disastrous! I do have back-up via Carbonite, but I don't think this has been operating properly since the ACPI-related BSs began.
So -- any suggestions? Anything that gets me out of this problem without loss of data will be most sincerely appreciated!
Tom Filipi

Hello TomF,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that after running some updates your system is getting BSOD errors associated with the Windows file wdf01000.sys. Now I cannot claim to be able to get you a copy of that file. I am not sure just replacing it would resolve your issue anyways. I can do this for you I can tell you that first the HP Compaq 8200 Elite Convertible Minitower PC is a commercial product. You can do this at you may get more assistance by posting this on the commercial forums at Business PCs - Compaq, Elite, Pro.
Additionally, I would suggest you start your computer in Safe Mode and using an elevated command prompt run the command "SFC /SCANNOW". You can do this by right-clicking on the Command Prompt link and choosing Run as adminstator. Also, you can use chkdsk to run another repair on your files to see if they can be repaired.
The SFC /SCANNOW command will run the System File Checker to see if it can repair any corrupted system files where the chkdsk will do the same, but for ALL the files on your computer.
I am also providing you with resources on both below:
Use the System File Checker tool to repair missing or corrupted system files
Run Check Disk from a Command Line to Check for and fix Disk Errors
I hope this helps. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Windows 8.1 hibernation still not working for me properly

I see that this was already discussed in the past; but for me hibernation on Windows 8.1 still does not always work properly.
Link to previous question: http://social.technet.microsoft.com/Forums/windows/en-US/238ec268-a2dc-49ab-8a75-c185710e086a/windows-81-sleephibernate-issues?forum=w8itprohardware
I have Windows 8.1 64 bit Pro installed; I also have all updates installed. I can always hibernate my PC, but the problem is that on startup it sometimes wakes up properly with all launched applications "still running" (of course I understand that
they were not running while the power was off); but sometimes it fails to start up and go back to previous state and performs a clean boot instead. When it fails it seems completely random. I see no error messages. It is like after hibernation there is a 30%
probability that Windows will forget that it was hibernated and perform a clean boot instead.
I remember that Windows 7 as well as Windows 8 systems didn't have this issue; hibernation worked properly
always.... I like Windows 8.1, but this issue with hibernation is... well.... spoils the impression a bit.
I have a desktop PC with a "usual" hard drive and a SSD drive; Windows is installed on SSD drive. No UEFI support.
Plz help. Anyone knows how to solve this? I would really appreciate it.
P.S: I am not talking about sleep mode; I only discussing hibernation here. I hibernate PC because it is good for my workflow. I often have many applications opened and I like when they stay opened because starting them again and opening projects and documents
takes time.

Hi,
This issue can be caused if the Hiberfil.sys was corrupted or it was larger than the capacity of C drive, then System cannot boot properly from Hibernation.
Hiberfil.sys file is a system file that is used by Windows to support Hibernation. If you have enabled Hibernation in Windows 8.1, you will see this file.
I suggest we try to re-built this file to check the results:
powercfg.exe /hibernate off
powercfg.exe /hibernate on
Then, if possible, please make sure that there is enough space in your C drive for Hibernation.
Meanwhile, please upload the event log here for further research.
Collect event log:
http://windows.microsoft.com/en-us/windows7/what-information-appears-in-event-logs-event-viewer
Please upload them to a file sharing service like Skydrive or "Rapidshare" and put a link to them in your reply.
Look forward to your response.
Kate Li
TechNet Community Support

Windows 7 bootcamp Bsod and constant glitch

I am have the most frustrating week with my Windows 7 Partition on my 2010 Macbook pro Version 10.6.8
I sucessfully installed Windows 7 Ultimate with no issues using boot camp about 3 weeks ago. However, about one week ago I recieved the BSOD with the error pointing a finger at the MacHALdriver.sys
I have no fricking idea what that is after hours of research on the web.
This only happened 1 out of 3 times I turned on the machine. The other times there were no issues.
However, to make things worse, as of yesterday the entire system is very glitchy (Windows partition) and the tool bars or any windows that I have open flash and disappear for a few seconds. The Tool bar does not even appear unless I mouse over it.
As far as I am aware I have the most recent drivers for bootcamp installed.
Should I delete and redo the partition?
Can anyone please help me out?

perhaps this might go a way to giving an insight into your problem;
http://www.runscanner.net/lib/MacHALDriver.sys.html
i am not saying download anything, this is just for you to have a look at.
and this;
https://discussions.apple.com/message/7123009#7123009

This is a windows issue that people cant seem to help me with

I am a iMac owner but I have a Windows desktop I am trying to reformat for business use. When I go to reformat it after awhile I get 'serenum.sys is corrupted press any key to continue' then it all fails and I have to restart. can anyone help me out here?

Have you tried posting your question to a Windows forum?
http://www.windowsforum.org
http://forums.windowsitpro.com/
http://www.windowsbbs.com/

Windows 8.1 recurring BSoD (BAD_POOL_HEADER) with Bootcamp

Dump files - https://onedrive.live.com/redir?resid=5D2B2627890829C!462&authkey=!AGLwKEUk2zRCl eM&ithint=file%2c.zip
I just upgraded my Windows 8 Pro to Windows 8.1 Pro and have been getting these BSoD's as soon as I reach the start screen.
Had to restart several times just to get into one working section, but lately since 3 days I can barely even boot in.
The BSoD shows right in the middle of the boot screen.
I have tried reinstalling Windows, it didn't work.
I am using mid 2011 21.5" iMac with Bootcamp.
The dump files show its a problem with MacHALDriver.sys but I can't boot into Windows any longer, so can't disable the PnP driver.
Please help!

There may well be but it is years since I supported MS Windows.
Those two suggestions did not work, I would post your question on the Boot Camp forum.
Doing a web search it seems that this error is known but apart from the uPnP disabling which you cannot do I can find no other answer.
Try the other forum and hopefully someone there will be of help.

Windows 8.1 recurring BSoD (BAD_POOL_HEADER)

Dump files - https://onedrive.live.com/redir?resid=5D2B2627890829C!462&authkey=!AGLwKEUk2zRCleM&ithint=file%2c.zip
I just upgraded my Windows 8 Pro to Windows 8.1 Pro and have been getting these BSoD's as soon as I reach the start screen.
Had to restart several times just to get into one working section, but lately since 3 days I can barely even boot in.
The BSoD shows right in the middle of the boot screen.
I have tried reinstalling Windows, it didn't work.
I am using mid 2011 21.5" iMac with Bootcamp.
Please help!!

The minidump files showed a BAD_POOL_HEADER (19) stop error caused by the MacHALDriver.sys:
BUCKET_ID: 0x19_20_MacHALDriver+1714
Bootcamp.exe is the process that crashes.
Try the following link for suggestions for this problem:
https://discussions.apple.com/thread/4466080?start=0&tstart=0

Win XP installation fails after successful Parallels installation...

Hi:
I've been trying for the last several hours to install my new copy of Windows XP under Parallels (which bought, installed, and updated to Build 3188 earlier).
Here's what happens: I get to the final step of the "OS Installation Assistant" in Parallels, where it says to insert the Windows XP CD into the CD-ROM drive. I do so, click "Finish," and after a few moments, my Macbook's SuperDrive spits out the Windows CD (yeah, I know... ).
That's it.
Oh, the one time I got the Windows installation process underway, the installation quit, giving me the following error message: "File symc8xx.sys is corrupted. Press any key to continue." This was followed by "Setup failed. Press any key to restart your computer."
*ANY* help you good folks can offer will be greatly appreciated.
Bill in CT

Since Parallels is not an Apple product, you have better luck posting your question on the Parallels discussion forums rather than an Apple forum that focuses on compatibility issues between Macs and Windows:
http://forums.parallels.com

MacHALDriver.sys is corrupt?

Similar Messages

Maybe you are looking for