Windows 8 and 8.1 Forums

BSOD using Word Bugcheck code: 0x7F

  1. #1

    Posts : 2
    Windows 8.1

    BSOD using Word Bugcheck code: 0x7F

    Hello All,

    I'm a on self-built desktop PC and have been suffering occasional BSODs
    for a reason I can't figure out.

    PC specs: Intel Core i5-4460 3.20 GHz
    8 GB RAM
    OS: Win 8.1 (32-bit), latest OS updates

    I tried Driver Reviver with no success.

    WhoCrashed gives me this:

    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1C)
    Bugcheck code: 0x7F (0x8, 0xFFFFFFFF8130B000, 0x0, 0x0)

    Per the BSOD Posting Instructions, the result
    from the DM Log collector Tool is attached
    [Thanks axe0 for the info, the correct file should
    be uploaded now]

    I'd appreciate any help anyone can provide since I
    can't for the life of me figure out why this BSOD is


    Attached Files
    Last edited by socratesabroad; 01 Jul 2015 at 11:40.

      My System SpecsSystem Spec

  2. #2

    Posts : 2,067
    Windows 10 Home/ Windows 10 TP/ Windows 8.1 Pro/ Windows 7 Pro

    Hi socratesabroad,

    Welcome to the 8forums.
    I have analysed a few crashes.
    There are a few causes of the crashes.

    One crash is caused by the program Silicon Image, please uninstall this program.
    Norton has also been flagged with Silicon, but I'm not sure if Norton could be a cause too.
    Please use uninstall tool | Norton to temporarily remove Norton.

    The Intel Rapid Storage Technology driver has also been flagged.
    Please update this driver via the download center of Intel.

    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    kb will then show the corrected stack.
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 82e38940
    Arg3: 00000000
    Arg4: 00000000
    Debugging Details:
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  TiWorker.exe
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    LAST_CONTROL_TRANSFER:  from 86e2f75c to 86e2a744
    c686102c 86e2f75c 858b0548 0eb45000 00000000 Ntfs!NtfsPrepareSimpleBuffers+0xb
    c686106c 86e2b12c 858b0548 0eb45000 00000000 Ntfs!NtfsPrepareBuffers+0x71
    c6861250 86e2e804 858b0548 0eb45000 00000000 Ntfs!NtfsNonCachedIo+0x395
    c6861368 86e2fb87 0108070a 00000000 00000001 Ntfs!NtfsCommonRead+0x62f
    c68614e0 814320f9 8d497018 c590b558 c590b79c Ntfs!NtfsFsdRead+0x1d4
    c68614f8 86d30bcc c590b558 8e66d020 c590b503 nt!IofCallDriver+0x3b
    c6861534 86d308f1 00000000 8e045b60 8e66d020 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x266
    c6861560 814320f9 8e66d020 c590b558 8e045b60 fltmgr!FltpDispatch+0xb1
    c6861578 8231f325 8231fa8e 8e045b60 c590b558 nt!IofCallDriver+0x3b
    WARNING: Stack unwind information not available. Following frames may be wrong.
    c68615b0 814320f9 8e045b60 8e66d020 c590b558 SiWinAcc+0x325
    c68615c8 81432019 8e82f0b2 a1d94538 a1d94568 nt!IofCallDriver+0x3b
    c68615e4 814327f4 c590b79c 00000043 a1d94570 nt!IoPageRead+0x15f
    c6861614 81432a9f ced68f88 f7f5bbbb 0001b5c7 nt!MiIssueHardFaultIO+0x84
    c6861694 8148363f a1d94538 00000000 00000000 nt!MiIssueHardFault+0x12f
    c6861710 8145c31c 00000000 c3bc5000 00000000 nt!MmAccessFault+0x34f
    c6861820 8145b606 00000000 c686183e 00000000 nt!MmCheckCachedPageStates+0xc5c
    c6861850 81696bc6 00000001 c3bc5000 05ec531b nt!CcMapAndRead+0xd6
    c6861888 86e98d74 8e82f0b0 c68618c0 00000400 nt!CcMapData+0x48
    c68618b8 86e98be9 0eb45c00 00000000 00000400 Ntfs!NtfsMapStream+0x59
    c6861964 86e98a2b 9819b848 9819b848 00000001 Ntfs!NtfsReadMftRecord+0xd4
    c68619d0 86e984b2 9819b840 9819b848 00000000 Ntfs!NtfsReadFileRecord+0x66
    c6861a18 86e2c9c0 9819b848 00000080 9819b9e0 Ntfs!NtfsLookupInFileRecord+0x45
    c6861b44 86e2f97e 000066e4 00000000 c6861c38 Ntfs!NtfsLookupRealAllocation+0x39b
    c6861bd0 86e2a8bc 000066e4 00000000 c6861c38 Ntfs!NtfsLookupAllocation+0x3a
    c6861c44 86e2f75c 9819b938 066e4000 00000000 Ntfs!NtfsPrepareSimpleBuffers+0x183
    c6861c80 86e2b12c 9819b938 066e4000 00000000 Ntfs!NtfsPrepareBuffers+0x71
    c6861dc8 86e2e804 9819b938 066e4000 00000000 Ntfs!NtfsNonCachedIo+0x395
    c6861ee0 86e2fb87 8c9a3cee 80ce61c0 8d497018 Ntfs!NtfsCommonRead+0x62f
    c6861f50 814320f9 8d497018 80ce61c0 80ce6404 Ntfs!NtfsFsdRead+0x1d4
    c6861f68 86d30bcc 80ce61c0 8e66d020 80ce6103 nt!IofCallDriver+0x3b
    c6861fa4 86d308f1 00000000 8e045b60 8e66d020 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x266
    c6861fd0 814320f9 8e66d020 80ce61c0 8e045b60 fltmgr!FltpDispatch+0xb1
    c6861fe8 8231f325 8231fa8e 8e045b60 80ce61c0 nt!IofCallDriver+0x3b
    c6862020 814320f9 8e045b60 8e66d020 80ce61c0 SiWinAcc+0x325
    c6862038 81432019 8e85a5d9 8e85a558 b4b91a7c nt!IofCallDriver+0x3b
    c6862054 81681e05 80ce6404 00000403 8e85a590 nt!IoPageRead+0x15f
    c6862088 816ee9d9 00011000 00011000 066e0000 nt!MiPfExecuteReadList+0x79
    c68620ac 8145b50c 00011000 00000005 c68620d4 nt!MmPrefetchForCacheManager+0x93
    c68620ec 81696ac0 00010000 00000001 c686216c nt!CcFetchDataForRead+0xac
    c6862134 8145b24c 00000001 bc70e000 c686216c nt!CcMapAndCopyFromCache+0x7c
    c6862170 86e90eea 9cc60100 9cc6b7a0 00010000 nt!CcCopyReadEx+0xdc
    c68622ec 86d33a43 98efb790 9cc6b7a0 00010000 Ntfs!NtfsCopyReadA+0x228
    c6862320 86d3262b 9cc6b798 98efb790 8e66d020 fltmgr!FltpPerformFastIoCall+0x86
    c6862360 86d4e4ee 98efb790 c686240c 00000000 fltmgr!FltpPassThroughFastIo+0x14b
    c686239c 8231f907 98efb790 c6862414 00010000 fltmgr!FltpFastIoRead+0x13e
    c68623d4 81687c83 98efb790 c6862414 00010000 SiWinAcc+0x907
    c6862470 815176c7 8e045b60 00000000 00000000 nt!NtReadFile+0x1d3
    c6862470 81504e39 8e045b60 00000000 00000000 nt!KiSystemServicePostCall
    c686250c 92a377bd 80002524 00000000 00000000 nt!ZwReadFile+0x11
    c6862550 92a378a9 bc70e000 066e0231 00010000 NAVEX15+0x17bd
    c6862578 92a3850d 066e8231 0000000d d965ec88 NAVEX15+0x18a9
    c686259c 92a39e22 00021000 c68625d0 921f3780 NAVEX15+0x250d
    c6862608 92a3a089 c6862788 00000010 921f3780 NAVEX15+0x3e22
    c6862704 92a39fde c6862824 bc6ce108 bc6ce608 NAVEX15+0x4089
    c686274c 92a3a57b c6862824 bc6ce108 bc6ce608 NAVEX15+0x3fde
    c68627f0 92a3a6e0 c6862824 bc6ce108 bc6ce608 NAVEX15+0x457b
    c6862840 92a3bb9e e16aee28 bc6ce008 bc6ce608 NAVEX15+0x46e0
    c68628f8 92a3f660 00000000 92bbaad8 bc6ce608 NAVEX15+0x5b9e
    c6862994 92a400a2 bc6ce608 00000003 daac74e0 NAVEX15+0x9660
    c68629f8 92a401e9 d3b5c9f8 e16aee28 bc6ce008 NAVEX15+0xa0a2
    c6862a28 828d4fe1 d3b5c9f8 e16aee28 bc6ce008 NAVEX15+0xa1e9
    c6862a6c 828d6f88 daac74ac daac74a0 daac74a0 SRTSP+0x4ffe1
    c6862a88 82914596 c7785190 daac74ac c6862aa4 SRTSP+0x51f88
    c6862aa8 82915e91 814971e6 daac74a4 daac74a0 SRTSP+0x8f596
    c6862af8 82916556 e16aee28 daac74a0 1f0948dd SRTSP+0x90e91
    c6862b18 828a9f91 c6864000 1f0948dd 8144d810 SRTSP+0x91556
    c6862b4c 828c6827 934a69e0 934a6a5c 934a6b00 SRTSP+0x24f91
    c6862b60 86d2fc84 934a6a5c e16aee28 00000000 SRTSP+0x41827
    c6862bd0 86d31c39 e76445b0 e76447d0 934a69e0 fltmgr!FltpPerformPostCallbacks+0x256
    c6862bf0 86d30c41 934a69e0 00000000 d1fdc030 fltmgr!FltpPassThroughCompletionWorker+0x66
    c6862c34 86d4a2d0 00000000 e76445b0 d1fdc030 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2db
    c6862c8c 814320f9 d1fdc030 e76445b0 80c321b8 fltmgr!FltpCreate+0x2cb
    c6862ca4 816a485b 05ec662b e7746e84 b818b520 nt!IofCallDriver+0x3b
    c6862db8 8172e76f b818b520 85905ea0 e7746d20 nt!IopParseDevice+0x51b
    c6862e54 816a659e 00000240 85905ea0 81c02900 nt!ObpLookupObjectName+0x5bf
    8231f325 ??              ???
    SYMBOL_NAME:  SiWinAcc+325
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  SiWinAcc.sys
    FAILURE_BUCKET_ID:  0x7f_8_SiWinAcc+325
    BUCKET_ID:  0x7f_8_SiWinAcc+325
    FAILURE_ID_HASH_STRING:  km:0x7f_8_siwinacc+325
    FAILURE_ID_HASH:  {9cc27b5f-f645-a8e1-f3e9-f064f5b5e09f}

    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    A driver has failed to complete a power IRP within a specific time.
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 83933b48, Physical Device Object of the stack
    Arg3: 80039a04, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: 8ad45970, The blocked IRP
    Debugging Details:
    DRIVER_OBJECT: 8ad2adf8
    IMAGE_NAME:  iaStorA.sys
    MODULE_NAME: iaStorA
    FAULTING_MODULE: 86a3d000 iaStorA
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    800399dc 8239fb35 0000009f 00000003 83933b48 nt!KeBugCheckEx
    80039a14 8239fa81 00000000 823fca90 00000002 nt!PopIrpWatchdogBugcheck+0xae
    80039a28 82242616 8ad45e90 8ad45e48 b03dbc75 nt!PopIrpWatchdog+0x28
    80039ae0 82242236 80039b28 00000000 dca35040 nt!KiExecuteAllDpcs+0x216
    80039c04 82314e30 00000000 49100fc1 380f6610 nt!KiRetireDpcList+0xf6
    80039c08 00000000 49100fc1 380f6610 c183c1dc nt!KiIdleLoop+0x38
    FOLLOWUP_NAME:  MachineOwner
    BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_iaStorA.sys
    FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_iastora.sys
    FAILURE_ID_HASH:  {6eb4f7a0-d522-00fa-b929-42434edf48d1}
      My System SpecsSystem Spec

BSOD using Word Bugcheck code: 0x7F

Similar Threads
Thread Forum
Numerous BSOD on new laptop, 0xa, 0x1e, 0x7f
As the title suggests, this is a new laptop (around 3 weeks old, Acer VN7-571G-70G9), and in the past couple of days I have experienced multiple BSOD. They *seem* to happen mainly while browsing the web, but not always. In an attempt to fix it, I ran the W8.1 refresh tool, in case something I had...
BSOD Crashes and Debugging
Hi Guys, This is my first entry to this forum upon which I stumbled by pure incident. My PC, purely used as Audio Workstation worked very fine and suddenly started to BSOD when getting into power save mode, e.g. when I was away for some minutes. The installation was a fresh Win 8.1...
BSOD Crashes and Debugging
New built PC freezes and reboots, bugcheck code 0x124
I recently built a new computer and have been having reboot problems. I think they are GPU related. I am looking for possible solutions before I contact the manufacturer and get a replacement. CPU: AMD FX-6300 Phenom II Motherboard: Asus M5A78L-M/USB3 GPU: Radeon R9 290 4GB HDD: Seagate 7200...
Graphic Cards
Random BSOD's BugCheck 124 - HAL.DLL
Hi There! I have a i7 4770K with an Asus z87-Pro Motherboard, 3 x SSD in RAID 0 and 16GB Memory. GTX970 Video Card. I am having random BSOD's which have been persisting over quite some time. I run 8.1 Pro x64 and the problems have persisted through an OS reload. it usually happens when I...
BSOD Crashes and Debugging
Famous Atikmdag.sys BSOD. Bugcheck code: 0x50
I've had this BSOD before, but then got the computer magically back to working order. I also did a thread on that one and have tried to use the fix that I provided for other people on that forum. The BSOD I have now is 100% identical to the last one I had (the one I wrote about at the other forum)....
BSOD Crashes and Debugging
Vulnerability in Microsoft Word Could Allow Remote Code Ex
Source: Microsoft Releases Security Advisory 2953095 - MSRC - Site Home - TechNet Blogs See also: Microsoft Security Advisory (2953095): Vulnerability in Microsoft Word Could Allow Remote Code Execution
Windows 8 News

Eight Forums Android App Eight Forums IOS App Follow us on Facebook