Windows 7 PC Blue Screen: STOP 0x000000F4

0x000000F4 (0x0000000000000003, 0xFFFFFA800B8D7B30, 0XFFFFFA800B8D7E10, 0XFFFFF8000337D270)
Sometimes bios won´t detect my SSD drive (Windows is installed here). Happens every time i start my laptop.
Here is a link to my dump file: http://1drv.ms/1o0VWJP
Hope someone can help me.

Emiliant
A critical system process was terminated because of a HD I/O error.  FIrst thing I would do is to update the SSD firmware. Then I would run a system file check to verify the OS files
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\062414-6723-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Users\Ken\Desktop
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Users\Ken\Desktop
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`03257890
Debug session time: Tue Jun 24 18:22:11.554 2014 (UTC - 4:00)
System Uptime: 0 days 0:01:24.475
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa800ac37320, fffffa800ac37600, fffff8000338f270}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800ac37320, Terminating object
Arg3: fffffa800ac37600, Process image file name
Arg4: fffff8000338f270, Explanatory message (ascii)
Debugging Details:
----- ETW minidump data unavailable-----
DISK_IO_READ_FAILURE: WARNING: Disk IO Read of 0 Bytes Occurred a time(s).
PROCESS_OBJECT: fffffa800ac37320
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR: 0xF4_IOERR
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
STACK_TEXT:
fffff880`07d92e38 fffff800`03417ab2 : 00000000`000000f4 00000000`00000003 fffffa80`0ac37320 fffffa80`0ac37600 : nt!KeBugCheckEx
fffff880`07d92e40 fffff800`033c2abb : ffffffff`ffffffff fffffa80`0ad33b50 fffffa80`0ac37320 fffffa80`0ac37320 : nt!PspCatchCriticalBreak+0x92
fffff880`07d92e80 fffff800`03341f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0ac37320 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`07d92ed0 fffff800`03088e53 : fffffa80`0ac37320 fffff800`c0000006 fffffa80`0ad33b50 00000000`00bc0c80 : nt!NtTerminateProcess+0xf4
fffff880`07d92f50 fffff800`03085410 : fffff800`030d482f fffff880`07d93a38 fffff880`07d93790 fffff880`07d93ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07d930e8 fffff800`030d482f : fffff880`07d93a38 fffff880`07d93790 fffff880`07d93ae0 00000000`00bc1990 : nt!KiServiceLinkage
fffff880`07d930f0 fffff800`03089242 : fffff880`07d93a38 00000000`00013600 fffff880`07d93ae0 00000000`00bc1468 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`07d93900 fffff800`03087dba : 00000000`00000000 000007fe`fd16d8c0 00000000`774c8d01 00000000`00013600 : nt!KiExceptionDispatch+0xc2
fffff880`07d93ae0 00000000`773c9c42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00bc13b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773c9c42
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xf4_ioerr_image_csrss.exe
FAILURE_ID_HASH: {183378f4-a174-8cab-8ad7-e5d860a58439}
Followup: MachineOwner
Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.
System file check (SFC) Scan and Repair System Filesa
Wanikiya and Dyami--Team Zigzag

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

  • Restarting After a Blue Screen Stop Error

    I have received a Blue Screen Stop Error on my Toshiba Satellite 5200 Series laptop.
    I could report it here, in full, if that would be helpful. However, it begins by telling me to restart the machine but the unit's Power button is not allowing me to switch it off.
    What action should I take ?

    Crikey ! Someone at another forum just told me to hold the button down for 5 seconds..... and it worked !

  • Blue screen appears on Windows HP G56. ***STOP: 0x000000F4

    Blue screen appears at random times ... 
    Product name: HP G56 Notebook PC
    Product number: XP267EA#ABU
    Message reads: 
    If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.
    ***STOP : 0x000000F4 (0x0000000000000003, 0xFFFFFA8U06F32B30, 0XFFFFFA8006F32E10, 0XFFFFF80002F94660)
    I've already put it back to factory image setting and updated all the updates so could someone please tell me what i can do. 

    Blue screen appears at random times ... 
    Product name: HP G56 Notebook PC
    Product number: XP267EA#ABU
    Message reads: 
    If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.
    ***STOP : 0x000000F4 (0x0000000000000003, 0xFFFFFA8U06F32B30, 0XFFFFFA8006F32E10, 0XFFFFF80002F94660)
    I've already put it back to factory image setting and updated all the updates so could someone please tell me what i can do. 

  • 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

  • Critical error, blue screen stop error

    after installing installation CD today, my laptop keeps going to a blue screen reporting a STOP error.... a critical error, but can't reslove. Have now removed the iTunes and it hasn't happened yet.
    Maybe a conflict, I don't know.
    Dell Inspirion Laptop   Windows XP  

    I found the answer !  Turns out it is/was not a Win7 problem, but a drive problem.
    I was following some links on another Win7 forum and happened upon mention of SSD drives causing a BSOD.  The one in particular mentioned was a Crucial M4 SSD. It sounded familiar . . . I have one as my C: drive.  Turns out I needed a firmware
    update. The update corrects a condition where an incorrect response to a SMART power-on counter will cause the m4 drive to become unresponsive after 5184 hours of Power-on time. The drive will recover after a power cycle, however, this failure will repeat
    once per hour after reaching this point. 5184 hours is about 7.2 months. Just a bit under how long I've had this system.
    I applied the update . . . . . computer has been running seven hours now.
    Thanks to all who helped me here.
    Joe
    Wanted to add for reference:
    The original post from Crucial acknowledging the issue.
    BSOD Crucial M4
    The fix is as simple as updating the firmware, but the hoops to jump through for the firmware update to take place is a bit frustrating.
    With my board, z68-v pro, it was necessary for me to go into the bios and change my controller mode to IDE. In addition I needed to remove the drive connected to the Marvell port and plug it into the Intel port as well as put my two ssd's on the first and
    second Intel ports. Once this was done I was able to get past the 'finding drives' screen and update the firmware for both ssd's. Once the update finished I went back into the bios and changed the controller mode back to AHCI. As i said, a frustrating experience
    but I commend Crucial for owning up to the issue rather than lead people to think their ssd's needed replacing or something was wrong with windows and subsequent unnecessary re-installs.

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

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

  • HP Pavilion 750n - Windows XP Blue Screen of Death Error

    Hello everyone - I hope I can get a reply to fix my son's computer (I can't afford to buy a new one).
    I received the blue screen of doom and I was not aware that Windows had a patch to fix this before the error occurred.  I tried to restore my system to when I first bought this computer without losing all my data (specially my pictures).  Now the system starts but it gets stuck on the page that asked if you want to logon on Safe Mode or Regular Mode, etc.  No matter what I choose the system keeps coming back to this same screen.
    I read the following on the HP web side but I'm not sure how to get this diskette/cd or whatever they have available:
    Preventing a Windows XP Critical Error
    If you purchased your HP Pavilion home PC between September 2001 and February 2002, your PC may experience a Microsoft® Windows® XP critical error. To prevent an error that may cause your computer to be unusable, HP strongly recommends that you go to the Microsoft Windows Updates Web site to download all critical updates. Without these updates, an Unmountable Boot Volume error may occur randomly, and if it does, the error creates a blue screen with the message: A problem has been detected and windows has been shut down to prevent damage to your computer. UNMOUNTABLE_BOOT_VOLUME…Technical Information: *** STOP: 0x000000ED
    If this error occurs, you will be unable to fix the problem without a diskette that you can order from HP Technical Support.
    The system won't let me send HP an email and I can’t see how to contact them just to ask for a price.  Perhaps, there may be another place where I can get the diskette for this fix - does anyone know how to get the diskette or if I can download the fix from somewhere else? 
    Any help will be greatly appreciated!

    Get BartPE or Ultimate Boot CD and you should be able to get the computer to a state that will allow you to copy your files.
    If you have a spare computer or HD, configure the problem HD as a slave and you should be able to access your files. 

  • My computer running on Windows 7 blue screens often whenI use Firefox since I installed latets version

    I have been using Mozilla for a long time. On one computer where I am running Windows 7, I suddenly started having problems after I downloaded the latest upgrade to Firefox 7.0.1 . not only does silverlight not work-always crashes, but firefox often (several times a day) stops responding and my computer blue screens. None of this was happening until this latest upgrade.
    I am not currently sending this from my computer with the problem because I cannot get Firefox to open

    Updating this thread...
    I see some people talking about Forms 6i and SQL Plus crashing when connecting to a database:
    APPCRASH Problem for plus80 and forms 6i builders
    Forms Developer 6i will crash if you try connecting to a database running the AL32UTF8 character set. Older systems require the UTF8 character set.
    Here are several very old threads with similar issues:
    <p>connecting form 6i  to oracle database 10G express edition
    <br>Forms 6i X 10g Database (the solution is here)
    More info: In Windows 7, I am running Forms 6i WITHOUT compatibility mode set to XP. It all seems to be running fine. I have had no problems with it since I first installed last year.
    Unfortunately, I don't have an Oracle 11 database available to try connecting to. I have only used this setup with Oracle 9 and 10 databases.

  • Windows XP blue screen and 0x00000050 when starting ITunes up

    when starting ITUNES after the upgrade to 7.3, I now get the blue screen of death.
    Windows XP service pack 2 is installed
    message is STOP: 0x00000050 (0xF8ac0000, 0x00000000, 0xF8ac0000, 0x00000000)
    I have installed different video cards and removed my sound card from the system but problem still remains. I did change the QUICKTIME settings as suggested for Vista problems but problem still remains.
    ITUNES will only run in SAFE MODE
    help please... i miss my music

    this is the information from the event log viewer. no files are referenced
    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 8/29/2007
    Time: 2:21:22 PM
    User: N/A
    Computer: DAD_ASUS
    Description:
    Error code 10000050, parameter1 f79f0000, parameter2 00000000, parameter3 f79f0000, parameter4 00000000.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 35 1000005
    0020: 30 20 20 50 61 72 61 6d 0 Param
    0028: 65 74 65 72 73 20 66 37 eters f7
    0030: 39 66 30 30 30 30 2c 20 9f0000,
    0038: 30 30 30 30 30 30 30 30 00000000
    0040: 2c 20 66 37 39 66 30 30 , f79f00
    0048: 30 30 2c 20 30 30 30 30 00, 0000
    0050: 30 30 30 30 0000

  • Windows crash (blue screen)

    after upgrading to the latest version of iTunes (7.6.1.9) my system crashes immediately when I try to open the application. Going back to an older version everything is ok. It seems to be related to AVG antivirus software (Grisoft)AVG 7.5.516. De-installing that software fixes the problem, but of course that's no solution.
    Any idea how to fix it?

    Have You tied checking with Grisoft to see if there are any know issues with the latest iTunes and AVG. A bit of Googling might help in case others are having the problem. There hasn't been an epidemic of blue screens following iTunes 7.6 and AVG is widely used so it seems unlikely that it is a general probelm.
    If you want to investgate this, you need to get the Windows stop message.
    It should be some sort of numbers and text -
    0x(zeros/letters/numbers) (CAPSANDUNDERSCORES)
    For example:
    Stop 0x05 (INVALIDPROCESS_ATTACHATTEMPT)
    Also is a file name mentioned in the error message? If so give the exact file name. This is the best clue to the cause of the problem - it will often be a driver.
    if you're not seeing a blue screen (or just a flash of one), you can use this technique to make hidden blue screens appear:
    1) Open your system control panel (Start->Control Panels->System).
    2) Select the "Advanced" tab.
    3) Click the "Settings" button in the "Startup and Recovery" section
    4) Verify that under "System Failure" the "Automatically restart" checkbox is not checked.
    There is some general help on Troubleshooting Windows Stop Messages here:
    http://aumha.org/win5/kbestop.htm
    You can also use the microsoft site to look up inforation about the stop message error number.

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

  • Blue Screen (STOP: 0x00000050) when using multiple Agilent34970A devices with a single GPIB

    Hi,
    I am using two test fixtures that contain two Agilent34970A Multimeters and two Sorensen Power Supplies (each test fixture is contaning one Multimeter and one Sorensen Power Supply) that are connected via GPIB cables to a single PCI-GPIB card. Below I have attached two VI's. GPIB_Communication_Experiment_1.vi (Test Fixture 1) and
    GPIB_Communication_Experiment_2.vi (Test Fixture 2) are used to run self test on the
    Agilent34970A multimeters. GPIB_Communication_Experiment_1.vi is talking to one of the Agilent Multimeters and one of the Sorensen Power Supplies (Address 9 for Agilent Multimeter and Address 2 for Sorensen Power Supply) whereas GPIB_Communication_Experiment_2.vi talks to the second Agilent Multimeter and its Sorensen Power Supply (Address 10 for the Multimeter and Address 3 for the Sorense Power Supply).
    The Problem occurs when I try to run these two VI's simultaneously where it generates a "blue screen of death" with a Technical Information : STOP: 0x00000050 (0xF8AC00440, 0x00000000, 0x8041889, 0x00000000).
    This Problem only occurs when trying to run the executables that were built from the attached VI's.
    I have tried to use VISA CLEAR within the while loop as you can see in the VI however it did not improve things.
    I have also uninstalled and re-installed the software for my PCI-GPIB card but that seemed not to work either.
    At this point I am confused.  If I try to run only one Test Fixture at a time I have no problem doing the Self Test on the Agilent Multimeter, yet every single time if I try to run the two test fixtures together I am  gettig the blue screen.
    Besides the two executable VI's I have also attached the regular VI's
    I would really appreciate your help, thanks in advance for your time.
    Attachments:
    GPIB_Communication_Experiment_1.vi ‏23 KB
    GPIB_Communication_Experiment_2.vi ‏23 KB

    Hello aps7828:
    If I read that correct, you only get the error when you run the executables and not the VIs. Can you take a look at your processor level while one .exe is running. I am wondering if that is the source of the problem.
    Regards,
    Roland A.
    Applications Engineer
    National Instruments
    Check out VI Roadshow

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

Maybe you are looking for