locked
BSOD RRS feed

  • Question

  • Please help! I have tried suggestions online but to no avail, thanks in advance.

    Crash dump directory:
    C:\Windows\Minidump


    Crash
    dumps are enabled on your computer.


    On Wed 27/06/2012 20:45:59 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\062712-50265-01.dmp
    This
    was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
    Bugcheck code: 0xF7
    (0xFFFFFFFF8F4879CA, 0x1C640546, 0xFFFFFFFFE39BFAB9, 0x0)
    Error: DRIVER_OVERRAN_STACK_BUFFER
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a driver has overrun a
    stack-based buffer.
    This appears to be a typical software driver bug and is
    not likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


    On Wed 27/06/2012 17:26:00 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\062712-18171-01.dmp
    This
    was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
    Bugcheck code: 0xA (0x0,
    0x2, 0x1, 0xFFFFFFFF81E81D7B)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that Microsoft Windows or a
    kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This
    appears to be a typical software driver bug and is not likely to be caused by a
    hardware problem.
    The crash took place in the Windows kernel. Possibly this
    problem is caused by another driver which cannot be identified at this time.



    On Wed
    27/06/2012 17:22:15 GMT your computer crashed

    crash dump file:
    C:\Windows\Minidump\062712-22203-01.dmp
    This was probably caused by the
    following module: ntkrnlpa.exe (nt+0x8E3BF)
    Bugcheck code: 0x50
    (0xFFFFFFFF8AD90B48, 0x0, 0xFFFFFFFF82C5A985, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


    On Wed 27/06/2012 17:21:37 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\062712-30312-01.dmp
    This
    was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
    Bugcheck code: 0x1A
    (0x411, 0xFFFFFFFFC006E4F0, 0x6702886, 0xFFFFFFFFC002E4F1)
    Error: MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver which cannot be identified at this
    time.


    On Sun 24/06/2012 10:34:35 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\062412-19343-01.dmp
    This
    was probably caused by the following module: win32k.sys (win32k+0xC6CF1)
    Bugcheck code:
    0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D756CF1, 0xFFFFFFFF88D2FD08,
    0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32
    Driver
    Bug check description: This indicates that a kernel-mode program
    generated an exception which the error handler did not catch.
    This appears to
    be a typical software driver bug and is not likely to be caused by a hardware
    problem.
    The crash took place in a standard Microsoft module. Your system
    configuration may be incorrect. Possibly this problem is caused by another
    driver on your system which cannot be identified at this time.



    On Sun
    24/06/2012 10:29:04 GMT your computer crashed

    crash dump file:
    C:\Windows\Minidump\062412-40218-01.dmp
    This was probably caused by the
    following module: ntkrnlpa.exe (nt+0x4165B)
    Bugcheck code: 0xA
    (0x4C47F6C, 0x2, 0x1, 0xFFFFFFFF82ABAE24)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that Microsoft Windows or a
    kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This
    appears to be a typical software driver bug and is not likely to be caused by a
    hardware problem.
    The crash took place in the Windows kernel. Possibly this
    problem is caused by another driver which cannot be identified at this time.



    On Sun
    24/06/2012 10:26:58 GMT your computer crashed

    crash dump file:
    C:\Windows\Minidump\062412-33203-01.dmp
    This was probably caused by the
    following module: ntkrnlpa.exe (nt+0x4165B)
    Bugcheck code: 0xA
    (0xFFFFFFFFC0384DA0, 0x0, 0x0, 0xFFFFFFFF82AD46CE)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that Microsoft Windows or a
    kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This
    appears to be a typical software driver bug and is not likely to be caused by a
    hardware problem.
    The crash took place in the Windows kernel. Possibly this
    problem is caused by another driver which cannot be identified at this time.



    On Mon
    18/06/2012 11:24:20 GMT your computer crashed

    crash dump file:
    C:\Windows\Minidump\062212-24484-01.dmp
    This was probably caused by the
    following module: ntkrnlpa.exe (nt+0x8E3BF)
    Bugcheck code: 0x50
    (0xFFFFFFFFB741A714, 0x1, 0xFFFFFFFF82B76943, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


    On Sat 16/06/2012 19:09:46 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\061612-50125-01.dmp
    This
    was probably caused by the following module: spbbcdrv.sys (SPBBCDrv+0x3F5F)
    Bugcheck code: 0xC2
    (0x7, 0x109B, 0x9B88, 0xFFFFFFFF87A27A60)
    Error: BAD_POOL_CALLER
    file path: C:\Program Files\Common
    Files\Symantec Shared\SPBBC\SPBBCDrv.sys
    product: SPBBC
    company: Symantec Corporation
    description: SPBBC
    Driver
    Bug check description: This indicates that the current thread is
    making a bad pool request.
    This appears to be a typical software driver bug
    and is not likely to be caused by a hardware problem.
    A third party driver
    was identified as the probable root cause of this system error. It is suggested
    you look for an update for the following driver: spbbcdrv.sys (SPBBC Driver,
    Symantec Corporation).
    Google query: spbbcdrv.sys Symantec Corporation
    BAD_POOL_CALLER





    On Sat 16/06/2012 17:38:14 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\061612-29343-01.dmp
    This
    was probably caused by the following module: atikmdag.sys (atikmdag+0x43798)
    Bugcheck code:
    0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF91847798, 0xFFFFFFFF9677532C,
    0xFFFFFFFF96774F10)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon
    Family

    company: ATI
    Technologies Inc.

    description: ATI Radeon Kernel Mode
    Driver
    Bug check description: This indicates that a system thread generated
    an exception which the error handler did not catch.
    This appears to be a
    typical software driver bug and is not likely to be caused by a hardware
    problem.
    A third party driver was identified as the probable root cause of
    this system error. It is suggested you look for an update for the following
    driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).

    Google query: atikmdag.sys ATI Technologies Inc.
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    On Sun 10/06/2012 21:08:42 GMT
    your computer crashed

    crash dump file:
    C:\Windows\Minidump\061012-21656-01.dmp
    This was probably caused by the
    following module: symevent.sys (SYMEVENT+0x14449)
    Bugcheck code: 0x4E
    (0x99, 0x3328B, 0x2, 0x1)
    Error: PFN_LIST_CORRUPT
    file path:
    C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event
    Library
    Bug check description: This indicates that the page frame number
    (PFN) list is corrupted.
    This appears to be a typical software driver bug and
    is not likely to be caused by a hardware problem. This might be a case of memory
    corruption. More often memory corruption happens because of software errors in
    buggy drivers, not because of faulty RAM modules.
    A third party driver was
    identified as the probable root cause of this system error. It is suggested you
    look for an update for the following driver: symevent.sys (Symantec Event
    Library, Symantec Corporation).
    Google query: symevent.sys Symantec Corporation
    PFN_LIST_CORRUPT





    On Sun 10/06/2012 21:06:40 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\061012-44781-01.dmp
    This
    was probably caused by the following module: cng.sys (cng+0x615E)
    Bugcheck code: 0x1000008E
    (0xFFFFFFFFC0000005, 0xFFFFFFFF82A47D9F, 0xFFFFFFFF8A593374, 0x0)
    Error:
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\Windows\system32\drivers\cng.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel
    Cryptography, Next Generation
    Bug check description: This indicates that a
    kernel-mode program generated an exception which the error handler did not
    catch.
    This appears to be a typical software driver bug and is not likely to
    be caused by a hardware problem.
    The crash took place in a standard
    Microsoft module. Your system configuration may be incorrect. Possibly this
    problem is caused by another driver on your system which cannot be identified at
    this time.


    On Thu 31/03/2011 13:50:45 GMT your computer
    crashed

    crash dump file: C:\Windows\Minidump\033111-22750-01.dmp
    This
    was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
    Bugcheck code: 0x18 (0x0,
    0xFFFFFFFF8506C770, 0x2, 0xFFFFFFFF84D4D007)
    Error: REFERENCE_BY_POINTER
    file path:
    C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that the reference count of an
    object is illegal for the current state of the object.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem
    is caused by another driver which cannot be identified at this time.

    Wednesday, June 27, 2012 8:58 PM

Answers

  • Hi,


    According to BSOD error codes, you can refer to Bug Check Code Reference.


    To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Before we could get your Minidump files, you can check following:


    1. Update your BIOS, chipset and the drivers

    2. Scan the system to check for the virus

    3. Test the issue in Clean Boot and Safe Mode


    Furthermore, I suggest that you can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)


    Hope this helps.


    Vincent Wang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, July 9, 2012 3:54 AM
    Friday, June 29, 2012 9:08 AM

All replies

  • There are several different bugchecks reported in your system.
    I suggest you to verify that you have the latest drivers for each of the installed devices (the video driver caused a 0x1000007E Stop), to temporarily remove any Symantec product (the SYMEVENT driver caused a 0x0000004E Stop, the SPBBC driver caused a 0x000000C2 Stop) and to check the integrity of the system files by running the sfc /scannow command in a command prompt window, since there are several system files involved in some of the reported bugchecks.

    As soon as you see a blue screen again, post the informations that you can note and upload the produced DMP file from the \Windows\Minidump folder to your Windows Live SKyDrive, so we can analyze it.

    Bye.


    Luigi Bruno


    Thursday, June 28, 2012 9:44 PM
  • Hi,


    According to BSOD error codes, you can refer to Bug Check Code Reference.


    To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Before we could get your Minidump files, you can check following:


    1. Update your BIOS, chipset and the drivers

    2. Scan the system to check for the virus

    3. Test the issue in Clean Boot and Safe Mode


    Furthermore, I suggest that you can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)


    Hope this helps.


    Vincent Wang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, July 9, 2012 3:54 AM
    Friday, June 29, 2012 9:08 AM
  • Please post a copy of your dumpfile as a shared file to your Sky Drive with a link here.
    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    For advice on how to configure your system to create dump files please read:
    http://support.microsoft.com/kb/254649

    The dumpfile will be created at c:\windows\minidump. You may need to change your settings in Windows to be able to see the file. To show hidden files type Folder Options in the search box above the Start button and select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and "Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.

    What is your computer make and model? If not a branded computer what is your motherboard make and model?

    Type System information in the Search Box above the start Button and press the ENTER key. What is your BIOS version and date?

    Is your Windows 7 32 bit or 64 bit?


    Hope this helps, Gerry

    Friday, June 29, 2012 10:21 AM