Windows Vista Blue Screen on Startup

I have an iMac 21". I've installed Windows Vista 32bit and Boot Camp 3.0 as directed, however I keep getting a blue screen whenever Windows starts. It's hard to read it since the computer restarts so quickly, but I have the dump files from the blue screen if anyone needs them. Also, my eject button won't work on my Apple Wireless Keyboard even though Boot Camp installed the keyboard driver.

OK. Installed Boot Camp 3.1 and most of my problems seem to be solved except there is an odd hesitation in the sound at startup. The Windows startup sound doesn't play. But by the time the desktop comes up, the logon chime sounds. Slow drivers?

Similar Messages

Windows 7 blue screen on startup

Hello! I've been getting this bluescreen at random intervals whenever I start my computer up. I have a dump file here: https://www.dropbox.com/s/7jet80znrfpqznu/022714-14445-01.dmp and have tried googling the issue, but nothing seems to work.

These crashes were related to memory corruption (probably caused by a driver).
Please run this test to find which driver is causing the problem.
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.
Driver verifier (for complete directions see our wiki here)
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag

HT1349 I have icloud on my pc with windows vista. Recently, upon startup I receive an error that says applephotostream.exe has stopped working. Windows will close this problem . . . any suggestions. I tried to download the control panel again. no luck

I have icloud on my pc with windows vista. recently, upon startup I get a message that says applephotostream.exe has stopped working. Windows will close this program . . . I tried re-installing the icloud control panel, etc. to no avail. any leads?

Hi, I have the same problem. Has anyone come forward with any advice on fixing the problem?

IMac G5 running OS 10.4.11. Started playing with a bluetooth speaker (may or may not be related). Now I cannot get past the blue screen on startup. I can get into safe mode. Tried install disc for disc utility and reloaded OS. Still get blue screen.

I have an older iMac G5 running OS 10.4.11. The other day I started playing with a bluetooth speaker (may or may not be related). Now I cannot get past the blue screen on startup.
I can get into safe mode. But no regular startup.
I tried disabling bluetooth, thinking that might be related. It didn't help.
I even tried using the install disc to run disc utility. That didn't work so I reloaded the OS.
But I still get hung on the blue screen when trying a normal startup.
All help would be appreciated.

Try resetting the PMU/SMU and PRAM/NVRAM. You'd need to identify the mode of resetting depending on the model of your G5 iMac. The Apple support sites that would help you for this are –
http://support.apple.com/kb/HT1436
http://support.apple.com/kb/HT1939
http://support.apple.com/kb/HT1767
http://support.apple.com/kb/HT1379
I hope this solves your problem.

"blue screen" at startup- still stuck!

So for some reason or another, I've ended up with the "blue screen" at startup problem. when I start my macBook in Leopard, after the apple logo, I get stuck permanently at a blue screen. The first thing I did was to repair the disk but the disk utility told me my disk was fine. Then I tried to do a restore of Mac OS X but after about a minute I get a error message saying "Restore Failure could not restore- File Exists". I have no idea how or why this happened or what it means. I would like to try apple's solution to the problem but they are very vague. They say try an "Archive and Install installation of Leopard". I have no idea how to do that! They say it is covered on "page 7 of the Install & Setup Guide included on the Leopard DVD" but I can't seem to find this so-called "Install & Setup Guide" anywhere on either of the two DVDs. Can anyone tell me how to fix this?

It's all in http://support.apple.com/kb/HT1545?viewlocale=en_US BTW, the setup guide's on the Leopard installation disk (retail version) and not on the disks that came with your machine.

Blue screen at startup---have tried EVERYTHING!!! Any ideas???

Hi there, I've got a really frustrating problem concering my husband's iBook G4. One day he got home from work, tried to start up, and got only a blue screen (no cursor.) (This is shortly after updating to 10.4.11, incidentally...coincidence?) We went to the forums, and tried numerous fixes, including:
Booting from install and running disk repair (none needed)
Booting in target disk mode with my mac and removing the login.plist file
Removing all login items from both user accounts in target mode
Attempting a boot (and eventual restore) from the external firewire backup, but it won't get past the blue screen here, either.
It started up in safe mode a couple of times, and even restarted in normal mode once, but then in primary account froze back up after a few minutes. Then it wouldn't even start in safe mode.
Then we did an Archive & Install from the original startup (Panther) but when it got to the login screen, it wouldn't accept either user password (even though the hint indicated we were using the right ones) and then froze. It now won't even boot from this disk, or start up in safe mode.
Everything seems to be intact while perusing it in target disk mode; even ran a hardware test from the Apple Hardware Test disc and that all checked out (no idea if this would have made any difference, but I'm grasping at straws, here!)
I know we did a couple more things suggested in the forums/support pages, but I can't remember what they are at this point...my brain is fried! (Also remember following Apple's instruction's for what to do when you get a blue screen at startup...tried this first thing to no avail.)
Soooooo...any suggestions or ideas? We would greatly appreciate the help!
Thanks so much!
Jennifer

Hi Jennifer,
Ok, so...what's going on today is that Leopard will open to the login screen (sometimes I can log in but generally not), but then the cursor is frozen, as is the keyboard (can't type to login or use shortcuts) and even a usb mouse doesn't work. The only thing I can do is power down with the off button, and upon restarting, if I get past the login, get the message "Computer was restarted after Mac OSX quit unexpectedly" or something like that. (Just restarted from frozen login screen and got blue screen again.)
Wondering if it's Leopard or my wonky install (we started up in target mode, with the install disc in the drive, and opened the installer on my mac, then chose the broken mac hd to install to. Seemed to work, but may this be related to the driver issue you mentioned?) We did it this way (after doing a zero-out erase) because it wouldn't even start up from the install disc itself.
It sounds to me like this method of installing is okay. If you did not have the correct drivers, you could never get as far as you do in Leopard. I am wondering why you install with the disk in your Mac and not in the iBook.
Anyway, have reset the PRAM, still no luck. On the apple page regarding this procedure they mention a power management unit reset for ibooks...would this correspond at all to our problems? Is it something I should try or steer clear of?
Okay. Resetting PRAM was a long shot, but worth trying. I would steer clear of trying to reset PMU. That is related to sleeping, waking and such things and your problems do not seem to be related to that. Also, I have never reset PMU, but from what I recall, it sounded a bit tricky.
Am now attempting to reboot from backup. And yes, when I open Startup Manager, the internal hard drive DOES show up. If that means anything. Have a bootable backup (created with SuperDuper) which also shows up, but when I try to start up with it, I get stuck at blue screen (still.)
As far as the iBook hard drive is concerned, this is a good sign. I am thinking that perhaps the hard drive is okay and the problem is something else.
So, since the iBook originally came with Panther, and Leopard is really yet another unknown to throw into the loop, if I do another erase/install, I'm thinking Panther is the way to go? (Unfortunately we shared a family pack Tiger with a friend, and haven't got a hold of that install disc yet, otherwise I'd try Tiger, since it's what it was running and so is what the backup is, too.)
From what I have seen in the forums, when people are having startup problems, the last resort solution usually works. That is, they take the install disk that came with the machine (Panther in your case), erase and zero out the hard drive and then re-install. That usually seems to do the trick. What they have probably done is either replaced some corrupted piece of software or fixed a directory problem on the disk. In your case, you have already done most of this except not with the Panther disk. So, I think it is worth going through this effort with Panther. If this actually worked, then you could worry about how to update your software to where you want it to be. If it does not work, I would consider this more evidence that there is probably a hardware issue.
If this doesn't work (and would probably have to try in target mode again if the install disc won't open...) should I buy Tech Tool or Disk Warrior or just send it in for repair? I suppose there's a point at which I'll have to admit defeat!
Not sure that I caught this before. You imply that the install disk will not open if it is inserted into the iBook. Is this a problem that showed up when the blue screen business started? When you insert the disk into the iBook and then reboot that computer from the disk (pressing the C key during startup), do you get something on the desktop?
If, when repairing the hard drive with Disk Utility, you had received a message that the disk was not repaired, then a stronger utility would be a reasonable choice. But, that does not seem to be your situation. So, if it were me, I would probably not buy Tech Tool or Disk Warrior at this point. I do think that it is possible that these utilities might be able to do more troubleshooting than you can do with Disk Utility and the Apple hardware CD. Tech Tool in particular has some hardware testing capability. So, if money were no object, you might buy that and see if it can give you more detailed diagnostic information. Of course, these are purely my opinions. I could be totally wrong on any of this.
Oh yeah, I don't know if I mentioned this earlier or not but all the restarts yesterday were accompanied be a brief "whooshing" sound (like a fan) for a second or so, and once I got both that sound and a "boooooop" issuing from the innards. Not sure if this means anything or not, but thought I'd mention it. Maybe the hard drive is melting! (Also I get further along the startup route after it's been turned off for a while.)
This is worth mentioning and I overlooked it in your previous posts. The "booooooop" sound got my attention. When the computer is started up, one of the first things that is done is that there are some hardware tests performed. Apple does use some sounds to indicate certain problems. You can learn a little more at You hear "breaking glass" or "musical beeps" when you turn on your Mac. I don't know if you are hearing one of these sounds or if they are unrelated. But, I think that the "boooooop" sound in particular might be trying to tell you something.
Let me sum up my opinions (which could be dead wrong). I still suspect a hardware problem. However, maybe the hard drive is okay. I think it would be worth using the Panther CD to do another erase and install on the iBook. If you still do not have a working computer, it is probably time to seek professional help. (However, if you get to this point, it is conceivable that you could be having some problems with your RAM chips. If you have worked with RAM chips before, you could try to play games with them: reseating them and removing them one by one- if you have two chips. But, if you have not done this before and are do not have some familiarity with working on hardware of this nature, perhaps you should just leave this alone.)
If you need to seek some professional help, you might be able to try one of these options - If you have AppleCare, you should definitely give them a call. If you live close enough to an Apple store, you could take your computer to the genius bar and see if they can help.
Sorry that you are having such a hassle,
Rich

SB Live ! 24 bit external USB and windows seven blue screen

;SB Li've ! 24 bit external USB and windows seven blue screen+ hi! i have installed windows seven 64 bit build 7600 RTM on my PC and i wanted to install also my USB sound card which is SB Li've ! 24 bit and i downloaded the beta drivers from creative. instalation was really fast and smooth but at the end i've got a message that the program has stopped to response and i have closed it. i did a system reboot and i have seen that the sound card has been installes succesfull and also the control panel. Sound was clear and really nice, all worked fine but sometimes im getting a blue screen on my windows with a code STOP 0x000000E and then a file named usbuhc.sys was the problem. i think that the sound card is the thing that is doing the blue screen becouse i have only a keyboard, mouse and the sound card SB Li've ! installed as USB.
Is it normal that i have those troubles on my PC ? is it my sound card my windows seven problem ? what should i do now ?
at the moment i have turned off the sound card so i will see if i get a blue screen or not.
thanks for any reply

? yes, i have also tried to download the beta drivers again and re-install them but i have still the same problem :/ it happens in a different time, sometimes after hour or sometimes after 0 hours when my computer is turned on. my system is mostly turned on becouse im downloading some stuff so it is running all the day, sometimes im surfing websites but its nothing special. I really dont know what to do :/@83.30.93.77

I see a blank blue screen at startup

I see a blank blue screen at startup. Am I going to lose everything that I didn't backup?

So I booted off the install disc (hold C at startup), did an archive and install) and then shut it down. Powered it up and zapped the PRAM at startup (commandoption+PR) and it now boots instantly. Just curious as to what video card you have in yours? I've been reading a lot of threads about problems caused by the ATI Radeon HD 2600, which is what I have in mine. Sounds as if a firmware update is needed, but not yet available. I also had 4 kernel panics in my first 20 starts. Apple Genius Bar said this was due to Symantec Anti-Virus for Mac.

'Famous' blue screen at startup AND safe mode boot failure

Dear all,
Two days ago, after installing the new Java update/airport update and restarting, I encountered a 'blue screen' on startup after getting past the mac symbol and swirling cog. I cannot say whether the updates were the cause (doubtful) of if my cheap USB mouse that was still plugged it caused it or whether i have the dreaded 'bad sectors.' The cause aside, here is what i've tried to fix the issue:
1) Disk Utility - Verification (OK'd) and Repairs (fine)
2) Disk Utility - Verification of Permissions (a few needed to be done) All repaired
-blue screen-
-Restart after period-
3) Rebooting in safe mode, removing startup items from the login items settings menu
4) Removing startup items from System/Library/StartupItems folders
5) Remove airport extensions (recent - date modified in list view)
(NB - safe mode i could say my desktop perfectl in original form and all files!)
-Restart-
-no longer able to start in safe mode-
-blue screen remains-
6)Single User mode -
resetting preference files (loginwindow.plist and windowserver.plist)
Finally system profiler from Tiger DVD states:
*Permissions repaired
*Dependency errors: com.apple.iokit.IOUSBFamily & com.apple.kernel.iokit no valid version found
*Integrity: kext has no receipt
I backed up most my data from the LAST crash, but recent music/1000 photos and others have been backed up altho i've been meaning to! Help!
I'M PANICKING now can no longer get in SAFE MODE!!
Please help Mac911!!!!
Charlie
G3 iBook 800mhz Mac OS X (10.4.6)

Update:
So, I managed to do ALL that you said, EXCEPT, the reboot and work fine business.
I created the admin account which works fine. So now I can see three user accounts (looks like there as already an admin type one).
The one I created works fine, only, I can only access/see the login screen through a safe boot, (otherwise blue screens...) . I can get into the admin account fine, but when restarting and logging in as my original user account it won't boot. Something is very wrong in MY user account. I think at this point my data there is still retrievable somehow for a backup, clean start. but i haven't reached that point yet.
Anyone have any clues what migt have caused the error in my user login?
One of the things I tried (too hastily now i admit) first was to remove the recently added updates from the extensions folder. has this exacerbated the problem? Can i put them back without logging in as me??
remember from my first post system profiler says software/extensions integrity 'kext has no receipt' and dependency errors: 'com.apple.iokit.IOUSBFamily and com.apple.kernel.iokit; no valid version found' - whereas in my newly created admin account it appears AOK.
is this the source?
any ideas anyone?
sorry lots of queries here but i am ever hopeful.....
All yours,
Charlie
G3 iBook 800mhz Mac OS X (10.4.6)

Windows 7 (64) blue screen on startup

Hi,
I went to turn on my computer today (Toshia qosmio x505-q880) and everything seemed normal until about halfway through the startup process I received a blue screen error. I can boot in safe mode, but I can't figure out whats causing this problem.
Here is the error message that I get when I boot into safe mode.
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7600.2.0.0.768.3
  Locale ID: 1033
Additional information about the problem:
  BCCode: 51
  BCP1: 0000000000000001
  BCP2: FFFFF8A000024010
  BCP3: 000000000156B000
  BCP4: 0000000000000374
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1
Files that help describe the problem:
  C:\Windows\Minidump\090710-8065-01.dmp
  C:\Users\Matt\AppData\Local\Temp\WER-16910-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
Problem signature:  Problem Event Name: BlueScreen  OS Version: 6.1.7600.2.0.0.768.3  Locale ID: 1033
Additional information about the problem:  BCCode: 51  BCP1: 0000000000000001  BCP2: FFFFF8A000024010  BCP3: 000000000156B000  BCP4: 0000000000000374  OS Version: 6_1_7600  Service Pack: 0_0  Product: 768_1
Files that help describe the problem:  C:\Windows\Minidump\090710-8065-01.dmp  C:\Users\Matt\AppData\Local\Temp\WER-16910-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

Also this is what I get when I use my crash reporter.
Seems to keep pointing to some WerFault.exe and Wer.dll
Version=1
EventType=BlueScreen
EventTime=129283576105180317
ReportType=4
Consent=1
UploadTime=129283576484580156
ReportIdentifier=79710af8-baad-11df-a1bc-c80aa96bb319
IntegratorReportIdentifier=090710-8065-01
Response.type=4
Response.AnalysisBucket=X64_0x51_nt!HvpSetRangeProtection+8fae8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=51
Sec[1].Key=BCP1
Sec[1].Value=0000000000000001
Sec[2].Key=BCP2
Sec[2].Value=FFFFF8A000024010
Sec[3].Key=BCP3
Sec[3].Value=000000000156B000
Sec[4].Key=BCP4
Sec[4].Value=0000000000000374
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service Pack
Sec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=768_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=366D14228723C1834DCC14382AED3B0B;BID=OCATAG;ID=5fed2613-7bb3-46f3-b4fc-0915969aa15d;SUB=9//8//2010 8:27:22 AM
File[0].CabName=090710-8065-01.dmp
File[0].Path=090710-8065-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\090710-8065-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-16910-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\Matt\AppData\Local\Temp\WER-16910-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERDE8B.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\Matt\AppData\Local\Temp\WERDE8B.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
Version=1
EventType=BlueScreen
EventTime=129283576105180317
ReportType=4
Consent=1
UploadTime=129283576484580156
ReportIdentifier=79710af8-baad-11df-a1bc-c80aa96bb319
IntegratorReportIdentifier=090710-8065-01Response.type=4Response.AnalysisBucket=X64_0x51_nt!HvpSetRangeProtection+8fae8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033UI[2]=C:\windows\system32\wer.dllUI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=CancelUI[8]=Windows has recovered from an unexpected shutdownUI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.
UI[10]=CloseSec[0].Key=BCCode
Sec[0].Value=51Sec[1].Key=BCP1
Sec[1].Value=0000000000000001
Sec[2].Key=BCP2Sec[2].Value=FFFFF8A000024010
Sec[3].Key=BCP3Sec[3].Value=000000000156B000
Sec[4].Key=BCP4Sec[4].Value=0000000000000374
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service PackSec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=768_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=366D14228723C1834DCC14382AED3B0B;BID=OCATAG;ID=5fed2613-7bb3-46f3-b4fc-0915969aa15d;SUB=9//8//2010 8:27:22 AM
File[0].CabName=090710-8065-01.dmp
File[0].Path=090710-8065-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\090710-8065-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-16910-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\Matt\AppData\Local\Temp\WER-16910-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERDE8B.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\Matt\AppData\Local\Temp\WERDE8B.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe

Sporadic blue screen on startup in windows 7

i get a blue screen on start up once or twice a month with no pattern found. Will start up fine if restarted.

would recommend system restore, probably an issue with an add-on..

Windows 7 Blue Screen - Random Shut Down

I'm having problem with my Toshiba Satellite L505 which randomly shows a blue screen prior to shutting down and restarting. I have use my system recovery disk to return my computer back to it's original state. The computer worked fine for a couple of month but has crashed again. Below is a sample of the blue screen messages prior to shutting down:
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
KMODE_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: 0x0000001e (0xffffffffc0000005, 0xfffff800032a526b, 0x0000000000000000,
0x000000007efa0000)
*** ntoskrnl.exe - Address 0xfffff800032c4c40 base at 0xfffff8000324f000 DateStamp
0x50e79935
2nd blue screen crash message
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: PCIIDEX.SYS
KMODE_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: 0x0000001e (0xffffffffc0000005, 0xfffff800033c6cda, 0x0000000000000001,
0x0000000000000018)
*** PCIIDEX.SYS - Address 0xfffff88000e879d4 base at 0xfffff88000e86000 DateStamp
0x4a5bc114
Does anyone know what this means and would be able to help.

Hiya
Run a full computer scan with your antivirus software. virus Backdoor.NTHack. may be the problem, and it runs Dl.bat in folder InetPub\Scripts.When you boot up the computer, go to task menager (CTRL+ALT+Delete), look if you have this runned: Firedaemon.exe, Sud.exe, Os2srv.exe, Mmtask.exe.
2. If you have a CARD READER than go to bios "Integrated Peripherals" and set Legacy USB storage detect to DISABLED
Let me know if you get any more problems

Windows 7 - Blue screen of death after Boot Camp install

Hello! I have done some searches with no answers, so...
After installing Windows 7 from scratch I then install Boot Camp 3.0 which then leads to the Windows blue screen of death upon reboot. I then have to recover Windows to the previous state prior to installing Boot Camp.
Help!?

Most likely, Apple HFS read-only, which is AppleHFS.sys and AppleMNT.sys - rename those and see.
You might want to run chkdsk after all this to make sure there are no errors with the drive and file system.
Windows Explorer will not accept HFS+ filenames with special characters and will "green bar" and hang when it does, too.
The faulty HFS driver is a valid concern.
Rename AppleHFS.sys and AppleMNT.sys
By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.
Navigate to c:/windows/system32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.
The faulty HFS driver is a valid concern. It seems to happen on many systems.
You find it in Windows/system32/drivers/AppleHFS.sys
Renaming to AppleHFS_disabled.sys will avoid the blue screens until you have found another solution or Apple updates Bootcamp 3
After renaming both myself because they are no longer "*.sys" or something? they are gone. In my case AppleHFS prevented Windows Backup from running to end and was causing error "some files skipped" and while some might find reading convenient, I prefer Windows not have even read-only access.
You can probably do better with MacDrive, or probably Paragon's HFS driver, to read AND write if needed, to HFS from Windows.

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...

T400 windows 7, blue screen memory_management and IRQL_NOT_LESS_OR_EQUAL

Hi can anybody help me solving this problem? I have T400 with windows vista 32. I upgraded it into windows 7. And now my laptop is having problem with the blue screen when the windows started it says about memory management or IRQL that asked me to disable the BIOS memory such as caching or shadowing.... What do you guys reckon?? Cheers.

I used to get that BLUE SCREEN ALL THE TIME
I stoped getting it one after I slipstreamed windows xp pro to sp1 and did a clean install
I use latest nvidia http://www.nvidia.com
I use the latest via drivers http://www.via.com.tw
also you should check to make sure your video card is seated properly take it out and put it back in
clear cmos/bios
check your memory make sure it's seated properly also try moving it around I found that the middle slot was bad on my board but I have a K7T266 pro2 v2 thank god I have a three year warenty still time to rma when every I get around to upgrade

Windows Vista Blue Screen on Startup

Similar Messages

Maybe you are looking for