BSOD crash


  1. Posts : 3
    OS Version: 6_1_7600 windows 7 64bit
       #1

    BSOD crash


    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? 64bit
    - the original installed OS on the system?OS Version: 6_1_7600
    - an OEM or full retail version? full retail

    - What is the age of system (hardware)? 2 weeks
    - What is the age of OS installation (have you re-installed the OS?) 2 weeks

    this is what windows showed when it restarted

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000000403
    BCP2: FFFFF68000044118
    BCP3: CFF000004FD18825
    BCP4: FFFFF6800003B0D8
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\100110-19422-01.dmp
    C:\Users\Vince\AppData\Local\Temp\WER-26005-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt



    Thx for the help!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    multhag said:
    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? 64bit
    - the original installed OS on the system?OS Version: 6_1_7600
    - an OEM or full retail version? full retail

    - What is the age of system (hardware)? 2 weeks
    - What is the age of OS installation (have you re-installed the OS?) 2 weeks

    this is what windows showed when it restarted

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000000403
    BCP2: FFFFF68000044118
    BCP3: CFF000004FD18825
    BCP4: FFFFF6800003B0D8
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\100110-19422-01.dmp
    C:\Users\Vince\AppData\Local\Temp\WER-26005-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt



    Thx for the help!
    These were all caused by memory management/hardware. Your first step is to test your ram. second is to update the below drivers.

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

    Ken J




    DMP
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\100110-22854-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\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
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`0303de50
    Debug session time: Fri Oct  1 16:17:40.948 2010 (GMT-4)
    System Uptime: 0 days 0:05:15.743
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {8887, fffffa80006ed8d0, fffffa80006e18a0, 205}
    
    Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000008887, The subtype of the bugcheck.
    Arg2: fffffa80006ed8d0
    Arg3: fffffa80006e18a0
    Arg4: 0000000000000205
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_8887
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff880`0310ee68 fffff800`02e91914 : 00000000`0000001a 00000000`00008887 fffffa80`006ed8d0 fffffa80`006e18a0 : nt!KeBugCheckEx
    fffff880`0310ee70 fffff800`02ea2587 : 00000000`0000441b 00000000`00000000 00000000`0000441b fffff8a0`08935ea0 : nt!MiUnlinkPageFromLockedList+0x2e4
    fffff880`0310ef00 fffff800`02e96dc9 : 00000000`00000000 00000000`24f2f8c2 fffff880`00000001 fffff800`02ffce00 : nt!MiResolveTransitionFault+0x167
    fffff880`0310ef90 fffff800`02e8c5be : 00000000`00000000 fffff980`0cf14000 fffff6fc`c00678a0 fffff800`02ffce00 : nt!MiResolveProtoPteFault+0x419
    fffff880`0310f030 fffff800`02e8acf1 : fffff8a0`08491d00 fffffa80`03fd6c90 00000000`00000bc0 00000000`00000000 : nt!MiDispatchFault+0x1de
    fffff880`0310f140 fffff800`02e6e82e : 00000000`00000000 00000000`0000000e 00000000`00000000 fffffa80`039bdc20 : nt!MmAccessFault+0x8f1
    fffff880`0310f2a0 fffff800`03176981 : 00000000`00bc0000 00000000`00bd0000 fffff880`0310f4f8 fffff880`0310f4f0 : nt!KiPageFault+0x16e
    fffff880`0310f430 fffff880`010e97cb : fffffa80`00030000 fffffa80`039bdc20 00000000`00000000 fffffa80`0000000e : nt!CcMapData+0x111
    fffff880`0310f4f0 fffff880`0105ea34 : 00000000`00010000 fffffa80`00000000 00000000`00bd0000 fffffa80`06d7e5e8 : Ntfs!NtfsMapStream+0x5b
    fffff880`0310f530 fffff880`0106273c : fffffa80`042cd1b0 fffff8a0`0888aa20 00000000`00000000 fffff800`02e4ff02 : Ntfs!NtfsLockFileRange+0xa4
    fffff880`0310f5c0 fffff880`01068a12 : fffffa80`042cd1b0 fffffa80`0468a8b0 fffffa80`049b3180 fffff8a0`0888aa20 : Ntfs!NtfsNonCachedIo+0x91a
    fffff880`0310f790 fffff880`0106d413 : fffffa80`042cd1b0 fffffa80`0468a8b0 fffff880`0310f900 fffff880`0310f901 : Ntfs!NtfsCommonWrite+0x872
    fffff880`0310f950 fffff880`00da323f : fffffa80`0468ac08 fffffa80`0468a8b0 fffffa80`03d74c30 00000000`00000000 : Ntfs!NtfsFsdWrite+0x1c3
    fffff880`0310fa10 fffff880`00da16df : fffffa80`05246040 fffffa80`04703d80 fffffa80`05246000 fffffa80`0468a8b0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0310faa0 fffff800`02e5a57b : fffffa80`0468a8b0 fffffa80`05246040 fffffa80`04703d80 fffffa80`03fe06e0 : fltmgr!FltpDispatch+0xcf
    fffff880`0310fb00 fffff800`02ea81e8 : 00000000`00bd3000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!IoAsynchronousPageWrite+0x20b
    fffff880`0310fb50 fffff800`02ea7a6c : 00000000`00000000 fffffa80`03fe06d0 fffffa80`00000000 fffff8a0`08935e98 : nt! ?? ::FNODOBFM::`string'+0x4cfdb
    fffff880`0310fc50 fffff800`03114c06 : fffffa80`039f1040 00000000`00000080 fffffa80`03973890 a803ed73`83b815eb : nt!MiMappedPageWriter+0x198
    fffff880`0310fd40 fffff800`02e4ec26 : fffff800`02feae80 fffffa80`039f1040 fffff800`02ff8c40 06800007`04120081 : nt!PspSystemThreadStartup+0x5a
    fffff880`0310fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware_ram
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED
    
    BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED
    
    Followup: MachineOwner
    ---------


    drivers to update
    Code:
    Alpham264.sys        fffff880`059d4000    fffff880`059d9500    0x00005500    0x45ffae87    3/20/2007 05:51:03                        
    Alpham164.sys        fffff880`059c7000    fffff880`059d3f00    0x0000cf00    0x46a45f4f    7/23/2007 03:57:03
      My Computer


  3. Posts : 3
    OS Version: 6_1_7600 windows 7 64bit
    Thread Starter
       #3

    thx alot! it fixed my problem! (for some reason, my secon ram card was bugging up my computer...
      My Computer


  4. Posts : 9
    Windows 7 Ultimate x64
       #4

    Hi Zig Zag,

    I was wondering if you could help me. I'm having a similar problem to multhag. I receive regular BSOD's - when i look in the minidump folder i have 23 dump files.

    The latest error i got was:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 3081

    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000000403
    BCP2: FFFFF6800000FE80
    BCP3: D93000010D02B867
    BCP4: FFFFF6800000FE80
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\101410-16021-01.dmp
    C:\Users\Tomi Hendrix\AppData\Local\Temp\WER-40887-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    I downloaded and ran mem test overnight last night. It completed 11 passes and found no errors. I haven't installed the drivers you recommended above as i was not sure if they were specific to multhag's errors.

    Could you please help me with what my next step should be?

    Thanking you very much in advance!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:01.
Find Us