|
I get two specific BSOD errors on a regular basis. Right now I get the first one. 1 - A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe CACHE_MANAGER If this is the first time you've seen 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 manufacturer 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 select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x00000034 (0x0000000000000107, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000) *** ntoskrnl.exe - Address 0xfffff80002e78040 base at 0xfffff80002e08000 DateStamp 0x4fa38fe2 2 - A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: AppleHFS.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED If this is the first time you've seen 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 manufacturer 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 select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff88001201409, 0xfffff880031bd508, 0xfffff880031bcd70) *** AppleHFS.sys - Address 0xfffff88001210635 base at 0xfffff88001200000 DateStamp 0x4df65bd5 How on earth do I fix this? I was getting them all the time then suddenly they stopped for a few weeks, now I get them every time I boot up. I'm using a 15" MBP. 8GB Ram. 1TB drive, 1TB optibay, 2.66Ghz i7. 512mb nVidia chip. I've updated my drivers and still no dice. Any help? |
|
you have a Hard drive issue you can try running disk check a few times just to see if its a a small problem like a bad sector or some such thing how ever there is a good chance the HD needs replacing it can be related to disk not spinning good or responding fast enough .. this issue ntoskrnl.exe - Address 0xfffff80002e78040 base at 0xfffff80002e08000 DateStamp 0x4fa38fe2 Missing or corupted boot.ini file usually this one is related to AppleHFS.sys - Address 0xfffff88001210635 base at 0xfffff88001200000 DateStamp 0x4df65bd5 Corupt or bad video driver and Bootcamp volume Im un familar with this stuff but definatly related to the video driver and bootcamp .. Enjoy |
|
Okay have you tried going into safe mode of the version of windows that you are using to see if it might be a driver that might be causing your problem. An easy way of going into safe mode on your computer. When you turn on your computer monitor and the case. Quickly hit the F8 key or Function 8 on your keyboard. you might have to do this several times in order to get a screen which will give you some options of going into safe mode and safe mode with networking. Try with safe mode and networking options. Basically what this will do it will oad essential of loading the operating system itself. I have also done some quick searchest for the first part. Take a look at this. It is from a different forum. But also provides a solution for it that will help you out on your problem #1. http://www.sevenforums.com/crashes-debugging/23643-ntoskrnl-exe-bsod.html And in order to help you in part to.here is a tool for fixing it. http://www.pcmaxutilities.com/wikiexefiles/applehfs-sys-error-fix-guide.html Which version of windows are you using over there? You never mention if your using windows XP, Vista, Windows 7 or 8. Let us know if this helps There might be some other suggestions as well that some one could find if I have overlooked something here. driver is definatrly the cause of one of the problems almost for sure , the other is a bit more complicated cant find a boot .ini almost as if the boot sector is messed up or something it could be massed up Hard drive if it just happened suddenly out of no where.. if they are using boot camp what ever that is it is most defiantly now corrupt.. the details are limited here but from all my research it seems likely they are running XP this is where all the copmplates and question about the problem come from XP users running boot camp and related to nvida video driver If they are using Bootcamp would usually mean that they are using a version of windows on a Mac in most cases. Since bootcamp is like an emulator for Mac to run windows within Mac OSX. It's like WINE for Linux, or VMware for windows where you can install virtually an operating system on a windows Machine. thats what I thought :) like I said very unfamilar with it how ever AppleHFS.sys is a boot camp systems file so I guess they are running window on there mac Shrug The only way for me to boot is to boot in safe mode. It blue screens about 30 seconds after startup otherwise. It is my boot camp partition. I should probably mention that using a disk drive is out of the question. Well fr sure now that your mentioning it your running on a mac with bootcamp installed on it. (Not that I have anything against mac. I am running a mac Mini at home over here for learning purposes.) Take a look at the second link there are you able to still use Safari to get out onto the net to take a look at the second link there for applehfs.sys. You could download it and try and still go into afemode without the network runing and try and run that application to fix it via usb thumb drive. One of my main issues it that I can't boot from the Windows CD or a Windows Thumb drive.
showing 5 of 6
show all
|
|
You're far from alone. It's probably a bug or an over site. I would suggest some research. It's likely to be a pain in the neck as a lot of the solutions suggest using alternate non free software solutions. It's a bit of a can of worms but it's one of those things that may solve itself. |
Have you tried doing repair installs or rolling windows back?