Bccode 1a windows 7 64 bit

  • *******************************************************************************

    *                                                                        
        *

    *                        Bugcheck Analysis                                    *

    *                                                                        
        *

    *******************************************************************************

    MEMORY_MANAGEMENT (1a)

        # Any other values for parameter 1 must be individually examined.

    Arguments:

    Arg1: 0000000000005001, The subtype of the bugcheck.

    Arg2: fffff70001080000

    Arg3: 0000000000005eaf

    Arg4: 0000000000005eaf

    Debugging Details:

    ——————

    BUGCHECK_STR:  0x1a_5001

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  CCC.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80002d04627 to fffff80002c91c40

    STACK_TEXT:  

    fffff880`0994a0e8 fffff800`02d04627 : 00000000`0000001a 00000000`00005001 fffff700`01080000 00000000`00005eaf : nt!KeBugCheckEx

    fffff880`0994a0f0 fffff800`02c9ef19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string’+0x3994b

    fffff880`0994a200 fffff800`02c8fd6e : 00000000`00000000 00000000`1f380000 fffffa80`03bccb01 00000000`1e085590 : nt!MmAccessFault+0x359

    fffff880`0994a360 00000000`775b1d84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e

    00000000`1e0854d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b1d84

    STACK_COMMAND:  kb

    FOLLOWUP_IP: 

    nt! ?? ::FNODOBFM::`string’+3994b

    fffff800`02d04627 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string’+3994b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

    FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b

    BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b

    Followup: MachineOwner

    ———

    ————————————————————————————-

    Please start by updating your ATI drivers and check results.

    If this does not help then:

    • Update all possible drivers you have
    • Uninstall all unused programs
    • Disable all security softwares that you have
    • Run msconfig and disable all startup items / services except Microsoft ones
    • Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support

    If this does not help then upload c:\windows\MEMORY.DMP file after zipping it. Once done, post a link here.

    You can also contact Microsoft CSS for assistance.


    This
    posting is provided «AS IS» with no warranties or guarantees , and confers no rights.
       

    Microsoft Student
    Partner 2010 / 2011
    Microsoft Certified
    Professional
    Microsoft Certified
    Systems Administrator: Security
    Microsoft Certified
    Systems Engineer: Security
    Microsoft Certified
    Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified
    Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified
    Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft
    Certified Technology Specialist: Windows 7, Configuring

    Microsoft
    Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations

    Microsoft Certified
    IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by

      Tuesday, February 7, 2012 6:31 AM

    • Marked as answer by
      Arthur Xie
      Tuesday, February 21, 2012 6:08 AM

  •      Синий экран  0x0000001A  указывает, что произошла серьезная ошибка управления памятью.

    Параметры MEMORY_MANAGEMENT:

    Параметр 1 Причина ошибки
    0x1 Разветвлённый клон счетчика ссылок поврежден (происходит на отладочных сборках Windows.)
    0x777 При вызове разблокировался адрес системного кэша, который в настоящий момент не заблокирован. (Этот адрес или никогда не отображался или разблокирован дважды.)
    0x778 Система использует последний адрес системного кэша, вместо того, чтобы сохранить его.

    0x780

    0x781

    PTE, отображающие параметры  системного кэша, были повреждены.
    0x1000 При вызове MmGetSystemAddressForMdl произошла попытка отобразить полностью кэшируемую физическую страницу как некэшируемую.
    0x1010 Ошибка возникает при разблокировке раздела системного кеша, которая в настоящий момент не заблокирована. (Этот раздел или никогда не блокировался или разблокирован дважды.)
    0x1234 Ошибка возникает при попытке блокировки не существующего раздела системного кеша.
    0x1235 Ошибка возникает при попытке защитить MDL с недопустимым значением.
    0x3451 PTE стека потока ядра, который был выгружен, поврежден.

    0x8888

    0x8889

    Структуры управления внутренней памяти повреждены.
    0x41283 Индекс системного рабочего набора, закодированный в PTE, поврежден.
    0x41284 PTE или список системного рабочего набора повреждены.
    0x41286 Ошибка возникает при попытке освободить недопустимый адрес пула.
    0x41785 Список системного рабочего набора поврежден.
    0x41287 Структуры управления внутренней памяти повреждены. Чтобы далее исследовать причину необходимо исследовать файл дампа памяти ядра.
    0x61940 PDE неожиданно лишен прав.
    0x03030303 Загрузчик поврежден. (Это значение применяется только к машинам Intel Itanium.)
    Other Произошла неизвестная ошибка управления памятью.

    Решение

    Windows XP

         Для устранения Stop 0x0000001A необходимо установить рекомендуемое обновление системы защиты 931784 или KB929338.

    Windows Server 2008 SP2 и Windows Server 2008 R2

         BSoD происходит, потому что у процессоров Intel Westmere появилась новая возможность кэширования Virtual Machine Control Structure (VMCS). Эта опция добавлена, чтобы обеспечить помощь виртуализации, для увеличения производительности гипервизора. Поскольку эта функция была представлена после выпуска Windows 2008 SP2 и после Windows 2008 R2, гипервизор не обрабатывает кеширование VMCS правильно. Вследствие чего  приводит повреждение памяти.

         Для решения данной ошибки обновите Вашу операционную систему.

    Windows 2000

         Для решения Stop 0x0000001A необходимо установить пакет обновлений Service Pack 3.

    Reader Interactions

    • #1

    I am using a desktop with below mentioned config.
    Processor : Intel® core ™ i3-3220 CPU @3.30GHZ
    RAM : 8 GB (2x4GB)
    HDD : 1TB
    Nvidia Geforce 210 — 512MB
    D-Link DWA-525 Wireless N150 Desktop Adaptor
    OS :Windows 7 Prof SP1 x64 bit

    Problem report :

    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: 1a
    BCP1: 0000000000003452
    BCP2: 000007FEFCDE2000
    BCP3: FFFFF700010930F8
    BCP4: D8E000017C9F1004
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\070114-29016-01.dmp
    C:\Users\VRTS\AppData\Local\Temp\WER-63632-0.sysdata.xml


    Pls help me to solve this issue.

    kemical

    • #2

    Hi,
    to best help you we really need to see the actual dump file which is produced when windows bsods. Make sure your system is set up to produce dump files by checking these settings:

    Go to Start and type in sysdm.cpl and press Enter
    Click on the Advanced tab
    Click on the Startup and Recovery Settings button
    Ensure that Automatically restart is unchecked
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
    found later.
    Click OK twice to exit the dialogs, then reboot for the changes to take effect

    If you already have some dump files ( found in the Minidump folder which is located in the main windows folder) or once you have a few (always better to have more than one as it helps us debuggers) read this thread then post the results:
    http://windowsforum.com/threads/how-to-ask-for-help-with-a-bsod-problem.38837/
    .

    • #3

    Hi,
    to best help you we really need to see the actual dump file which is produced when windows bsods. Make sure your system is set up to produce dump files by checking these settings:

    If you already have some dump files ( found in the Minidump folder which is located in the main windows folder) or once you have a few (always better to have more than one as it helps us debuggers) read this thread then post the results:
    http://windowsforum.com/threads/how-to-ask-for-help-with-a-bsod-problem.38837/
    .

    As u told, I run that SF diagnostic tool.Then I got a folder with this name (SF_01-07-2014).And I compressed it by 7-ZIP.when I upload it,an error is coming like that » There was a problem uploading your file».

    I have tried with winrar,winip and 7 Zip.I cant upload it.Sorry for my poor english…

    Pls suggest me what i have to do further…

    Last edited:

    kemical

    • #4

    Apologies about the forum upload service it’s in the process of being fixed but in the meantime try using this site to post your files on and then post the link:
    http://www.mediafire.com/

    kemical

    • #6

    Code:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41284, fffff8a00d5c5001, d351, fffff781c0000000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
    
    Followup: MachineOwner

    Hi,
    almost all of the dump files sent were like the above. A couple were Bugcheck 24 which could mean NTFS errors and another was a Bugcheck 3B which could be anything from bad RAM to corrupt data.
    You may have a RAM issue and you’ll have to perform some testing to see if this is so.

    AppleCharger.sys Thu Oct 25 01:51:02 2012: GIGABYTE On/Off Charge driver. May cause BSOD on Win7/8 systems — uninstall to test

    Dnetr28x.sys Tue Apr 19 04:31:37 2011: D-Link DWA-525 Wireless N 150 Desktop Adapter please update:
    http://www.dlink.com/uk/en/home-solutions/connect/adapters/dwa-525-wireless-n-150-pci-adapter

    gdrv.sys Fri Mar 13 03:22:29 2009: Gigabyte Easy Saver — mobo power utility driver please update:
    http://www.gigabyte.com/products/product-page.aspx?pid=4004#utility

    GVTDrv64.sys Tue Sep 05 08:10:02 2006: Gigabyte Easy Tune 6 driver (known BSOD issues w/Win7)-uninstall to test.

    nvlddmkm.sys Sat Jan 08 02:07:22 2011: Nvidia gpu driver. Please update:
    http://www.nvidia.com/download/driverResults.aspx/75991/en-us

    Please run the Intel driver update utility:
    https://downloadcenter.intel.com/default.aspx

    If you still bsod after making the above changes run a chkdsk:
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

    Run a system file scan. Find command prompt in the start menu, right click on it and run as admin. Type:
    sfc /scannow
    Press enter and await results.

    Download the latest version of Memtest86 here:
    http://www.memtest.org/
    You can use this app to test your RAM. You’ll need to burn to a disk or USB drive and then boot from it. This is so the RAM can be tested outside of the windows operating system. Try to run for at least 12hours unless errors appear straight away and it’s obvious there is something wrong with the RAM (the errors will show up in red).

    Please post any new dump files.

    • #7

    I found error report in memtest86 test (Error details are coming in RED color). Further what I have to do please suggest me

    kemical

    • #8

    You’ll need to replace your RAM. You could test each stick individually to see which or both have an issue but to be honest it’s probably better to just start again and buy a new pair of sticks as they are matched in the factory for compatibility.

    • #9

    Thanks for your best support

    kemical

    • #10

    Glad to help.. Post back if you need further help.. :)

  • Bcm43142a0 скачать драйвер windows 10 64 lenovo
  • Bccode 116 windows 7 как исправить
  • Bcm43142a0 sony vaio windows 10
  • Bcad для windows 10 скачать торрент
  • Bcm43142 bluetooth adapter драйвер для windows 10 64