IQ846 Memory Dump/BSOD

While using Windows Media Center with Live TV, whether it is Windows Vista, Windows 7 or Windows 8, the application locks up my system after ~20-~30 minutes, with a weird noise from the speakers, and then the BSOD shows up with a mememory dump.  Then I do a hard shutdown. I don't know what the problem is here. Is it the memory, the hard drive, probably not... could it be the power supply though? Would you recommend some preventative measures (so I don't need to do a hard shutdown at every BSOD) in order to keep using Live TV embedded in Windows Media Center? This system is only used for viewing TV, I don't use it as a PVR or personal data storage.
This question was solved.
View Solution.

I ran the DISM /Online /Cleanup-Image /RestoreHealth command and the "component store corruption was repaired." I ran the sfc /scannow command and it didn't give an error any more : "Windows Resource Protection did not find any integrity violations." I am currently running Live TV with no lockups. I'll keep you posted if I run into them again within these couple of days. Thank you for all your help erico.

Similar Messages

  • GT60 0NC - Memory Dumps - BSOD - Replacing RAM

    I just bought my GT60 a month ago and this past weekend my laptop started crashing. BSOD tells me that it was a physical memory dump.
    I ran the Windows Memory Diagnostic test from bootup and the RAM failed 10% into the first pass.
    I was going to RMA the laptop but I didn't feel it was worth sending it back for faulty RAM. In fact I've never heard of the RAM that my laptop came with. So I went ahead and ordered some GSkill ram from Newegg.
    My problem is I have only found 1 stick of the 3 sticks of RAM for my GT60. The first stick I found it the first one you see when you pull off the back plate.
    but I can't find the other 2 sticks.
    Anyone know where they are?

    Quote
    Sometimes my computer doesn't even start after a few times of fail or it only shows 4GB RAM where there are 2x4GB.
    PSU is more than adequate for your system and configuration. For some reason, if the 124 BSOD continues to be a problem,  the CPU V. is being set too low. Always possible the CPU has an extremely high VID. With not all the RAM showing, I suspect a CPU socket pin problem of some or one being bent or damaged. A close inspection of the socket with a bright light and magnifier is recommended.
    Quote
    I used MSI live update 5 to update BIOS and everything.
    In the future, to be much more safe, use the forum's USB flash procedure;
      >> Forum USB Flash Method <<

  • No memory dump files after BSOD

    Hi. I'm experiencing BSOD problem for quite a long time. I really don't know anymore what could be the cause of this problem and i desperately need help about it. I don't know much about this, but I've been told to upload memory dump file so that experts
    may determent what is the cause of my problem. But that is where another problem is. I'm not getting any new memory dump files after my PC crashes. It just stopped ''appearing''. I did everything on this site to enable mini dumps:
    http://www.carrona.org/setmini.html
    But I'm still not getting them... What should i do? Please help me.

    1. Start > type
    %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key +
    Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key +
    Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'. 
    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
    4. Double check
    that the WERS is ENABLED:
    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it
    and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply. 
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • BSOD with BugCheck Error 1001 Memory Dump Help

    Hello, I need a bit of help.  My computer just crashed with a blue screen of death suddenly while I was doing some audio editing (I do this frequently, never had an issue before).  I have no idea what to do with this memory dump I got, so I was
    hoping someone could help me.
    https://onedrive.live.com/redir?resid=3BE2487D830FFF04!107&authkey=!ANb7Ny6ZZXtBfL8&ithint=file%2c.dmp
    That's the link to the memory dump file.  Let me know if you need any other data from me.  Thanks!

    Thompa2
    This was Related to
    lvrs64.sys Kernel Audio Improvement Filter Driver from Logitech Inc.  I would install the newest driver available.  Yours is ~ 2years old.
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0
    Debug session time: Thu Feb 27 00:37:31.119 2014 (UTC - 5:00)
    System Uptime: 0 days 15:35:44.212
    BugCheck 1000007E, {ffffffffc0000005, fffff88002ec1fc6, fffff88007de3758, fffff88007de2fb0}
    Probably caused by : lvrs64.sys ( lvrs64+2fc6 )
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88002ec1fc6, The address that the exception occurred at
    Arg3: fffff88007de3758, Exception Record Address
    Arg4: fffff88007de2fb0, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    lvrs64+2fc6
    fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d
    EXCEPTION_RECORD: fffff88007de3758 -- (.exr 0xfffff88007de3758)
    ExceptionAddress: fffff88002ec1fc6 (lvrs64+0x0000000000002fc6)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000003cd464
    Attempt to read from address 00000000003cd464
    CONTEXT: fffff88007de2fb0 -- (.cxr 0xfffff88007de2fb0;r)
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
    r8=0000000000000000 r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    lvrs64+0x2fc6:
    fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    Last set context:
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
    r8=0000000000000000 r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    lvrs64+0x2fc6:
    fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 00000000003cd464
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100
    GetUlongFromAddress: unable to read from fffff800036b41c0
    00000000003cd464 Nonpaged pool
    FOLLOWUP_IP:
    lvrs64+2fc6
    fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d
    BUGCHECK_STR: 0x7E
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff88002ec1fc6
    STACK_TEXT:
    fffff880`07de3990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`12f495f0 : lvrs64+0x2fc6
    fffff880`07de3998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`12f495f0 00000000`00000000 : 0x1
    fffff880`07de39a0 00000000`00000000 : 00000000`00000000 fffffa80`12f495f0 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: lvrs64+2fc6
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: lvrs64
    IMAGE_NAME: lvrs64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 505cb9b9
    STACK_COMMAND: .cxr 0xfffff88007de2fb0 ; kb
    FAILURE_BUCKET_ID: X64_0x7E_lvrs64+2fc6
    BUCKET_ID: X64_0x7E_lvrs64+2fc6
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x7e_lvrs64+2fc6
    FAILURE_ID_HASH: {4d85bbe7-3359-5d02-03c0-19e8d54c8fdc}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • HP Pavilion dv6 Vista Recovery - Physical memory dump w/ error code 0x000000F4 (and others)

    Hello Everyone, 
    This is my first time posting in the forums so I hope that I have chosen the appropriate area and will do my best to be brief but informative. 
    Computer: HP Pavilion dv6000
    Operating System: Windows Vista.
    For the past 6-8 months it has been unable to perform Windows Update citing that the most likely reason was a virus. I have tried numerous trouble shooting options when it was recommended that I perform a chkdsk. After initiating a chkdsk in Command Prompt, my computer restarted and had a black screen with no cursor. After watching this for 2 hours and realizing that none of the usual chkdsk progress or text was coming up I made the decision to force shut down.
    When I rebooted, I was told to enter system recovery which I did and completed a system recovery from the hard drive. After the system recovery finished and the laptop restarted, I experience a Blue Screen of Death due to a physical memory dump. The error codes are STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006671040, 0xFFFFFA8006671278, 0xFFFFF80001D01DA0). 
    I am not able to boot in safe mode. In the start up repair, I am able to enter command prompt from which I started chkdsk again. Both chkdsk f/ and chkdsk r/ passed with no errors. Additionally, the computer passed both UEFI Hard Drive and Memory tests. I have system recovery CDs for the computer but they fail at 78% completion.
    Please let me know if you have any questions or require anymore information. I would appreciate any and all advice!
    Thank you!
    This question was solved.
    View Solution.

    Hello @GraydonS,
    Welcome to the HP Forums, I hope you enjoy your experience!
    I have read your post on how there is an error message being displayed on your notebook, being a Blue Screen of Death (BSOD), and I would be happy to assist you in this matter!
    Since you are having recovery issues with your system, I recommend following this document on Troubleshooting System Recovery Problems (Windows Vista). This should help you to successfully recover your Operating System.
    If the issue persists, please call our technical support at 1-800-474-6836. If you live outside the US/Canada Region please click the link below to get the support number for your region.
    http://www.hp.com/cgi-bin/hpsupport/index.pl
    I hope this helps!
    Regards  
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • Memory dump in virtual machine

    One of our VMs is restarting frequently and is using a Windows Server 2012 R2.
    From the screenshot it have memory dump.
    Is this a hardware related issue even though it happened on a virtual environment?
    Will we be able to get cause of error if we try using any memory checking tools on the virtual environment? or should it be done on the ESXI host level (physical server)?
    Thanks! 

    Good day.
    Please provide more info. What version of ESXi you are using?
    Are there any errors in windows (guest) system logs? For example if you are running ESXi 5.0 and Windows 2012R2 as guest you could get bsod with 0x00000109 error The Ultimate SysAdmin Fanboy: Resolve bugcheck 0x00000109 CRITICAL_STRUCTURE_CORRUPTION on Windows Server 2012 running i…

  • Running Firefox causes a physical memory dump.

    Every time I try to run the latest version of Firefox on Windows 7 I get a BSOD that shows a physical memory dump with messages like "bad_pool_header" or "system_service_exception." This happens even if I run Firefox in safe mode with all plugins disabled. I don't remember when I last updated Firefox, but I was not having this problem until today. I put my computer to sleep at night, and when I woke up this morning my internet connection was not available, so I had to reset my cable modem. After I regained my connection I found that Firefox was not working. Internet Explorer works fine. (Note that in System Details the listed version of Firefox is not the one I was running - I am currently on a different computer, but I was running the latest version of Firefox when I was having issues.)

    addendum: the problem mentioned above is not solved by the latest update, and the problem not only occurs when using the scrollbar but on various occasions and exclusively when using Firefox. With the use of other applications (including Windows Internet explorer) the memoryproblem does not occur (upto now that is)

  • Not able to memory dump and create a memory.dmp file in the path: %SystemRoot%\Minidump

    This question is a part of my job profile. I work for an MNC chip maker. As a part of our systems testing environment, we boot into the Microsoft windows 8.1 windows OS and run some specific tests from the OS. The platform design (mother board) is an internal
    design.
    Issue is with the booting sequence since no much information is available when Windows 8.1 tries to boot and when we see the splash screen. Especially when we see a BSOD, there had been no leads.
    I tried to enable the small memory dump option in Windows 8.1 OS which tries to write the files into the location %SystemRoot%\Minidump on a system crash while boot. Please note that Windows 8.1 has been stored as a .VHD file in the hard disk (which
    is the boot-disk). The issue is, even in an event of a BSOD while booting, I am not able to see any memory dump files that had been logged in that location.
    Is this issue would have been caused by the VHD file format since it is a virtualized disk ? Please let me know what all the issues could be, so that I can have some memory logs here to look into. May be analyze the Windows debugger.
    Best Regards
    Akhil

    Hi,
    The causes why Windows does not save memory dump file after a crash are listed in the link below:
    http://support.microsoft.com/kb/130536
    I suggest you check the space, make sure that there's enough room for the memory dump file.
    And this blog can also be helpful
    No kernel memory dump created on Windows 7 or Windows 8
    http://blogs.technet.com/b/yongrhee/archive/2012/08/27/no-kernel-memory-dump-created-on-windows-7-or-windows-8.aspx
    Yolanda Zhu
    TechNet Community Support

  • IPOD causes "Blue Screen of Death" with physical memory dump

    Plugged in the IPOD into USB port on computer. It shows "found USB device" and then 5-10 seconds later I get the blue screen of death and a notification that there is a driver error and a physical memory dump as occurred.
    Spent two hours with Apple people and Dell people this morning and nothing. I have updated drivers, flashed my bios, uninstalled and then reinstalled the latest version of Itunes.
    Any help would be greatly appreciated.

    what numerical and text codes are you getting with it? (ie 0x[zeros/letters/numbers] CAPSANDUNDERSCORES)
    if the blue screen mentions a specific file, let us know what that is called too. (exact spelling, please.)
    here's a reference on the sorts of things i'm asking about:
    Troubleshooting Windows Stop Messages
    if you're just seeing a flash of a blue screen, we can use this technique to make hidden blue screens appear for us:
    1) Open your system control panel (Start->Control Panels->System).
    2) Select the "Advanced" tab.
    3) Click the "Startup and Recover" section's "Settings" button
    4) Verify that under "System Failure" the "Automatically restart" checkbox is not checked.

  • Blue Screen re: Physicial Memory Dump on HP Pavilion DV6-3210-US

    Hello. I am running Windows 7 and recently have been getting this bright blue screen with a ton a words on it but I can only pick out CRASH DUMP and PHYSICAL MEMORY DUMP from this before it just disappears. In a couple of cases it tried to run a service repair and didn't let me choose to run in anything but safe mode. It has also let me choose what mode to run.
    I took it to a computer repair company and they put a new hard drive on my computer, tuned it up and sent me on my way. I've had it back 2 days and I just got the error again. I have a 30 day guarantee on my repair and probably should take it back but they didn't fix it the first time. I don't think they knew what this was and went for what they knew they could do easily.
    What do I do?

    Hello SandykUtah.
    The two most common causes of blue screen errors are problems with either the hard drive or the memory.  Your notebook has diagnostics for both of these pieces of hardware.  I suggest running them both in addition to the advice suggested above by maxpower757.  
    This document covers running the hard drive test.  Simply repeat the process and select "memory test" to run the RAM test.  
    Make sure to post the results.  I hope you have a great day!
    Please click the white star under my name to give me Kudos as a way to say "Thanks!"
    Click the "Accept as Solution" button if I resolve your issue.

  • Windows 7 - Memory Dump problem ! Blue screen of death !! HELP

    Hey guys,
    I have an iMac 27 inch 2011  running Windows 7 home premium 64bit using bootcamp. My computer specs are
    I Mac OSX 10.7  
    CPU - Intel i7 3.4 ghz quad core
    RAM - (16 gb )
    VIDEO - ATI Radeon HD 2 GB
    I installed windows 7 on my imac using bootcamp today. It was working fine until i started installing things and i ran into the blue screen of death saying Memory dump. This message only shows for about 2 seconds and then restarts my computer. It randomly happens, such as internet explorer or just on my homescreen.
    Thanks in advance for you help. 
    Thank you

    To locate any of the forums click the Apple Support Communities link in the upper left of this page, then type in the first word of what you're looking for.
    As for returning the machine no, I suspect you just have an installation problem. Macs run MS Windows in Boot Camp better than most dedicated Windows boxes.

  • Blue screen hard disk dump AND memory dump

    I sent my toshiba satellite a215-s4767 to the repair depot for a screen replacement and since i got it back i have had 2 blue screen memory dumps and 1 hard disk dump blue screen(that was last night). I got it back on christmas eve so ive had it back for 2 weeks.

    Please take a look at this document USB 3.0 Blue Screen Document. Verify your USB 3.0 chipset is the same as described in the document and if it is the same download the fix from Intel.
    Best regards,
    I am an HP employee

  • Windows 2003 Memory Dump - Bug check Analysis attached

    Hi all
    I recently have had a Windows 2003 Standard with SP2 server crash with a memory dump
     I have used WinDBG to read the file and output below
    can anyone shed any light on the faults, or point me in the right direction?
    *                        Bugcheck Analysis                                   
    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8081c630, The address that the exception occurred at
    Arg3: b7487c30, Trap Frame
    Arg4: 00000000
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    nt!IoGetAttachedDevice+c
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
    TRAP_FRAME:  b7487c30 -- (.trap 0xffffffffb7487c30)
    ErrCode = 00000000
    eax=000007f6 ebx=85e76068 ecx=000007f6 edx=00000000 esi=85e76068 edi=89d42020
    eip=8081c630 esp=b7487ca4 ebp=b7487ca4 iopl=0         nv up ei pl nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
    nt!IoGetAttachedDevice+0xc:
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h] ds:0023:00000806=????????
    Resetting default scope
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  DocTransport.ex
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    LAST_CONTROL_TRANSFER:  from 8082db20 to 80827f7d
    STACK_TEXT: 
    b74877fc 8082db20 0000008e c0000005 8081c630 nt!KeBugCheckEx+0x1b
    b7487bc0 8088c12a b7487bdc 00000000 b7487c30 nt!KiDispatchException+0x3a2
    b7487c28 8088c0de b7487ca4 8081c630 badb0d00 nt!CommonDispatchException+0x4a
    b7487ca4 8081c7e1 89d42020 b7487d64 00000000 nt!KiExceptionExit+0x186
    b7487cb8 808f44c7 85e76068 b7487d64 08a9ea50 nt!IoGetRelatedDeviceObject+0x63
    b7487d38 8088b658 00001e20 00000000 00000000 nt!NtReadFile+0x55
    b7487d38 7c82845c 00001e20 00000000 00000000 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    08a9ea8c 00000000 00000000 00000000 00000000 0x7c82845c
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!IoGetAttachedDevice+c
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt!IoGetAttachedDevice+c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrpamp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51d4c567
    IMAGE_VERSION:  5.2.3790.5190
    FAILURE_BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
    BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x8e_nt!iogetattacheddevice+c
    FAILURE_ID_HASH:  {22c1c728-5bf3-efb9-fff4-40d5ae0d47e2}
    Followup: MachineOwner

    Hi,
    For Bug Check 0x8E, it
    indicates that a kernel-mode application generated an exception that the error handler did not catch. For more details, please refer to following article and check if can help you.
    Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Did you remember that which operation (or any change) you do before this issue occurred? Or just the server
    crashed suddenly?
    Please check if all necessary updates were installed and drivers were updated.
    à
    PROCESS_NAME: 
    DocTransport.exe
    Did you install any third-party application on the server? Please
    perform a clean boot and monitor the result.
    By the way, as you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. However, it is not
    effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Hope this helps.
    Best regards,
    Justin Gu

  • Database memory dump (please help!!!!!).

    Hello people,
    I have a big problem with one of the database of my company, it seems that is a memory fail when try to allocate space or something, i search the Metalink looking for a solution but, I really don´t know what is the real problem of this memory dump, in the alert log that post down shows error in the TRC file, but there only shows the dump memory not the cause of this, we have big datafiles with a lot of data, I dont know if this is because the DBF files contain too much data or what..... the ORA-07445 seems that is a very generic error, and I dont have any tips to search the original error.
    Can be this error because the server don´t have big resources?, the configuration of the server are:
    XEON 1 core 4 cpu´s
    4gb ram
    1TB hard disk
    Windows 2003 standard edition
    Oracle 10g 10.2.0.1 standard edition.
    All in 32bits, ¿do you recommend migrating to 64bits for the 2gb memory limit of users in W2003?
    ¿The big datafiles and big tablespaces can be an issue for this memory dump? ¿Oracle 11g manages better big files that Oracle10g?
    Please if your need any more info of configuration or something, please tellme.
    Thanks for all your answers.
    ALERT.LOG
    Mon May 31 11:44:15 2010
    Errors in file e:\oracle\product\10.2.0\admin\udump\orcl_ora_1620.trc:
    ORA-07445: se ha encontrado una excepción: volcado de memoria [ACCESS_VIOLATION] [_kglrfcl+313] [PC:0x603F7EE5] [ADDR:0x4] [UNABLE_TO_WRITE] []
    Mon May 31 11:44:19 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_pmon_2104.trc:
    ORA-00600: internal error code, arguments: [1100], [0x4FCCB9FC], [0x4A54A8EC], [], [], [], [], []
    Mon May 31 11:44:20 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_pmon_2104.trc:
    ORA-00600: internal error code, arguments: [1100], [0x4FCCB9FC], [0x4A54A8EC], [], [], [], [], []
    Mon May 31 11:44:20 2010
    PMON: terminating instance due to error 472
    Mon May 31 11:44:22 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_psp0_3604.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:22 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_j000_3844.trc:
    ORA-00472: proceso PMON terminado con error
    Mon May 31 11:44:22 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_mman_3760.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:23 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_lgwr_360.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:23 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_ckpt_2112.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:24 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_q001_952.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:24 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_dbw0_1444.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:26 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_reco_1256.trc:
    ORA-00472: PMON process terminated with error
    Mon May 31 11:44:26 2010
    Errors in file e:\oracle\product\10.2.0\admin\bdump\orcl_smon_2504.trc:
    ORA-00472: PMON process terminated with error
    Instance terminated by PMON, pid = 2104

    I have tracked the SQL that hangs up the database but is a SQL that works always not only once, but there is something that when the database is with too many resources this crash the DB and not always is the same SQL. I have searched any tip or solution on the metalink but nothing is like this error.
    I don´t know if anyone can help me with this... I have open an request via Metalink but i dont know if going to be any solution to this error.
    Thanks anyway.

  • Several LR3 issues - Crashes, memory dumps, and other oddities

    I recently built a new PC dedicated to my photo work.
    i7 2600k, 16gb DDR 3 ripjaws, 128GB crucial m4 SSD, (2) x 1TB 7200 HDDs (mirrored), Sapphire Radeon HD 5570.
    The first month or so of use LR worked great. However, recently I have been getting several errors and oddities.
    1) Randomly closes. I can restart it without a problem and pick back up where I left off. There are not warnings or signs that it is about to close.. it just does.
    2) "Unexpected end of file". Unable to edit photo. Preview does show, however. I have never seen this error before on other machines.
    3) Memory dumps. I assume this is related to LR3 as that is the only program I am actively using when it happens (Chome is always open as well, however) I will have the dump files examined to know for sure.
    4) Something new that just started today. In the preview bar on the bottom, as I scroll through the photos I see the previews of other photos.. some photos from other folders I took weeks or months ago. When I hover over the image it changes to what it should be. I am seeing 2 instances of this. 1 with a photo from this particular shoot and one from one I did over a month ago. Everything I scroll back and forth (rapidly or not) as the previews load it loads the wrong files first, multiple times (around 8 or 9 in a row) and then they slowly change to what it should be.
    I am not sure if I am properly describing this error but it is really weird.
    Also, this seems to only happen on the images off a CF card. I was borrowing a friends D200 as a 2nd body for a party. When I scroll through the images off my SD card I do not see the issue appear. When I get to the CF portion of the folder is when I see the problem....
    I just updated LR today but these issues occured prior to the update and still exist afterwards.
    Do I need to do a fresh install of LR?
    What precautions do I need to take in doing so to insure my catalogue stays intact?
    Thanks for your help.

    I am still having issues.
    The crash dumps are far less frequent now. I think it may have been a catalogue issue maybe? I started a new one and things were better.
    However, I am consistantly getting the "Lightroom has stopped working" and it closes down..... repeatedly. Very Very annoying.
    It is not a major issue to just restart Lightroom, esp since it is on an SSD, it pops right back up instantly.
    All of my files are on the HDD, however, not the SSD.
    I had reinstalled LR3 once before which did not help. Any other suggestinos?
    I can't imagine a reinstall of Windows would do anything for me. I have no issues with anything other than LR.
    Could my video card be playing a role in the errors? I do notice weird random artifacts in my images sometimes when I add a brush stroke, or clone something out. Or sometimes just simply zooming in will great these weird multicolored lines in the image. Zooming out makes it go away. It is random when it shows up and often times closing and reopening LR will make it go away. So these are not permanent artifacts in the image unless I export the file with them showing. This leads me to think maybe the video card is having some issues. All drivers are up to date. It is not a high end card. Based on all my research when buidling this machine, a basic video card is all that is needed as RL is CPU and memory intensive, which is where I put most of my $. (i7 2600k and 16GB DDR3)

Maybe you are looking for