975X PUE SATA RAID Windows XP Blue Screen Install

Hi,
I've just purchased a new MSI 975X PUE motherboard and am trying to install Windows on it.
I have connected 2x WD Raptor 36GB drives, and set them up in a RAID 0 array using the Ctrl+I RAID BIOS utility. I have set the SATA config in the BIOS to RAID mode, and turned off the other SATA controller... The RAID BIOS detects the array ok after it has been set up, and shows it as OK.
When I boot from a Windows XP SP2 CD I press F6 and choose the RAID Driver for ICH7R RAID. Windows tells me that it already has a driver but this version is newer, so I say to use the one on the floppy (I have tried without doing this and Windows does not detect any Hard Drives at all).
Once I have loaded the drivers it continues loading the other drivers for the setup, and then gets to "Loading Windows Setup", here is waits for a minute or so and the blue screens.... The stop code is 0x7B (INACCESSIBLE_BOOT_DEVICE)...
I have upgraded the BIOS from 7.0 to 7.1 (not 7.2 yet as I have read about problems with it).
I've tried various versions of the drivers from different locations, and each time it blue screens in exactly the same place... I'm beginning to get very annoyed with this as I shouldn't be expected to find my own drivers when there are ones supplied on the CD...
Is anyone able to suggest what I could do?
Thanks
[EDIT] Also I have tried an install of Windows Vista Beta and that installed fine using the drivers from the CD...

I must say again that the problem is located in the memory modules. As suggested by Hans before, try running memtest86 first,
http://filexoom.com/files/2006/11/1/41824/memtest86%2B-1.65.floppy.zip
and sometimes even if tests runs fine, doesn't mean that memory is OK. It just might be that that type of memory doesn't fit within your MB. As I mention before, my friend was using Corsair for his MB(getting the message INACCESSIBLE_BOOT_DEVICE), and after replacing with A-Data(definitely lower quality memory), everything went fine. So, try with another memory.
As for Murphyman, when you use the yellow connector, you are using the Jmicron controller,witch asks for RAID drivers before you use the device installed on it. The blue IDE controller is controlled by Intel's ICH7DH, and no RAID driver is need. So, try connecting the DVD drive on the blue connector, and see if will work.

Similar Messages

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

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

975X PUE: SATA vs IDE Combinations: 2+2, 4, or 1+3?

Hello,
I searched but didn't find info. For a new build with a 975X PUE, what is the optimal configuration of IDE/SATA drives. I want to have a configuation like:
DRIVE PURPOSE SATA or IDE?
C: VISTA OS ?
D: Data drive 2 SATA, RAID1
E: Backup for Data ?
My question is: Should I use SATA for drives C and E or IDE? Or one of each? Is there a general rule for which is preferred? All things being equal, I prefer SATA since cables are smaller.
Thx.
Scott
PS C and E will likely be single-drive, non-RAID.

Quote from: jsmartin22 on 16-June-07, 14:51:31
I thought perhaps there would be a difference data rates between the IDE/SATA, which arise only when you reach a specific # of SATA drives--in which case it might be better to begin using IDE. Looks like I was wrong. Thx.
Scott
SATA II 300 has 3.0 Gbit/sec available per port, so the number of SATA ports used should not make a difference. There is a theoretical advantage in using SATA, as it is a serial connection instead of a parallel connection with PATA.
Furthermore, because of your RAID 1 setup, you will be using AHCI mode for the onboard Intel controller. The Intel Matrix Storage driver (used for AHCI mode) might give you a couple percents extra drive performance over an IDE interface, even when using single drives.
So SATA would be the way to go...

T420 Installing Windows XP = blue screen

I am trying to install WinXP 32 on a T420. It seems to be looking for a SATA driver as once it loads up the setup program, it goes to a blue screen.
I have tried downloading the SATA drivers off the drivers site, but out of the 4 to choose from none (using F6 to use an additional driver) of them seem to work.
Anyone have any thoughts?

You could change the SATA mode in BIOS to compatibility mode and then install Windows XP that should prevent the blue screen during install. After Windows is installed download the "Intel Rapid Storage Technology Driver for Windows XP (32 bit)" (filename 83im15ww.exe) and run this file to extract the driver. After the extraction run "C:\DRIVERS\WIN\IRST\PREPARE\install.cmd", then shutdown the computer. Now enter BIOS en re-enable SATA AHCI mode and reboot the computer. If asked for a driver for this device when the computer start point to the directory "C:\DRIVERS\WIN\IRST" for the driver. This way should work and give the same result.
-gan

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 gives Blue screen of death when connect ipod

I have an ipod 20g and everytime i connect it to my 2.0 usb windows freezes gives me a blue screen and restarts

same problem here, also with a 20gb ipod. Mine also shuts the PC down on a disconnect of the ipod as well although this is less frequent.
I was using the USB2 ports on the front of my Dell but I've swithed them round now and am using a Firewire port on the back and touch wood it hasn't happened in the 2 days since I switched over.

Windows 7 Blue Screen of Death from Apple Wireless Keyboard?

I've installed Windows 7 with Boot Camp 3.0 drivers on my Mac mini, and I suppose overall, I'm enjoying it. However, I'm getting a blue screen that seems almost random. Keyword is almost.
I've got my Apple Wireless Keyboard and Mighty Mouse paired, and they're both working well, however, I do believe I am getting some blue screens from my wireless keyboard.
It seems, at random intervals (usually when I haven't touched the keyboard and mouse for awhile) I get an IRQL blue screen and no information about what's exactly causing it. For example, if I'm sitting in the other room listening to music for awhile, and I come back and press the "next" media button on my keyboard, it'll crash and give me the blue screen. However, I've also tried pressing another random button (shift) to "wake" the keyboard if it had fallen asleep, which also results in a blue screen. The blue screens ONLY show up when I give input via the wireless keyboard. Or, if I leave the computer on overnight to download a file or something, the screen will sleep (which it should) then I'll press a button on the keyboard, the screen will stay asleep, and the computer will restart. Which is just a hidden blue screen I'm assuming.
I've tried reinstalling Windows (Clean/fresh install of course), installing/uninstalling drivers, pairing and re-pairing. I've also removed unnecessary/non-Windows 7 drivers that were installed with Boot Camp.
Outside of this blue screen, I am quite impressed with Windows 7. I just can't figure out what's going on. Is there any place I can get a description of what's causing this crash? Does anyone know what's happening or know a solution to this?
Thanks in advance, if you need more details, please ask.

Experiencing exactly the same symptoms, bugcheck/bluescreen only when touching the Apple wireless keyboard after a period of inactivity.
I have an 20" iMac, just upgraded Leopard -> Snow Leopard latest minor version and updated to Boot Camp 3.1 hoping they provided a fix, but the driver at fault (keymagic.sys) doesn't look updated and the issue is still there
Hopefully someone from Apple dev support is reading this, here's all the info I could squeeze from the crash dump:
=============================================
* Bugcheck Analysis *
IRQLNOT_LESS_OREQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80002e33440, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e33440, address which referenced memory
Debugging Details:
READ_ADDRESS: fffff80002e33440
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: VISTADRIVERFAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f2f0c0 -- (.trap 0xfffff88002f2f0c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f2f100 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e33440 rsp=fffff88002f2f258 rbp=fffff88002f2f2b0
r8=fffff80002a4f000 r9=0000000000000000 r10=fffffa80027f3010
r11=fffff88002f2f208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoIsWdmVersionAvailable:
fffff800`02e33440 80f906 cmp cl,6
Resetting default scope
LASTCONTROLTRANSFER: from fffff80002ac0469 to fffff80002ac0f00
FAILEDINSTRUCTIONADDRESS:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
STACK_TEXT:
fffff880`02f2ef78 fffff800`02ac0469 : 00000000`0000000a fffff800`02e33440 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f2ef80 fffff800`02abf0e0 : 00000000`00000000 fffffa80`03375d90 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f2f0c0 fffff800`02e33440 : fffff880`04a02e5d fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 : nt!KiPageFault+0x260
fffff880`02f2f258 fffff880`04a02e5d : fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 : nt!IoIsWdmVersionAvailable
fffff880`02f2f260 fffffa80`02a3add0 : fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc : KeyMagic+0x2e5d
fffff880`02f2f268 fffffa80`027e8b40 : fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 : 0xfffffa80`02a3add0
fffff880`02f2f270 fffffa80`02a3add0 : 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 : 0xfffffa80`027e8b40
fffff880`02f2f278 0000057f`fd5c5228 : fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 : 0xfffffa80`02a3add0
fffff880`02f2f280 fffff880`04a02dfc : fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 : 0x57f`fd5c5228
fffff880`02f2f288 fffff880`00e5a2a7 : fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 00000000`00000010 : KeyMagic+0x2dfc
fffff880`02f2f290 fffff880`00e30c9b : fffffa80`027fd9d0 fffffa80`027fd9d0 fffffa80`027fd9e0 fffffa80`027fdc01 : Wdf01000!FxRequestBase::CompleteSubmitted+0x1f3
fffff880`02f2f310 fffff880`00e30dc4 : 00000000`00000002 fffff880`04bbcff7 00000000`00000000 fffff880`04bbcff7 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f2f380 fffff800`02aab935 : 0d780da4`0da40dd4 fffff880`02f2f420 0d440d78`0d780da4 fffff880`04bbeb52 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f2f3b0 fffff800`02ac3516 : fffffa80`027e8f2b 00000000`00000000 fffffa80`027fdc70 fffffa80`027e8b40 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f2f3e0 fffff880`04b62323 : fffffa80`027e8b40 00000000`00000000 fffffa80`02655c10 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2f4c0 fffff880`04ba24be : fffff880`02f2f590 fffffa80`027e8b40 00000000`00000000 fffffa80`0294f600 : bthport!BthCompleteRequestEx+0x5b
fffff880`02f2f4f0 fffff880`04b9c8d4 : 00000000`00000000 00000000`00000001 fffffa80`02a50c40 fffff880`02f2f6e0 : bthport!L2Cap_CompleteReadIrpList+0xc2
fffff880`02f2f540 fffff880`04b70732 : fffffa80`03349530 fffffa80`0294f5f0 fffff880`00410001 00000005`00000002 : bthport!L2CapInt_ProcessReadBip+0x430
fffff880`02f2f6d0 fffff880`04b70078 : fffffa80`0267f230 00000000`00000000 fffffa80`029b5402 fffffa80`02670000 : bthport!HCI_ProcessAclReadBip+0x642
fffff880`02f2f7a0 fffff880`04b988d9 : fffffa80`0267f230 fffffa80`03036702 fffffa80`026c0ab0 00000000`00000000 : bthport!HCI_ProcessAclRead+0x214
fffff880`02f2f810 fffff880`04b66201 : 00000000`00000000 00000000`00000000 00000000`00000056 fffffa80`026c0ab0 : bthport!HCI_ProcessMpBip+0x61
fffff880`02f2f880 fffff880`04b4d327 : fffffa80`0294f4f0 fffffa80`026c0ab0 00000000`00000000 fffff800`02ac59fa : bthport!BTHPORT_RecvMpBip+0x41
fffff880`02f2f8d0 fffff880`04b5399f : 00000000`00000000 fffffa80`00cd3910 fffff880`04b56388 fffffa80`00cda820 : BTHUSB!BthUsb_ReadTransferComplete+0xf7
fffff880`02f2f930 fffff880`04b53c31 : 00000000`00000003 fffff880`02f2f9f0 fffffa80`00ca2d00 fffffa80`00000012 : BTHUSB!UsbWrapWorkRoutine+0x17b
fffff880`02f2f9b0 fffff800`02ac3516 : fffffa80`00cd3bdb 00000000`00000000 00000000`00000000 00000000`00000000 : BTHUSB!UsbWrapInterruptReadComplete+0x1dd
fffff880`02f2fa40 fffff880`044135d9 : fffffa80`01e81050 fffffa80`00cda700 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2fb20 fffff880`04413ab7 : fffffa80`028ef502 fffffa80`00cd3910 00000000`ffffffff fffffa80`01e81ea8 : USBPORT!USBPORTCoreiCompleteDoneTransfer+0xa15
fffff880`02f2fc00 fffff880`0441164f : fffffa80`01e81ea8 fffffa80`01e811a0 fffffa80`01e82040 00000000`00000000 : USBPORT!USBPORTCoreiIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f2fc60 fffff880`04402f89 : fffffa80`01e81050 00000000`00000000 fffffa80`01e81e02 fffffa80`01e81ea8 : USBPORT!USBPORTCore_UsbIocDpcWorker+0xf3
fffff880`02f2fca0 fffff800`02acc5dc : fffff880`02f07180 fffffa80`01e81ea8 fffffa80`01e81ec0 00000000`00000000 : USBPORT!USBPORTXdpcWorker+0x1d9
fffff880`02f2fcd0 fffff800`02ac96fa : fffff880`02f07180 fffff880`02f11f40 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f2fd80 00000000`00000000 : fffff880`02f30000 fffff880`02f2a000 fffff880`02f2fd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
KeyMagic+2e5d
fffff880`04a02e5d ?? ???
SYMBOLSTACKINDEX: 4
SYMBOL_NAME: KeyMagic+2e5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: KeyMagic
IMAGE_NAME: KeyMagic.sys
DEBUGFLR_IMAGETIMESTAMP: 49c160ec
FAILUREBUCKETID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
BUCKET_ID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
Followup: MachineOwner
---------

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.

OSD Failure - Windows 7 - Blue Screen on First Boot in Full OS

Hi,
We are experiencing a really strange problem with our OSD which is hard to pin down. Our setup is SCCM 2012 R2 with 4 PXE enabled DP's (VMWare VMs) across 2 data centers and on seperate hosts and we are delivering Windows 7 (32 and 64) with recaptured WIM
files. Ouor deployments work fine for around a week and then they suddenly start experiencing a reboot look and blue screening at the first boot into the full OS.
This occurs on multiple different physical machines and we inject driver packages for different builds with WMI filters on motherboard as is common. The really weird part is that this will work for days then stop working. The only workaround we have is to
recapture the WIM file (we have a build and capture task sequence for this) and then it works again, even though the content and drivers are exactly the same from the same B+C task sequence. Even the windows updates are the same with no new ones. It doesn't
seem to be the drivers themselves but rather the process of DISM injecting them offline in windows PE which appears to break the registry. The last thing we see before blue screen is "Updating registry" in windows 7 boot.
These are the things we have tried are...
- Recapturing the WIM (works for around a week but not a fixed period)
- Host the WIM on a physical DP (to rule out VMWare) with only the WIM and a single driver package. Again this worked fine for a week or so.
- Built several different physical machines. All fine but when this stops, it stops for all of them
- If we remove all drivers but the LAN driver it can work but our testing has ruled out a specific bad driver as we have used different models of machine and if it was, then it would never work.
- We have set the TFTP block size to default of 1024 (we had it higher as 8192) to rule out the boot image being corrupted on download. It made no difference other than being a lot slower.
- Compared MD5 hashes for the WIM to rule out corruption.
- Removed and redistributed the WIM and drivers to different DP's (that it had never been on before)
The DISM.log on a failed device shows entries like
CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
Any advice would be greatly appreciated. This question on
Dell's forum sounds very similar.
What we are really struggling with is why would the same WIM, with the same driver package, from the same distribution point, to the same physical machine, work every day for a week the permanently break? Aaargh!
Thanks everyone,
Shaun

Hi,
Have this problem been resolved? How?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hp mini wa545ua#aba windows 7 blue screen of death and won't load operating system

I tryed to run my computer and the blue screen came up and it wouldn't load micosoft help

To enter the BIOS filip the power button and quickly tap the F10 key.
Select the Diagnostics section and run a memory test and a hard disk self test.
Post your results here.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Bootcamp Windows 7 Blue Screen of Death on MBPwR

Hello all, I've never needed to use this before but gosh darn it I need some advice, because I can't figure this out...
I'd rate myself a 9 out of 10 in "Windows PC" experience
And maybe a 6 out of 10 with Macs, I'm still new!
I just bought the new Mac Book Pro with Retina Screen in early July, I can't remember the exact date. But it hasn't been thirty days yet, so if you think that's my best bet to try and get an exchange here, let me know.
MC975LL/A
PROBLEM : Mac OSX Lion 10.7 works wonderfully, not a problem in the world, smooth as butter – the issue is Windows. I like to play some games and OSX doesn't play well with some Windows based games so I always install it on Bootcamp. Well, this has been a neverending issue on my new MBPwR because I can't seem to get it to work correctly.
      1. Here's how it started - I installed Windows 7 Ultimate x64 through Bootcamp, via my Superdrive and it ran well for a week or so. After installing a game and some other software (Steam) please take that as a coincidence as I did, I don't think Steam had anything to do with the crash, more likely it was something 'game' related, HDD, RAM, CPU, GPU? The computer started to get the "Blue Screen of Death" that Windows computers get, specifically: page_fault_in_nonpaged_area, I've never seen it before and I've owned a number of Windows computers over the years!
     2. Is this my fault, or something deeper? - I can't figure it out, is this a hardware problem or a software one? I reinstalled Windows 7 yesterday and attempted to try again. Just a chance my installation was messed or something, well it happened literally after five minutes of booting into Windows 7. After it happened the first time I used a memory check and a hard drive check software and both came up flawless. Some online on other boards although Windows based have suggested this error can be caused by the RAM and the CPU or the GPU, even... Is this true? As there is no way to test it, maybe exchanging this computer is the best option?
    3. As as a side note... - Has anyone else had a crawling slow boot into Windows 7? It takes my MBPwR almost five minutes of a top left-hand blinking cursor to actually boot to Windows 7.
So did I have some really, really bad luck here with a new computer? Or is this somehow software related? I can answer any questions if you have them so we can try and figure this out!
Thanks!

Did the Nvidia driver install okay? Some users had to reinsall just the driver from Apple Windows Software Support.
Did Windows DVD not find anything wrong?
Is Windows set to be default boot OS in the control panel for selecting the boot volume?
There probably is a leaning curve and bleeding edge sortof with any new logicboard and setup.
Apple has issued a firmware upgrade for some models - I thought Retina - the MacBook Air has a serious problem under Windows.
Mac will run hotter under Windows. Maybe an error message.
GPU-Z:
http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
AIDA64 Extreme Edition
http://www.aida64.comhttp://www.aida64.com/product/aida64-extreme-edition/overview
CCleaner
http://www.piriform.com/ccleaner
How to view error message:
From Control Panel-> Admin. Tools-> Event Viewer-> Windows logs:
Check Application and System Folders for Red highlit messages. Note that you can right-click clear these log folders.
Memtest
This is a step by step guide with audio and video to explain how to use memtest to see if your memory is defect. Another thing to add is that some errors will not be found on the first pass, best to do at least 3 passes.

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 7 Blue Screen Issues With Alt-tabbing From WoW

As the title says, lately I've been having blue screens which are mostly caused by wow.
Previously I've had the occasional bsod (once a month or so) when alt tabbing, but it was pretty rare. However recently, I've had something more like 1 a day, usually caused by alt tabbing out of wow. It seems the longer I'm alt tabbed the more likely it
is to happen. I haven't experienced the same problem with any other game, although the occasional monthly ones usually happen when I'm changing my music as I alt tab out of League of Legends.
I downloaded bluescreenview and it appears the cause is some combination of win32k.sys as well as ntoskrnl.exe Based off the fact that it is happening more with a more demanding game, I'm guessing the problem is
most likely due to a bad stick of ram, but I'd like a second opinion.
I'll attach a few of the most recent dump files (the one today is slightly different than the ones last week which seems slightly odd).
http://puu.sh/8lVuH http://puu.sh/8lVtT http://puu.sh/8lVse
Thanks in advance for any help, and I hope image files are okay :)

Thanks, and it's not, no. You can't exactly debug pictures :')
We have two consistent bug checks:
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
BugCheck 3B, {c0000005, fffff80002e5301e, fffff88008945c70, 0}
0: kd> ln fffff80002e5301e
(fffff800`02e52ff8) nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26 | (fffff800`02e53040) nt!PsIsProtectedProcess
^^ The exception occurred in nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe. This is a routine that first enters a critical region, and then acquires the specified fast mutex for the calling thread.
PAGE_FAULT_IN_NONPAGED_AREA (50)
This indicates that invalid system memory has been referenced.
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
BugCheck 50, {fffff900c25efcf0, 0, fffff9600032c69d, 0}
^^ Address fffff900c25efcf0 was written to by the instruction at address
fffff9600032c69d.
1: kd> r cr2
Last set context:
cr2=fffff900c25efcf0
^^ The 1st parameter address was stored in cr2 prior to calling the page fault handler.
1: kd> !pte fffff900c25efcf0
VA fffff900c25efcf0
PXE at FFFFF6FB7DBEDF90 PPE at FFFFF6FB7DBF2018 PDE at FFFFF6FB7E403090 PTE at FFFFF6FC80612F78
Unable to get PXE FFFFF6FB7DBEDF90
^^ Can't see whether or not it's valid/non-valid.
1: kd> .trap fffff880`073858e0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c376ae40
rdx=00000000701215e6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600032c69d rsp=fffff88007385a70 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000410 r10=fffff80002e4e000
r11=0000000000000022 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
fffff960`0032c69d 488b4f20 mov rcx,qword ptr [rdi+20h] ds:00000000`00000020=??????????
^^ On the instruction we failed on, address fffff960`0032c69d deferenced
rdi+20h where rdi is 0000000000000000. All of this would result in a memory write to the address
00000000`00000020.
1: kd> dd 00000000`00000020
00000000`00000020 ???????? ???????? ???????? ????????
00000000`00000030 ???????? ???????? ???????? ????????
00000000`00000040 ???????? ???????? ???????? ????????
00000000`00000050 ???????? ???????? ???????? ????????
00000000`00000060 ???????? ???????? ???????? ????????
00000000`00000070 ???????? ???????? ???????? ????????
00000000`00000080 ???????? ???????? ???????? ????????
00000000`00000090 ???????? ???????? ???????? ????????
Right, so the code wanted to write to 00000000`00000020 which as we can see above is a completely invalid address. The 1st parameter and cr2 however note we failed writing to address
fffff900c25efcf0. This does not make sense, and is essentially not logically possible.
The hardware was told to write to 00000000`00000020, and the hardware came back and said 'I cannot write to
fffff900c25efcf0'. Another way to think about it is if you kindly asked the waiter of your table for more water, he writes it down, but comes back and says 'I'm sorry, but we're all out of coffee'.
1. Uninstall any/all installed Asus bloatware, I for example see Asus PC Probe, and AI Suite.
2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:
avast! removal -
http://www.avast.com/uninstall-utility
MSE -
http://windows.microsoft.com/en-us/windows/security-essentials-download
3. If the above fails, you have faulty RAM.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Windows 7 Blue Screen Crash

Hello, I recently have been getting a lot of blue screen crashes simultaneously. I haven't downloaded any games or anything. I just use this laptop for school work mostly. I already ran a memory diagnostic test and no problems found as well as restored my
computer to a month back to when it wasn't having any problems. Anyways, this the problem details:
Problem signature:
Problem Event Name:   BlueScreen
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   4105
Additional information about the problem:
BCCode:   3b
BCP1:   00000000C0000005
BCP2:   FFFFF88005CFC3BE
BCP3:   FFFFF88009ACE4D0
BCP4:   0000000000000000
OS Version:   6_1_7601
Service Pack:   1_0
Product:   768_1
Files that help describe the problem:
C:\WINDOWS\Minidump\103014-25318-01.dmp
C:\Users\Mark\AppData\Local\Temp\WER-82087-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
Hope that someone could help! Thanks!

FS
These were all Related to NETwNs64.sys Wireless WiFi Link Driver from Intel Corporation (yours is 5 years old). I would remove the current driver and install the newest driver available.
If you continue to crash Remove McAfee and use MSE in its place.
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\problem\103014-25318-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0360c000 PsLoadedModuleList = 0xfffff800`0384f890
Debug session time: Thu Oct 30 12:54:00.869 2014 (UTC - 4:00)
System Uptime: 0 days 0:01:07.181
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88005cfc3be, fffff88009ace4d0, 0}
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys ( NETwNs64+2673be )
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005cfc3be, Address of the instruction which caused the bugcheck
Arg3: fffff88009ace4d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
NETwNs64+2673be
fffff880`05cfc3be 8b10 mov edx,dword ptr [rax]
CONTEXT: fffff88009ace4d0 -- (.cxr 0xfffff88009ace4d0;r)
rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
r8=0000000000000a70 r9=0000000000000000 r10=fffff8000360c000
r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
r14=fffffa8008bf7fb0 r15=fffffa800af1c008
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
NETwNs64+0x2673be:
fffff880`05cfc3be 8b10 mov edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
Last set context:
rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
r8=0000000000000a70 r9=0000000000000000 r10=fffff8000360c000
r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
r14=fffffa8008bf7fb0 r15=fffffa800af1c008
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
NETwNs64+0x2673be:
fffff880`05cfc3be 8b10 mov edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: wlanext.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88005cfc3be
STACK_TEXT:
fffff880`09aceeb0 00000000`00000000 : fffffa80`08bf7618 fffffa80`00000002 00000000`000000dc fffffa80`00001e37 : NETwNs64+0x2673be
FOLLOWUP_IP:
NETwNs64+2673be
fffff880`05cfc3be 8b10 mov edx,dword ptr [rax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: NETwNs64+2673be
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETwNs64
IMAGE_NAME: NETwNs64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d10df1b
STACK_COMMAND: .cxr 0xfffff88009ace4d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_NETwNs64+2673be
BUCKET_ID: X64_0x3B_NETwNs64+2673be
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x3b_netwns64+2673be
FAILURE_ID_HASH: {69744f93-8380-f8c7-a080-fedb60128a80}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

975X PUE SATA RAID Windows XP Blue Screen Install

Similar Messages

Maybe you are looking for