BSOD Locale ID:1033

Hello,
Recently for no real reason that I can see, I started getting this error.
Problem signature:
  Problem Event Name:BlueScreen
  OS Version:6.1.7601.2.1.0.256.1
  Locale ID:1033
Additional information about the problem:
  BCCode:1000007e
  BCP1:FFFFFFFFC0000005
  BCP2:FFFFF8800F59ADBB
  BCP3:FFFFF88002BF4228
  BCP4:FFFFF88002BF3A80
  OS Version:6_1_7601
  Service Pack:1_0
  Product:256_1
Files that help describe the problem:
  C:\Windows\Minidump\052414-16582-01.dmp
  C:\Users\Nephoros\AppData\Local\Temp\WER-29936-0.sysdata.xml
From what I noted, its completly random, it happens when I play wow, and if only then, I am uncertain.
Please assist me so that this will not happen again.

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
If your computer is not generating .DMP files, please do the following:
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.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Similar Messages

  • BlueScreen of Death. Windows 7 (64-bit) Locale ID: 1033

    Hello. I keep happening to get errors, when the computer Idles or goes in sleep mode. This isn't the first time, either.
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 116
      BCP1: FFFFFA8003EA34E0
      BCP2: FFFFF8800409EDC0
      BCP3: 0000000000000000
      BCP4: 000000000000000D
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\042514-19843-01.dmp
      C:\Users\Zach\AppData\Local\Temp\WER-70481-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
    Minidump: https://onedrive.live.com/?cid=f535c11f3f3b6b66&id=F535C11F3F3B6B66%21134#cid=14F604FB3205F70D&id=14F604FB3205F70D%21105

    ZV
    Two issues.  The driver verified crash was related to readyboost.  I would turn it off at least to test, the others were called BCC116
    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
    If so, it might be as simple as dust buildup and subsequently inadequate cooling.
    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
    For more information please read this blog  http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
    Bugcheck code 00000116
    Bugcheck code 00000116
    Bugcheck code 00000116
    Bugcheck code 0000007F
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 1 days 11:16:46.716
    System Uptime: 2 days 4:48:03.890
    System Uptime: 2 days 5:21:56.656
    System Uptime: 0 days 0:00:14.976
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Apr 25 04:47:05.280 2014 (UTC - 4:00)
    System Uptime: 1 days 11:16:46.716
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Apr 23 16:38:38.470 2014 (UTC - 4:00)
    System Uptime: 2 days 4:48:03.890
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 04:18:13.236 2014 (UTC - 4:00)
    System Uptime: 2 days 5:21:56.656
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Sat Nov 9 07:15:24.664 2013 (UTC - 4:00)
    System Uptime: 0 days 0:00:14.976
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
    BUGCHECK_STR: 0x7f_8
    PROCESS_NAME: System
    Wanikiya and Dyami--Team Zigzag

  • Windows BlueScreen Locale ID: 1033

    Hi Guys, This is my first attempt at using this forum so excuse me if I haven't provided all the necessary information.
    I have found recently that my computer has started to BSOD when playing games I'm wondering If my graphics card is on the way out.
    The following is the Problem Signature.
    Source
    Windows
    Summary
    Shut down unexpectedly
    Date
    ‎11/‎9/‎2013 7:40 AM
    Status
    Not reported
    Problem signature
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033
    Files that help describe the problem
    110913-47720-01.dmp
    sysdata.xml
    WERInternalMetadata.xml
    Extra information about the problem
    BCCode: a
    BCP1: 0000000000000001
    BCP2: 0000000000000002
    BCP3: 0000000000000001
    BCP4: FFFFF80004898DE4
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
    Regards
    Dave

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    Wanikiya and Dyami--Team Zigzag

  • Blue Screen of Death Windows 7 - (64bit) - Locale ID: 1033

    Hello there. I've been having issues with the blue screen that has been frequently occurring. I don't know a whole lot about computers so I was hoping if you could help me out. The Information regarding the bluescreen is below. 
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004C9EE62
      BCP3: FFFFF880039854B8
      BCP4: FFFFF88003984D10
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\052214-21200-01.dmp
      C:\Users\Spencer\AppData\Local\Temp\WER-111119-0.sysdata.xml

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    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.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Windows 7, Blue Screen Local ID: 1033

    Lately i get this Blue Screen error and i have no idea what i should do:
    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.1
      Locale ID:    1033
    Additional information about the problem:
      BCCode:    50
      BCP1:    FFFFFAFDF700001A
      BCP2:    0000000000000000
      BCP3:    FFFFF80003178F5C
      BCP4:    0000000000000005
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1
    Files that help describe the problem:
      C:\Windows\Minidump\020214-15740-01.dmp
      C:\Users\Maria\AppData\Local\Temp\WER-47221-0.sysdata.xml

    MH
    These were related to amifldrv64.sys belong to CLICKBIOSII module developed by MSI.  I would install the newest driver available.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Machine Name:
    Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03056670
    Debug session time: Tue Sep 17 10:40:08.022 2013 (UTC - 5:00)
    System Uptime: 0 days 0:00:28.849
    Loading Kernel Symbols
    BugCheck 50, {fffffaf5b100001a, 0, fffff80002f7af5c, 5}
    *** WARNING: Unable to verify timestamp for amifldrv64.sys
    *** ERROR: Module load completed but symbols could not be loaded for amifldrv64.sys
    Could not read faulting driver name
    Probably caused by : amifldrv64.sys ( amifldrv64+188c )
    2: kd> !analyze -v
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffaf5b100001a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002f7af5c, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c0100
    GetUlongFromAddress: unable to read from fffff800030c01c0
    fffffaf5b100001a Nonpaged pool
    FAULTING_IP:
    nt!MmFreeContiguousMemory+ec
    fffff800`02f7af5c f6411a20 test byte ptr [rcx+1Ah],20h
    MM_INTERNAL_CODE: 5
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0x50
    PROCESS_NAME: SCEWIN_64.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME: fffff8800b252610 -- (.trap 0xfffff8800b252610)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000058000000000 rbx=0000000000000000 rcx=fffffaf5b1000000
    rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f7af5c rsp=fffff8800b2527a0 rbp=fffff8800b252b60
    r8=fffffa800a0ae010 r9=00000000000000a0 r10=fffffa800670b210
    r11=fffffa800a0ae010 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po cy
    nt!MmFreeContiguousMemory+0xec:
    fffff800`02f7af5c f6411a20 test byte ptr [rcx+1Ah],20h ds:fffffaf5`b100001a=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80002f055a3 to fffff80002e88c00
    STACK_TEXT:
    fffff880`0b2524a8 fffff800`02f055a3 : 00000000`00000050 fffffaf5`b100001a 00000000`00000000 fffff880`0b252610 : nt!KeBugCheckEx
    fffff880`0b2524b0 fffff800`02e86d2e : 00000000`00000000 fffffaf5`b100001a fffffa80`08a81a00 fffff880`0273d000 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`0b252610 fffff800`02f7af5c : fffffa80`0a0ae010 fffff880`0a4014e7 fffffa80`1fffc000 fffffa80`0a306290 : nt!KiPageFault+0x16e
    fffff880`0b2527a0 fffff880`0a40188c : fffffa80`0a0ae010 fffffa80`08a81980 fffffa80`08a81980 00000000`00000016 : nt!MmFreeContiguousMemory+0xec
    fffff880`0b2527e0 fffffa80`0a0ae010 : fffffa80`08a81980 fffffa80`08a81980 00000000`00000016 fffff800`03018730 : amifldrv64+0x188c
    fffff880`0b2527e8 fffffa80`08a81980 : fffffa80`08a81980 00000000`00000016 fffff800`03018730 fffffa80`08a81980 : 0xfffffa80`0a0ae010
    fffff880`0b2527f0 fffffa80`08a81980 : 00000000`00000016 fffff800`03018730 fffffa80`08a81980 fffffa80`0a269b10 : 0xfffffa80`08a81980
    fffff880`0b2527f8 00000000`00000016 : fffff800`03018730 fffffa80`08a81980 fffffa80`0a269b10 fffff880`0a4019b4 : 0xfffffa80`08a81980
    fffff880`0b252800 fffff800`03018730 : fffffa80`08a81980 fffffa80`0a269b10 fffff880`0a4019b4 00000000`00000001 : 0x16
    fffff880`0b252808 fffffa80`08a81980 : fffffa80`0a269b10 fffff880`0a4019b4 00000000`00000001 00000000`00000001 : nt!NonPagedPoolDescriptor+0x1b0
    fffff880`0b252810 fffffa80`0a269b10 : fffff880`0a4019b4 00000000`00000001 00000000`00000001 00000000`000000a8 : 0xfffffa80`08a81980
    fffff880`0b252818 fffff880`0a4019b4 : 00000000`00000001 00000000`00000001 00000000`000000a8 fffff800`02f93744 : 0xfffffa80`0a269b10
    fffff880`0b252820 00000000`00000001 : 00000000`00000001 00000000`000000a8 fffff800`02f93744 00000000`00000000 : amifldrv64+0x19b4
    fffff880`0b252828 00000000`00000001 : 00000000`000000a8 fffff800`02f93744 00000000`00000000 fffffa80`0a306290 : 0x1
    fffff880`0b252830 00000000`000000a8 : fffff800`02f93744 00000000`00000000 fffffa80`0a306290 fffffa80`0a269b10 : 0x1
    fffff880`0b252838 fffff800`02f93744 : 00000000`00000000 fffffa80`0a306290 fffffa80`0a269b10 fffff880`0a401bff : 0xa8
    fffff880`0b252840 fffff880`0b252928 : fffff880`0b252968 fffffa80`0a41b060 00000000`00000001 fffff880`0b252960 : nt!EtwpCCSwapTrace+0x4d4
    fffff880`0b252900 fffff880`0b252968 : fffffa80`0a41b060 00000000`00000001 fffff880`0b252960 00000008`0a43ab01 : 0xfffff880`0b252928
    fffff880`0b252908 fffffa80`0a41b060 : 00000000`00000001 fffff880`0b252960 00000008`0a43ab01 fffffa80`0a306290 : 0xfffff880`0b252968
    fffff880`0b252910 00000000`00000001 : fffff880`0b252960 00000008`0a43ab01 fffffa80`0a306290 00000000`00000008 : 0xfffffa80`0a41b060
    fffff880`0b252918 fffff880`0b252960 : 00000008`0a43ab01 fffffa80`0a306290 00000000`00000008 00000000`00000000 : 0x1
    fffff880`0b252920 00000008`0a43ab01 : fffffa80`0a306290 00000000`00000008 00000000`00000000 fffffa80`0a269b10 : 0xfffff880`0b252960
    fffff880`0b252928 fffffa80`0a306290 : 00000000`00000008 00000000`00000000 fffffa80`0a269b10 00000000`00000000 : 0x00000008`0a43ab01
    fffff880`0b252930 00000000`00000008 : 00000000`00000000 fffffa80`0a269b10 00000000`00000000 fffffa80`06743820 : 0xfffffa80`0a306290
    fffff880`0b252938 00000000`00000000 : fffffa80`0a269b10 00000000`00000000 fffffa80`06743820 fffffa80`0a3062e0 : 0x8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    amifldrv64+188c
    fffff880`0a40188c ?? ???
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: amifldrv64+188c
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: amifldrv64
    IMAGE_NAME: amifldrv64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4accc6d8
    FAILURE_BUCKET_ID: X64_0x50_amifldrv64+188c
    BUCKET_ID: X64_0x50_amifldrv64+188c
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x50_amifldrv64+188c
    FAILURE_ID_HASH: {2881f1e0-4106-fe9b-c0f6-de1062eca6a6}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Blue Screen Of Death (Please help) Locale ID: 1033

    So this computer is only 1 year old, I got this computer from cyberpower and the computer has been alright until out of no where i have been getting this blue screen
    This is the information it gives me about it, can someone please help me resolve this
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88011184DBB
      BCP3: FFFFF88003E72228
      BCP4: FFFFF88003E71A80
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\061014-20342-01.dmp
      C:\Users\Toktz1\AppData\Local\Temp\WER-31746-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

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    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.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • BSOD System_Service_Exception and Driver_Verifier_Detection on HP m9520f PC

    Hello,
    I recently re-formatted and reinstalled Windows 7 Ultimate 64x on my HP Pavilion Elite m9520f PC.
    I encountered the BSOD crashes several times a day of having the "System_Service_Exception 0x0000003B" and DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 error. The system automatically restarts when the BSOD takes place.
    I have installed the most recent NVIDIA GeForce 9600 GS driver update to see if it solves the problem but nothing was solved. I also went to the Advanced Boot Options and did the last known good configuration option but did not work. More information on how to solve this problem would be sincerely appreciated.
    Here's both of the problem signatures:
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF880016537E7
    BCP3: FFFFF88006810E70
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    AND
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional information about the problem:
    BCCode: c4
    BCP1: 0000000000000091
    BCP2: 0000000000000002
    BCP3: FFFFFA800A8D9710
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    This question was solved.
    View Solution.

    Unplug the PC from household power.
    Remove the memory modules.
    Put a single stick of memory into the slot nearest the CPU.
    Once that is done you can plug the PC back in to see if it boots up.  
    If it does not boot up then unplug the PC.  Remove that memory module and put the other module in its place, plug in the PC and try booting up again. 
    ****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

  • Windows Server 2008 R2 won't boot after replacing hardware (BSOD 0x0000007B)

    My problem in a nutshell: I moved, the PC (without the HD) got totalled, I ordered a new machine with the exact same hardware. Meanwhile, I tried to copy some files to another machine by plugging in the HD externally, but all files in the
    /User/Documents/ folder are protected/encrypted (I didn't encrypt them). I fiddled around with the rights and ownership of those files but to no avail, and I was later unable to revert the changes I made. So I guess I should probably not have done that. Anyway,
    the new machine eventually arrived, I plugged in the HD, and after loading AtiPcie.sys I was greeted by a BSOD that immediately forced a reboot.
    Edit: I now know what the BSOD message is, but if I edit it into this post it breaks the formatting for some reason. See my reply further down in this thread for the error message.
    Here's a list of things I did in my vain attempts at solving the problem:
    Safe mode
    No effect at all, except that the (probably same) BSOD occurs after loading CLASSPNP.sys instead.
    Various hardware checks including chkdsk
    No problems found. To be certain, I plugged in another HD and installed Win2k on it. It boots just fine.
    Recovery console: bootrec /rebuildbcd
    The operation "completed successfully" (after renaming the old BCD file) but had no effect.
    Recovery console: bootrec /fixmbr, bootrec /fixboot, bootsect /nt60 all
    Same as above, except now the list of drivers loaded during startup is replaced by a Windows logo and a loading bar. I preferred the list.
    StartRep.exe
    After a while, this gave me an error with the following problem signature (from memory, I didn't think I would be unable to replicate it later):
    Problem Event Name: StartupRepairOffline
    Problem Signature 01: 6.1.7600.16385
    Problem Signature 02: 6.1.7600.16385
    Problem Signature 03: unknown
    Problem Signature 04: (sth long, don't remember)
    Problem Signature 05: ExternalMedia
    Problem Signature 06: 13 (I think)
    Problem Signature 07: BadDriver
    OS Version: 6.1.7601.2.1.0.256.1 (or sth like this)
    Locale ID: 1033
    The only external devices at that point apart from the monitor were a USB keyboard and a USB mouse. Ever since that scan, StartRep.exe immediately completes with no problems found. Also, BSOD on reboot as usual.
    Removed AtiPcie.sys and atikmdag.sys
    Didn't seem to do anything.
    I'm out of options now, and I'm reluctant to reinstall Windows since it seems this might permanently make the user documents inaccessible. Any suggestions how I might get that machine running again, preferably without losing those protected documents?

    Boot the installation media and if it sees the existing install then you can choose to upgrade.
    I do have an option to upgrade, but when I select it I get to a screen with this text:
    The computer started using the Windows Installation disc. Remove the Installation disc and restart your computer so that Windows Starts normally. Then, Insert the installation disc and restart the upgrade. (Do not select "Custom (advanced)"
    to perform an upgrade. "Custom (advanced)" installs a new copy of windows and deletes your programs and settings.)
    Since I can't boot Windows, this isn't an option. The line "Custom (advanced)" installs a new copy of windows and deletes your programs and settings.) is exactly what I want to avoid since it would presumably make the
    protected user files inaccessible.
    Hi
    You can check the HDD mode in the BIOS, even if the same hardware, I know the HDD mode can be set on another mode (raid versus jbod). Thus the driver last used will not be the same.
    I can find only one such option in the BIOS (Integrated Peripherals -> On-Chip ATA Devices -> RAID Mode) and the current setting is IDE with the alternatives being RAID and AHCI. I don't think that's what you're referring to though.
    Other question: Is there any way to find out more about the BSOD from some dumpfiles via the recovery console, or something?

  • Getting BSOD error message and PC restarting upon startup...

    Can someone help me in resolving my PC problem please?
    2 days ago, I started getting a BSOD with a message that popped up so fast, I couldn't read it. It then asked me how I wanted to start Windows, and I pick normally. It takes an extremely long time to start up, but it does start. It then seems to function
    OK. I shutdown normally and the next time I turn my pc on, got the same thing.
    I have not installed any new software except for the Windows updates. My pc is approximately 2 years old, they usually last 5 years for me. No new hardware. Today I opened it up, cleaned it out and reseated the RAM.
    I have run the SMART utility at the command prompt to check the hd and it tells me OK OK.
    Upon shutting down tonight, and on the next startup, I will have the pc run the memory test.
    I was able to find this:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.256.48
      Locale ID: 1033
    Additional information about the problem:
      BCCode: fc
      BCP1: FFFFF8A006D24920
      BCP2: E2400001EAD0A963
      BCP3: FFFFF8800378C5B0
      BCP4: 0000000000000002
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1
    What does this mean? It looks to me like locations in the RAM, but I'm not sure. Could this mean my RAM has gone bad?
    I have tried to report/check for solutions, but it keeps asking me to send more information, and when I try to send it, it tells me there is a problem with the Windows Error Reporting system.
    I don't see any problems that need fixing in my Action Center.
    I did scan for malware using Malware bytes and found 1 item which I then cleaned out. I have re-scanned several times and have come up clean.
    Can anyone point me in the right direction to solving this problem please?
    Thank You!

    Hi,
    The dump file can not be opened directly, we need to use a debugger tool to open and analyze the file, we usually use WinDbg, you can get it from the MSDN website, to analyze the file, you can find many WinDbg related articles in the msdn websites
    if you're interested with it.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx
    If you have problems analzing the file, please upload the latest dump file to OneDrive, then share the download link with us.
    http://windows.microsoft.com/en-in/onedrive/share-file-folder
    Yolanda Zhu
    TechNet Community Support

  • Chronic BSOD with Lenovo ThinkPad 430s - WHAT do I do? Thank you.

    Dear Community,
    I have had chronic crashes to BSOD since I got my Lenovo ThinkPad 430s with Professional Windows 7, and latest BIOS. Current on Windows updates. I understand there is an Intel problem.
    Therre is no  predicting the BSOD, and no prevention that I cannot figure.
    How do I proceed to get this corrected? Thank you. Roy Waller   [email protected]
    Lenovo T430s
    Windows 7 Professional
    System Model 2352CTO
    x64 based PC
    Processor Intel (R) Core i5-3320MCPU @ 2.60 GHz, 2601 Mhz, 2 Core (s), 4 Logical Processors
    BIIOS Version/Date LENOVO G7ET94WW (2.54), 4/30/2013
    Solved!
    Go to Solution.

    Here is the information from a BSOD crash months ago. I will try to gather the data on the next BSOD. I know this is a stupid question, but where would I find the serial number of this Lenovo Thinkpad 430s. I am certain I purchased this computer a little more than a year ago. The BSOD has been a problem from the beginning. I am a physician, retired, teaching Honors Anatomy & Physiology - pro bono- in a local high school. When the BSOD problem occurred, I just went to my old Apple MacBook and forgot about the T430s.
    Problem signature:
      Problem Event Name:                        BlueScreen
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
    Additional information about the problem:
      BCCode:                                               124
      BCP1:                                                    0000000000000000
      BCP2:                                                    FFFFFA8006C9C028
      BCP3:                                                    00000000B2000000
      BCP4:                                                    0000000000100402
      OS Version:                                          6_1_7601
      Service Pack:                                       1_0
      Product:                                               256_1
    Files that help describe the problem:
      C:\Windows\Minidump\072113-35022-01.dmp
      C:\Users\Sonny\AppData\Local\Temp\WER-67314-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

  • BSOD after closing Itunes (newest version, also older versions) error: Reference by pointer 0x000000018

    Every time I close Itunes I get a BSOD in windows vista ultimate 64bit error I get in BSOD : Reference by pointer error code 0x000000018.
    Looked for dumpfile but no dumpfile created.
    Allready uninstalled Itunes and all apple software following some tips I found on the internet in correct order, reinstalled same problem occurs.
    I believe it must have to do something with apple mobile device software, but when I remove that software Itunes can't find the mobile devices
    anymore.

    Guys,
    I'm in the same boat, close iTunes 11.0.4.4 and BSOD. When it is open everything is fine!
    Running Vista
    I'm good with computers....but not at the level that know what the message means.
    Can you offer any help? Is this the same problem you are having?
    Cheers
    Steve
    Problem signature:
      Problem Event Name:                     BlueScreen
      OS Version:                                     6.0.6002.2.2.0.768.3
      Locale ID:                                        1033
    Additional information about the problem:
      BCCode:                                          18
      BCP1:                                               88903D38
      BCP2:                                               8C59FD90
      BCP3:                                               00000001
      BCP4:                                               00000001
      OS Version:                                     6_0_6002
      Service Pack:                                    2_0
      Product:                                          768_1
    Files that help describe the problem:
      C:\Windows\Minidump\Mini072313-01.dmp
      C:\Users\Steve Rusk\AppData\Local\Temp\WER-75406-0.sysdata.xml
      C:\Users\Steve Rusk\AppData\Local\Temp\WER42A1.tmp.version.txt
    Read our privacy statement:
      http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

  • 0xC0000005 error on startup no BSOD

    i've been getting the this error 0xC000000D. the topic at http://social.technet.microsoft.com/Forums/windows/en-US/ce8f9d22-b5cc-4378-8e97-92d615030b5c/session-microsoft-security-essentials-oobe-stopped-due-to-the-following-error-0xc000000d-using has
    brought me 0 results. this error is not associated with a BSOD. instead it happens at log in with very slow start up time.
    this warning message also comes at the same time as this error
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL -
     1 user registry handles leaked from \Registry\User\S-1-5-21-1901419260-3906909440-2995065001-1000:
    Process 1296 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1901419260-3906909440-2995065001-1000
    Problem Details brings up this.
    Problem Event Name:    APPCRASH
    Application Name:    Explorer.EXE
    Application Version:    6.1.7600.16450
    Application Timestamp:    4aebab8d
    Fault Module Name:    SHLWAPI.dll
    Fault Module Version:    6.1.7600.16385
    Fault Module Timestamp:    4a5be059
    Exception Code:    c0000005
    Exception Offset:    0000000000007656
    OS Version:    6.1.7600.2.0.0.768.3
    Locale ID:    1033
    Additional Information 1:    cfde
    Additional Information 2:    cfde40d2947ae30049954a76bd1df2fb
    Additional Information 3:    15bc
    Additional Information 4:    15bcac7c5df11c3174523e464068ba30
    malware is not an issue. scans bring up nothing.

    i've been getting the this error 0xC000000D. the topic at http://social.technet.microsoft.com/Forums/windows/en-US/ce8f9d22-b5cc-4378-8e97-92d615030b5c/session-microsoft-security-essentials-oobe-stopped-due-to-the-following-error-0xc000000d-using has
    brought me 0 results. this error is not associated with a BSOD. instead it happens at log in with very slow start up time.
    this warning message also comes at the same time as this error
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL -
     1 user registry handles leaked from \Registry\User\S-1-5-21-1901419260-3906909440-2995065001-1000:
    Process 1296 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1901419260-3906909440-2995065001-1000
    Problem Details brings up this.
    Problem Event Name:    APPCRASH
    Application Name:    Explorer.EXE
    Application Version:    6.1.7600.16450
    Application Timestamp:    4aebab8d
    Fault Module Name:    SHLWAPI.dll
    Fault Module Version:    6.1.7600.16385
    Fault Module Timestamp:    4a5be059
    Exception Code:    c0000005
    Exception Offset:    0000000000007656
    OS Version:    6.1.7600.2.0.0.768.3
    Locale ID:    1033
    Additional Information 1:    cfde
    Additional Information 2:    cfde40d2947ae30049954a76bd1df2fb
    Additional Information 3:    15bc
    Additional Information 4:    15bcac7c5df11c3174523e464068ba30
    malware is not an issue. scans bring up nothing.
    Thaurane
    That thread is not relevant here.  Different error codes.
    Your error code is called a memory exception.  Basically a driver is misbehaving. 
    To start I would update to Service pack 1 as in itself that might fix this.
    If you want to upload your event viewer logs we can take a look.  There are some more comprehensive things we can do but the EV logs are a good place to start
    Please provide us with your Event Viewer administrative logs by following these steps:
    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
    If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem.  The
    work around is to edit the registry.  If you are not comfortable doing this DONT.  If you are, backup the key before you do
    Press Win+"R" and input regedit
    Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
    Wanikiya and Dyami--Team Zigzag

  • BSOD when on Skype Video call

    So I just recently started to get frequent BSODs when on a video call. I believe it has to do with my Logitech webcam, because I can Audio call (No video at all) with no problem, but if I turn on the camera, a few minutes later, i just randomly get the BSOD.
    I do have this file from the last BSOD. I got it when in a game while video calling, but the error is the same, so I know it's not the games or anything. 
    =================================================================
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004BE561A
      BCP3: FFFFF880033C4658
      BCP4: FFFFF880033C3EC0
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\010714-31855-01.dmp
      C:\Users\Matt\AppData\Local\Temp\WER-86050-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
    ==================================================================
    The .dmp file is here: https://skydrive.live.com/redir?resid=3533AA13C3B40212!107&authkey=!AJH3kGYMbTnw1jM&ithint=file%2c.dmp
    I couldn't get it to open or anything, so I figured someone else could. I really need help here. I usually know my way around these issues but this one's got me stumped..
    Thanks for any help possible. Really appreciate it.

    Matthew
    This one crash was Related to
    stdriver64.sys stdriver.sys from NCH Software  I would remove it at least to test. 
    You also have other drivers needing updating because you have not installed SP-1.  You need to asap
    Service pack 1 Update.
    http://windows.microsoft.com/installwindows7sp1
    Learn how to install Windows 7 Service Pack 1 (SP1)
    http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1
    Additional Resources:
    http://windows.microsoft.com/en-US/windows7/uninstall-sp1
    http://windows.microsoft.com/troubleshootwindows7sp1
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\010714-31855-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* 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:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
    Machine Name:
    Kernel base = 0xfffff800`0360b000 PsLoadedModuleList = 0xfffff800`03847e70
    Debug session time: Tue Jan 7 17:10:45.288 2014 (UTC - 5:00)
    System Uptime: 0 days 0:31:08.334
    Loading Kernel Symbols
    *** WARNING: Unable to verify timestamp for stdriver64.sys
    *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
    BugCheck 1000007E, {ffffffffc0000005, fffff88004be561a, fffff880033c4658, fffff880033c3ec0}
    Probably caused by : stdriver64.sys ( stdriver64+261a )
    Wanikiya and Dyami--Team Zigzag

  • Could really use your help- BSOD with new Samsung ssd in a GX660r

    I recently put a new Samsung 830 series 128 gb ssd into my MSI GX660r. It'll work fine for about a day, then start crashing constantly (BSOD) whenever it's in normal mode. If I start it up in safe mode it seems to be working fine, I haven't had a BSOD in it yet, but in normal mode it's crashing. Any help? I'm hoping its just a driver issue or something, but I really have no idea what to do and since I'm in grad school it's really not a good time (since I have no time to take care of the problem myself) I'll paste in the most recent crash log that it gave me:
    Problem signature:
      Problem Event Name:   BlueScreen
      OS Version:   6.1.7601.2.1.0.768.3
      Locale ID:   1033
    Additional information about the problem:
      BCCode:   3b
      BCP1:   00000000C0000005
      BCP2:   FFFFF880010F8626
      BCP3:   FFFFF8800BBCAE10
      BCP4:   0000000000000000
      OS Version:   6_1_7601
      Service Pack:   1_0
      Product:   768_1
    Files that help describe the problem:
      C:\Windows\Minidump\102112-11325-02.dmp
      C:\Users\Joseph Trees\AppData\Local\Temp\WER-18439-0.sysdata.xml

    here's what all my dmp files say if it helps
    ==================================================
    Dump File         : 102112-11325-02.dmp
    Crash Time        : 10/21/2012 9:01:50 PM
    Bug Check String  : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code    : 0x0000003b
    Parameter 1       : 00000000`c0000005
    Parameter 2       : fffff880`010f8626
    Parameter 3       : fffff880`0bbcae10
    Parameter 4       : 00000000`00000000
    Caused By Driver  : Ntfs.sys
    Caused By Address : Ntfs.sys+99065
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7efc0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\102112-11325-02.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 277,296
    ==================================================
    ==================================================
    Dump File         : 102112-11263-01.dmp
    Crash Time        : 10/21/2012 8:50:25 PM
    Bug Check String  : NTFS_FILE_SYSTEM
    Bug Check Code    : 0x00000024
    Parameter 1       : 00000000`001904fb
    Parameter 2       : fffff880`09714e08
    Parameter 3       : fffff880`09714660
    Parameter 4       : fffff800`030a6d60
    Caused By Driver  : Ntfs.sys
    Caused By Address : Ntfs.sys+48d8
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7efc0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\102112-11263-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 277,288
    ==================================================
    ==================================================
    Dump File         : 102112-11325-01.dmp
    Crash Time        : 10/21/2012 8:41:41 PM
    Bug Check String  : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code    : 0x0000003b
    Parameter 1       : 00000000`c0000005
    Parameter 2       : fffff880`03cbcc1a
    Parameter 3       : fffff880`02a85be0
    Parameter 4       : 00000000`00000000
    Caused By Driver  : aswSP.SYS
    Caused By Address : aswSP.SYS+bc1a
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7efc0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\102112-11325-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 280,856
    ==================================================

  • BSOD - Server 2008 R2 - ntoskrnl.exe

    I've been having an issue lately with a BSOD happening multiple times during the day. I have DMP logs and used BlueScreenView to get some basic information (I know that this is as helpful as it is useless) which seems to show that ntoskrnl.exe is
    causing the crashes. There are 6 servers, 1 is used by IT and doesn't seem to have had this issue while the other 5 are part of a load balanced environment and have been having this issue in some cases 5 times a day. These are RD servers.
    The servers were all working perfectly fine until our company purchased and installed a piece of software called Screwdrivers/Simplify Printing. This software seems to be the cause of the crashes and I have contacted their support regarding this.
    But while I wait I figure it might be a good idea to ask if the DMP files actually could provide more information as to what specifically is causing the crashes.
    For those who don't know, Screwdrivers is a utility to help with printing (driverless printing from the RD server to the workstation using the Screwdrivers driver) and I'm wondering if there is a specific model of printer causing the crashes or
    a specific workstation side driver or if its just one or a few users that are causing the crashes. Obviously BlueScreenView isn't giving any good information but if the DMP file contains more information that may help I figure that it's worth looking into.
    The BSOD error is below:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version:      6.1.7601.2.1.0.18.10
      Locale ID:           1033
    Additional information about the problem:
      BCCode:             f4
      BCP1:  0000000000000003
      BCP2:  FFFFFA801CCD9060
      BCP3:  FFFFFA801CCD9340
      BCP4:  FFFFF80001D85270
      OS Version:      6_1_7601
      Service Pack:    1_0
      Product:             18_3
    I have uploaded the DMP and NFO files zipped to my onedrive but I can't post until my account gets verified but once I can post the link I will gladly or you
    could try to find my post with the same topic title.
    https://onedrive.live.com/embed?cid=CBD3F774506379E4&resid=CBD3F774506379E4%21148&authkey=AK0BPufjZy24HYQ
    I am currently running the verifier.exe tool as suggested to see if any more information can be obtained. It has been running for about 3 hours now so we'll see what results I get.
    I have posted this on answers microsoft com and ZigZag3143 has advised me that it might be good to post here and after looking at the DMP files ZigZag has found the following...
    "These were literally all critical process termination (0xF4) meaning something causes an OS process to terminate unexpectedly. 
    The running process at the time of the crash was Simplifiy notification but there is nothing definitive.  I would run driver verifier on
    one of the servers (non production) as verifier will crash it when the mis-behaving driver is loaded or makes a bad call
    One other thing of note was that vmdebug.sys Replay Debugging Driver from VMware, Inc. was also in the stack."
    The company we bought the software from is looking into this on their end but I figured the DMP files could potentially help get some more information. I'm hoping that maybe there's a way to find out if its a single printer model, a certain local
    workstation printer driver, a certain user, a certain PC, or something else. These are RDP server so there's upwards of 50+ users on each of the 5 servers at any given time and to have the servers just randomly restart is really frustrating for our users
    as this is arguably the most important system (next to payroll of course lol).
    Thanks,
    Ryan

    Hi Ryan,
    For Bug Check 0xF4, it indicates that a process or thread crucial to system operation has unexpectedly exited
    or been terminated. For more details, please refer to following article.
    Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
    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. Please refer to following article
    and check if help you to analyze Bug check 0xF4.
    Debugging a Bugcheck 0xF4
    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

Maybe you are looking for

  • Very, very disappointed in Nokia

    Unfortunately in April my Siemens S65 phone was stolen and the insurance company gave me a Nokia 6230i as a like for like replacement. I have to say in the 4 months since I've had the Nokia I've had a string of problems with it. These include the Ema

  • CM 7.1 LDAP integration not updating

    I have an LDAP integration that worked at 1 time to import all the users but now when I make a change to a user in AD, it never gets to CM.  The sync process seems to just sit there and the only option is to "Cancel Sync".  I can update the LDAP fiel

  • Shuts Down After One Minute?

    I can turn on the Mac and load it all the way to the desktop, but after a minute or so, a pop-up of "Logout, Cancel, Restart, Shutdown" will occur. Even though nothing is pressing against the keyboard, it will turn itself off after a minute. I know t

  • Old tbs exist after oatm

    Hi all, I have done OATM migartion successfully, no error. But getting some tablespace who contains the object, still pointing to the old tablespace. select distinct tablespace_name from dba_segments where tablespace_name not like 'APPS%' and tablesp

  • Droplet Error Message

    I have created a Photoshop Action and then created a Droplet from this action. I saved the droplet in the Export Actions Folder. In Lightroom 1.0 Export I specify the droplet and the Action starts. However, in Photoshop CS3 beta, when Photoshop opens