Random BSOD after installing port replicator drivers.

Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
Solved!
Go to Solution.

nbuduroi wrote:
Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
The win7 driver for the usb port replicator with digital output is not out yet. So, you cannot get it work under win7. I recall seeing an official flyer of the product, in which there is a line stating that a win7 driver will be out in December.

Similar Messages

Random BSOD after installing Windows 8.1 on Lynx K3011

I upgraded the graphics drivers as intructed her in another thread and that works now. However I keep getting a random BSOD with the error MEMORY_MANAGEMENT.
I did a bug check analysis and this is the result:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101413-9031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.x86fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0x81c14000 PsLoadedModuleList = 0x81e0e218
Debug session time: Mon Oct 14 12:47:54.837 2013 (UTC - 7:00)
System Uptime: 0 days 0:00:09.648
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {1238, 85ea6368, 802, 0}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c )
Followup: MachineOwner
3: kd> !analyze -v
*                        Bugcheck Analysis                                    *
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00001238, The subtype of the bugcheck.
Arg2: 85ea6368
Arg3: 00000802
Arg4: 00000000
Debugging Details:
BUGCHECK_STR: 0x1a_1238
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81d63c8d to 81d14ce4
STACK_TEXT:
8b90ebf0 81d63c8d 0000001a 00001238 85ea6368 nt!KeBugCheckEx
8b90ec38 82d1abb4 85ea6368 8506b040 00000162 nt! ?? ::FNODOBFM::`string'+0x355e7
8b90ec54 82d18dec 00000000 8506bd10 00000001 rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+0x4c
8b90ecc4 82d1704b 00000000 86291040 8506b008 rdyboost!ST_STORE<SMD_TRAITS>:tDmPageRemove+0x3ac
8b90ed00 82d1739e 00000000 8506c200 83a4b040 rdyboost!ST_STORE<SMD_TRAITS>:tWorkItemProcess+0xf3
8b90ed40 82d266a0 ce25f08e 00000000 8506c200 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorker+0xfc
8b90ed70 81cc36a8 8506b008 61b2fcc6 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorkerThread+0x1d
8b90edb0 81d2a701 82d26683 8265bf68 00000000 nt!PspSystemThreadStartup+0x58
8b90edbc 00000000 00000000 2444c718 80000010 nt!KiThreadStartup+0x15
STACK_COMMAND: kb
FOLLOWUP_IP:
rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
82d1abb4 6a00            push    0
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52158f40
BUCKET_ID_FUNC_OFFSET: 4c
FAILURE_BUCKET_ID: 0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
BUCKET_ID: 0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
Followup: MachineOwner
Any ideas? Probably more incompatible drivers. If I can't get Windows 8.1 running correctly, does anyone know how to restore the system image?
Solved!
Go to Solution.

this error is so much obvius.
just look on internet on how to disable readyboost. additional just turn off the hybrid function and u will never see this bsod again, even i dont know how dumb ur mediacenter edition is and want to give u other bsods. btw i only seen bsods couse of **bleep** driver on my devices. donno how u manage to get such bluescreens......
btw according to the results i recommning ya to use ckhdsk /f to ur disk. mstWorker is mentioned wich means read write issues on access files. mstworker is microsoft Tiworker, an process wich examines files an bit. used by winupdate and the indexer.

BSOD After Installing Boot Camp 5640 Drivers on Win7 x64

I get a BSOD after installing the Boot Camp 5640 drivers on Windows 7 x64 Professional due to "CACHE_MANAGER". If install the drivers individually, this does not happen (provided I don't run bootcamp.exe).
This wouldn't be a problem except that I can't get the trackpad working properly without running setup.exe or bootcamp.exe.

what is your exact rMBP
check here and make sure you are trying to install the right boot camp pkg for your windows version and machine
http://support.apple.com/kb/ht5634

No sound after installing the latest drivers

After installing the latest drivers for X-fi xtrememusic, 2.8.003 I have no sound. Also my creative console is stuck in Entertainment Mode, it won't switch to any other mode. Help please?

Pheary wrote:
?My best guess is this is some bizarre driver/registry problem, since it mostly works perfect in XP, but barely at all in Vista.
Well, i don't have a solution for you, but if your soundcard + hub act like that even under xp after a few weeks i would suggest to get a replacement, cause there might be a hardware-error that causes your problem. A software/driver problem sounds very unlikely to me. That your having problems under Vista, isn't strange at all, cause there are still no final drivers relaesed for Vista and the support of the hub is rather barebone at the moment. Stormblade

Random BSOD after migrated to SCCM 2012 R2 - System Endpoint Protection

We are currently experiencing random BSOD after upgrade to SCCM 2012 R2 from SCCM 2012. These BSOD are happening on our Windows 7 x64 machines. With the upgrade, we switched to System Center Endpoint Protection for the anti-virus protection and start
to notice this problem. Have anyone else experiencing the same issue? I'm trying to run adplus right now on 2 machines to try and capture the error but so far no luck. This BSOD is so random and we are getting at least 5 calls a day from users about this.
The only similarity with these BSOD is usually the user is away from keyboard and after the BSOD, System Center Endpoint cannot connect to update virus definition.
Below is a screenshot of the BSOD and it didn't create any memory dump file. We are currently running Windows 7 x64.
Message was: "STOP:
C000021a [fatal system error]. The Windows subsystem process terminate
unexpectedly with a status of 0xC0000005

- Event Type : Stopped working (APPCRASH)
      Application Name: Client Server Runtime Process
      Path:             C:\windows\system32\csrss.exe
      Event Time      : 03/22/2014 12:30:26 AM
          Application Name: csrss.exe
          Application Version: 6.1.7600.16385
          Application Timestamp: 4a5bc115
          Fault Module Name: sxs.dll
          Fault Module Version: 6.1.7601.17514
          Fault Module Timestamp: 4ce7c9cc
          Exception Code: c0000005
          Exception Offset: 0000000000011b2f
      Memory dump     : Not created

Windows 7 BSOD randomly occuring after installing iTunes 10.6 with iPhone 4 in dock

After installing iTunes 10.6 and IOS 5.1 on my iPhone 4, Windows 7 computer was randomly blue screening with the iPhone 4 in the attached dock. After removing the phone from the dock, system works fine.

Re-installed iTunes as you suggested and it worked. However, started experiencing random BSOD's. Disk check found a number of file errors on the boot drive - which it fixed. It then took a number of re-boots before computer became stable.
Then, upgraded iTunes on a HP workstation (no iPhone attached). On reboot windows had to attempt a boot repair 3 times before it would reboot. Couldn't even do a disk check without first reverting to the last restore point. It also corrupted Norton. The end result was 2.5 hours of wasted time.
Being an expert pc user, I can safely say that I believe Apple has some serious issues with 10.6.

BSOD after installing Boot Camp 5 drivers on my MacBook Pro (13" mid 2012, non-retina)

Basically what the post says. I go through the normal rounds of creating a bootable flash drive (i've tried ISO files from 7, 8, and 8.1 -- all 64 bit versions), downloading the drivers either off the website, or through the Boot Camp Assistant, then I finally partition my disk equally and go through the normal install process with the version of windows. Everytime windows installs correctly and starts up just fine, but as soon as I install the bootcamp drivers (or any drivers at all, say the graphic drivers from intel's website) all **** breaks loose. Near the end of the bootcamp driver install on windows 7 it blue screens and shuts the computer down. In windows 8 and 8.1 it installs without a hitch then when I go to restart it the machine boots into the windows partition, shows the windows 8 logo with the loading circle thing under it for several minutes then I get presented with the new Windows 8 blue screen of death with the (sorry there was a problem loading your system ) on it. Then it shuts down, restarts and does it all over again. Someitmes it will try and "repair" the system on windows 8 start up but that never does anything.
I've tried what seems to be everything with this situation and still I get the same results. Even reinstalled OS X. I've searched the internet for hours upon hours for an answer and I've gotten nowhere. Any help would be greatly appreciated!
here are my exact system specs if anyone needs to know anything more than what I've posted in the title: http://store.apple.com/us/product/FD101/refurbished-macbook-pro-25ghz-dual-core- intel-i5
Thank you to anyone in advance.

Well, at least my Windows won't boot after renaming them to *.sys.old.
But anyway, these two drivers aren't the cause, instead it's actually BootCamp.exe and/or the trackpad or keyboard drivers.
This guy had the exact same problem and the 'solution' was to disable BootCamp.exe.
https://discussions.apple.com/message/10301692#10301692
I finally managed to install all Boot Camp updates but still nothing has changed; as soon as I launch BootCamp.exe or change settings for the trackpad the system crashes.
It seems I have two options now: Use Windows without "Tap to click", "Secondary Tap" and modified keyboard settings, or find suitable trackpad/keyboard drivers.
Speaking of which, is there any chance to get Boot Camp drivers for Win 7? Maybe this would solve my problem since I only have Vista/x64 drivers which I used for Win 7.
Thanks!

Windows 8 crashes and with the error "kernel_security_check_failure" after installing Boot Camp drivers.

Hi!
I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
All help is greatly appreciated!

I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise. After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD. This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON!
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Am conrtacting them, but, here's the Debugger output:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
*                        Bugcheck Analysis                                    *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29            int     29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2            xor     edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner

BSOD after installing Boot Camp 4.0.4033

I have recently installed Windows 7 Professional on my 15" Early 2008 MacBook Pro, 2.5 GHz Intel Core Duo w/ 4GB Ram. I have a solid state SATA drive.
I have tried renaming the AppleHFS.sys & AppleMNT.sys drivers to no avail. Pulling my hair out here. I'm not sure how to get the error numbers from the bsod screen.
I'm starting to think about giving up on installing the mac drivers because much of the time I use the partition in parallels, but it becomes very difficult to use when I need to boot natively to use all of the ram on windows applications.

I do not know exsactly what your issue could be. My advice would be to try and F8 Windows into safe mode and try to run a Disc check on the Windows partition to see if their are errors that might be fixed. If you have the Windows DVD you can boot into that and run repair apps from that. You may just have a corupt boot config and its causing the BSOD. I have a 2011 Macbook and have similar problem with freeze ups on Windows 7. Mostly after it has to reboot after a update? All I can think of after looking at my Windows Events viewer was that a problem with a driver was most likely the cause. I unfortunately have Mountain Lion and have to use BootCamp 4. Personally I have never had a issue with BootCamp until 4.0 and Mountain Lion. In fact when I upgraded to Mountain Lion I did so without the BootCamp partition and then I added BootCamp back in after Mountain Lion upgrade. When I fist tried to install Windows 7 BootCamp never did start the Windows install corectly. All it did was boot back into OS X. That should have been my first hint that things would not go well

BSOD when installing windows 7 drivers using bootcamp in macbook pro late 2013

I followed the bootcamp instructions and installed windows 7 in my macbook pro 13 inch late 2013. But when the bootcamp starts to install the required drivers, halfway through the computer goes to BSOD. And after restart windows shows many error messages of "validation error".
I have a student licensed windows 7 professional.

I had the same problem. I was installing a Debug Build of Windows 7 on MacBook Pro 15" Late 2013 with a student license and it would die with BSOD while running BootCamp at the end of Windows installation. I solved the probelm by downloading a non-Debug version of Windows 7 Professional with Service Pack 1 and re-trying the installation from scratch. That is, I went back to OS X, launched BootCamp Assistant, erased the previous partition of Windows and re-created it again. After that, I installed a fresh copy of the right flavor of WIndows and it worked flawelessly.

T540p BSOD after installing driver with ThinkVantage System Update

Hello,
today I got my brand new T540p. Its was delivered without OS (Lenovo Campus). I downloaded the ethernet drivers and the TV System Update on a usb flash drive with my old thinkpad. After installing Windows 8 Pro, i installed the ethernet drivers to connect to the internet. Then i started the TV System Update and let it install all critical and optional drivers.
After the all drivers have been installed the machine wants to reboot, but now i am in a reboot loop. Everytime it hangs in the screen "Windows Update 100%" and then I see the blue screen of death (Driver Power state failure) and the machine reboots again.
Does anyone else have this problem or is there a fix from lenovo?
Thanks,
Mat

After fresh install of win 8 I only updated drivers from windows update. Works fine so far. Upgraded to win 8.1 still no problem. Use nvidia, wifi, intel graphics driver from windows update. Windows could not install chipset drivers. So I downloaded the intel chipset drivers from lonovo. Install crashes with bsod and ending up in reboot loop. I assume it's a problem with the intel drivers from lenovo. At moment I install win 8 again and I will try to install the drivers from intel website.

BSOD after installing Boot Camp, AMD Radeon 6630M driver issue

I have reinstalled Windows using Boot Camp twice now and get a blue screen right after installing the Boot Camp drivers and restarting.
I am installing Windows 7 Ultimate 64-bit on my Mac mini 2011 edition. I created an install disk in Lion and used the option to copy the Boot Camp drivers into the disk.
I have narrowed the problem down to Apple's driver for the AMD Radeon 6630M graphics which my Mac mini has. The driver will install without errors but then the blue screen appears on next startup. If I use safe mode to uninstall the AMD driver, the blue screen goes away, but the display resolution is very low.
I checked for driver updates from AMD, but there are none for the 6630M.
Anyone else having this issue?

Hi,
I have installed Windows using Boot Camp and I also get the blue screen of death right after installing the Boot Camp drivers and restarting.
I am installing Windows 7 Ultimate 64-bit on a i7 Mac mini 2011 edition. I created the USB install thumb within Lion's Boot Camp, and got downloaded the latest Bootcamp drivers (bootcamp 4.0). I connect the mac mini to a 24" iiyama screen with a HDMI cable. I don't have a DVI cable anymore unless i would have checked that point too.
I have also narrowed the problem down to Apple's driver for the AMD Radeon 6630M graphics which my Mac mini also has. The driver will install without errors but then the blue screen appears on next startup. If I use safe mode to uninstall the AMD driver or renaming the atikmdag.sys file (the main cause of the crash), the blue screen goes away, but the display can't get the effects such as Aero interface.
AMD provides official drivers that don't recognize its own 6630m graphic card with Apple, then doesn't install any up-to-date driver... Only Apple's AtiGraphics setup program will install the drivers...but it makes Windows 7 crash at each boot.
Thanks for your technical skills or info to come over this issue (or releasing a bootcamp update ?)

2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

Hey all,
I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
Thanks!

Thank you to The hatter.
I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

Display Problems After Installing Graphics Card Drivers

Hi, I was wondering if anyone can help with a problem that's got me stumped?
I've just upgraded my pc (CPU, Motherboard, Memory, Hard Drive, Sound Card, Monitor) - the only things that haven't changed are my graphics card and PSU.
I've built the system, installed windows and the motherboard drivers, which all work correctly. But after I install the graphics card drivers and reboot, the display becomes all scrambled when it loads into windows. The display is fine with the initial boot and up until the Windows XP screen, with the moving bar comes up.
The graphics card was fine in my previous system and I have tried my old monitor, but neither works. I've updated the BIOS, using the MSI Live Update program and have also tried various versions of the nVidia drivers (including the latest).
Any help would be appreciated.
Thanks in advance.
****UPDATE****
I've now managed to install the nVidia drivers and now windows loads normally, but after a short amount of time the screen scrambles again.

I have the same problem. It happened right after I installed the graphics update. When the computer restarted, my screen went crazy. I couldn't see anything, just a screen full of horizontal lines. After restarting a couple of times it seemed to go away, but it has begun to happen again recently. although not as bad yet. I am not saying it's not a logic board issue, but it does seem funny that more than one person is experiencing the same type of problem after the graphics update. I guess it's time to take a trip to the apple store.

Random Lockups after installing any detonaters

hey guys, i get random lock up in windows xp after installing any detonaters
how do i fix this

by the way my specs are
AK32 Spacewalker Motherboard
AMD Athlon XP 1800 +Maxtor D740X 40Gb
AC 97 Built In Sound Card
256 Mb DDR RAM
Samsung SyncMaster 753 s
ATX 400 W/P4
MSI Geforce 4 MX 440
OS:WINXP

Random BSOD after installing port replicator drivers.

Similar Messages

Maybe you are looking for