Blue Screen STOP:0x000000BE id:1033


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    Blue Screen STOP:0x000000BE id:1033


    Hi. First of all sorry about my english! I have the following error (can happen at any time.. maybe 5 minutes or 2 hours after windows started up..)

    I only installed Windows 7. NO drivers. NO software.

    Computer specs:

    Windows 7 Ultimate
    Intel Celeron G1840 2.80GHZ
    2.00 GB
    64-Bit Operating System

    My Log Attachment.

    Someone can help me please? Really don't know what to do..

    Already Thanks.
      My Computer


  2. Posts : 2,528
    Windows 10 Pro x64
       #2

    First, upgrade to Windows 7 SP1, then patch fully. If the problems occur, post the memory dump file (at least kernel if possible, not a mini dump) to a file sharing site and we'll review then. However, you're running Windows 7 without SP1 and patches. It's not supported, and there are lots of things fixed in SP1 and further patches that aren't downlevel on RTM. Get up to date before troubleshooting.
      My Computer


  3. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #3

    cluberti said:
    First, upgrade to Windows 7 SP1, then patch fully. If the problems occur, post the memory dump file (at least kernel if possible, not a mini dump) to a file sharing site and we'll review then. However, you're running Windows 7 without SP1 and patches. It's not supported, and there are lots of things fixed in SP1 and further patches that aren't downlevel on RTM. Get up to date before troubleshooting.
    Thanks! I updated Windows and now I have this Blue Screen:

    IMG: https://i.imgur.com/DiMDLI2.jpg

    dump file.. 040915-17456-01

    debug log attachment.

    Best Regards.
      My Computer


  4. Posts : 2,528
    Windows 10 Pro x64
       #4

    According to your dump, you most certainly did not install SP1, and binaries are still all at RTM levels:

    Code:
    0: kd> vertarget
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
    Debug session time: Thu Apr  9 10:05:28.063 2015 (UTC - 7:00)
    System Uptime: 0 days 0:44:25.343
    
    0: kd> lmvm hal
    start             end                 module name
    fffff800`02803000 fffff800`0284c000   hal        (deferred)             
        Mapped memory image file: C:\ProgramData\dbg\sym\hal.dll\4A5BDF0849000\hal.dll
        Image path: hal.dll
        Image name: hal.dll
        Timestamp:        Mon Jul 13 18:27:36 2009 (4A5BDF08)
        CheckSum:         0004BD36
        ImageSize:        00049000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     hal.dll
        OriginalFilename: hal.dll
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  Hardware Abstraction Layer DLL
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> lmvm ntfs
    start             end                 module name
    fffff880`0120e000 fffff880`013b1000   Ntfs       (deferred)             
        Mapped memory image file: C:\ProgramData\dbg\sym\Ntfs.sys\4A5BC14F1a3000\Ntfs.sys
        Image path: \SystemRoot\System32\Drivers\Ntfs.sys
        Image name: Ntfs.sys
        Timestamp:        Mon Jul 13 16:20:47 2009 (4A5BC14F)
        CheckSum:         00195F88
        ImageSize:        001A3000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntfs.sys
        OriginalFilename: ntfs.sys
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  NT File System Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> lmvm nt
    start             end                 module name
    fffff800`0284c000 fffff800`02e28000   nt         (pdb symbols)          C:\ProgramData\dbg\sym\ntkrnlmp.pdb\DE7B3DD8AC5343B3B4874BAB3F4599DD2\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\4D9FDD345dc000\ntoskrnl.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Fri Apr 08 21:14:44 2011 (4D9FDD34)
        CheckSum:         00547734
        ImageSize:        005DC000
        File version:     6.1.7600.16792
        Product version:  6.1.7600.16792
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7600.16792
        FileVersion:      6.1.7600.16792 (win7_gdr.110408-1633)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> !chkimg !nt
    3563 errors : !nt (fffff80002b28000-fffff80002b28fff)
    I asked that you install SP1, and then fully patch via Windows or Microsoft update. According to this dump file, you most certainly have failed to do so, and corruption in the kernel binary is still causing issues. Until you get SP1 and subsequent patches on here, it will potentially continue to fail. Since there are so many bugs fixed with SP1 and subsequent patches, I don't think it's wise to troubleshoot anything without these patches. Get SP1 on that system, and then patch please. After that, if you're still seeing issues, you probably want to test your hardware, specifically memory (RAM) and disk, for potential issues.
      My Computer


  5. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #5

    cluberti said:
    According to your dump, you most certainly did not install SP1, and binaries are still all at RTM levels:

    Code:
    0: kd> vertarget
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
    Debug session time: Thu Apr  9 10:05:28.063 2015 (UTC - 7:00)
    System Uptime: 0 days 0:44:25.343
    
    0: kd> lmvm hal
    start             end                 module name
    fffff800`02803000 fffff800`0284c000   hal        (deferred)             
        Mapped memory image file: C:\ProgramData\dbg\sym\hal.dll\4A5BDF0849000\hal.dll
        Image path: hal.dll
        Image name: hal.dll
        Timestamp:        Mon Jul 13 18:27:36 2009 (4A5BDF08)
        CheckSum:         0004BD36
        ImageSize:        00049000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     hal.dll
        OriginalFilename: hal.dll
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  Hardware Abstraction Layer DLL
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> lmvm ntfs
    start             end                 module name
    fffff880`0120e000 fffff880`013b1000   Ntfs       (deferred)             
        Mapped memory image file: C:\ProgramData\dbg\sym\Ntfs.sys\4A5BC14F1a3000\Ntfs.sys
        Image path: \SystemRoot\System32\Drivers\Ntfs.sys
        Image name: Ntfs.sys
        Timestamp:        Mon Jul 13 16:20:47 2009 (4A5BC14F)
        CheckSum:         00195F88
        ImageSize:        001A3000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntfs.sys
        OriginalFilename: ntfs.sys
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  NT File System Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> lmvm nt
    start             end                 module name
    fffff800`0284c000 fffff800`02e28000   nt         (pdb symbols)          C:\ProgramData\dbg\sym\ntkrnlmp.pdb\DE7B3DD8AC5343B3B4874BAB3F4599DD2\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\4D9FDD345dc000\ntoskrnl.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Fri Apr 08 21:14:44 2011 (4D9FDD34)
        CheckSum:         00547734
        ImageSize:        005DC000
        File version:     6.1.7600.16792
        Product version:  6.1.7600.16792
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7600.16792
        FileVersion:      6.1.7600.16792 (win7_gdr.110408-1633)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    0: kd> !chkimg !nt
    3563 errors : !nt (fffff80002b28000-fffff80002b28fff)
    I asked that you install SP1, and then fully patch via Windows or Microsoft update. According to this dump file, you most certainly have failed to do so, and corruption in the kernel binary is still causing issues. Until you get SP1 and subsequent patches on here, it will potentially continue to fail. Since there are so many bugs fixed with SP1 and subsequent patches, I don't think it's wise to troubleshoot anything without these patches. Get SP1 on that system, and then patch please. After that, if you're still seeing issues, you probably want to test your hardware, specifically memory (RAM) and disk, for potential issues.
    Hi! Thanks for the support.

    I'm trying to install the sp1 update but I always have the same error.. "Error found Code: 800B0100" at Windows Update.. Can you help me please?

    Thanks!
      My Computer


  6. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #6

    Hi! I install SP1.. Now this is my log..

    Already Thanks.. :)
      My Computer


  7. Posts : 2,528
    Windows 10 Pro x64
       #7

    Well, you're still not fully patched, but at least the call stack is interesting and you're at the SP1 release of the kernel (I'd still recommend patching fully via MU at this point). The call stack indicates a hard fault to bring data back in from the modified list, but the memory contents referenced couldn't be found. A hard fault (which is already a page fault) that is getting data from a backing medium (either the paging file or pulling in a binary from disk) that causes a page fault will cause a machine to bugcheck, as it did in this case. Minidumps won't help us here, you'll have to gather a kernel memory dump. And, I'm still gonna request that you actually fully patch your system.
      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 13:36.
Find Us