Bue Screen Error ox7A

  1. #1
    cricky is offline Newbie

    Angry Bue Screen Error ox7A

    Ok i need Help with a Blue Screen Error 0x0000007A, at the moment it is rerly annoying me happens only when i am playing World of warcraft i am running Windows Vista Home Premium. i am Using Packard Bell PC with Nvidia Graphics Card it is the PC Model IMEDIA 2326 AIO
    Here is this if it is anyhelp

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 7a
    BCP1: C0604000
    BCP2: C000000E
    BCP3: 2594C880
    BCP4: C0800000
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\Mini062109-02.dmp
    C:\Users\cricky\AppData\Local\Temp\WER-43929-0.sysdata.xml
    C:\Users\cricky\AppData\Local\Temp\WERE59D.tmp.ver sion.txt

    the Error is a kernal_data_inpage_error i have tried Numerous of Different Things to try and Solve it I have been on Packard Bell's website they said use Smart Restore and i did do which reset all my drivers to when they were all put in the computer and it reset all files as well. i have ran Memory Diagonosic Tool it said no errors Found ran the Error checking tool same there plz could you tey and help me


  2. #2
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    1) Download and install the

    Debugging Tools from Microsoft

    All you need do is download and install this. Make no attempt to start or run it.

    2) Download, install and run Who Crashed.

    Post back your results.

  3. #3
    cricky is offline Newbie
    ok i will post back my results just gonna start downloading now

  4. #4
    cricky is offline Newbie
    i will post my results in the morning

  5. #5
    cricky is offline Newbie
    it says there isnt any this is what it said:
    Crash dumps are enabled and no crash dumps have been found on your computer. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware or power failure. Then it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.

  6. #6
    cricky is offline Newbie
    ok Help i just got an other Blue Screen it was 0x00000077

  7. #7
    cricky is offline Newbie
    when i go to Analyze on Whos Crashed it says Access is Denied

  8. #8
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    When you run Who Crashed right click it and Run as Administrator.

  9. #9
    cricky is offline Newbie
    On Wed 24/06/2009 12:03:38 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC04B61C0, 0xC000000E, 0x61FFA8C0, 0x96C38000)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Wed 24/06/2009 09:47:06 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC040E580, 0xC000000E, 0x612C4860, 0x81CB001F)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Tue 23/06/2009 22:40:44 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC040E530, 0xC000000E, 0x6F9D8860, 0x81CA601F)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Tue 23/06/2009 15:29:53 your computer crashed
    This was likely caused by the following module: csrss.exe
    Bugcheck code: 0xF4 (0x3, 0x872D2A08, 0x872D2B54, 0x81C89400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\csrss.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Client Server Runtime Process
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 15:12:11 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040DCA8, 0xC000000E, 0x2C9A1860, 0x81B9534A)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 14:47:41 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040DD18, 0xC000000E, 0x6D3E0860, 0x81BA3501)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 14:24:56 your computer crashed
    This was likely caused by the following module: csrss.exe
    Bugcheck code: 0xF4 (0x3, 0x85E62140, 0x85E6228C, 0x81C8C400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\csrss.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Client Server Runtime Process
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 13:40:28 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC040E4D0, 0xC000000E, 0x16A02860, 0x81C9A01F)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Tue 23/06/2009 13:13:34 your computer crashed
    This was likely caused by the following module: csrss.exe
    Bugcheck code: 0xF4 (0x3, 0x85E62140, 0x85E6228C, 0x81C8C400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\csrss.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Client Server Runtime Process
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 13:00:26 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040DBE0, 0xC000000E, 0x98CE7860, 0x81B7C501)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Tue 23/06/2009 12:14:55 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC04CA4C8, 0xC000000E, 0x158688C0, 0x9949908C)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 21:42:30 your computer crashed
    This was likely caused by the following module: wininit.exe
    Bugcheck code: 0xF4 (0x3, 0x87118340, 0x8711848C, 0x81C40400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\wininit.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Windows Start-Up Application
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 21:29:23 your computer crashed
    This was likely caused by the following module: srv.sys
    Bugcheck code: 0x7A (0xC04E1148, 0xC000000E, 0x6702E860, 0x9C2299D5)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\srv.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Server driver
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 21:06:18 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC040E648, 0xC000000E, 0x7CC41860, 0x81CC9FBF)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Mon 22/06/2009 1839 your computer crashed
    This was likely caused by the following module: csrss.exe
    Bugcheck code: 0xF4 (0x3, 0x86B0AD90, 0x86B0AEDC, 0x81C58400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\csrss.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Client Server Runtime Process
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 18:13:21 your computer crashed
    This was likely caused by the following module: wininit.exe
    Bugcheck code: 0xF4 (0x3, 0x868CA340, 0x868CA48C, 0x81C79400)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\wininit.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Windows Start-Up Application
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 16:53:18 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040E390, 0xC000000E, 0x5B7EF860, 0x81C72FC2)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 15:57:34 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040E530, 0xC000000E, 0x4980D860, 0x81CA6FC2)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 14:01:45 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC0604000, 0xC000000E, 0x8D040880, 0xC0800000)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Mon 22/06/2009 13:39:15 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x77 (0xC000000E, 0xC000000E, 0x0, 0x1A6BA000)
    Error: KERNEL_STACK_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Mon 22/06/2009 11:28:00 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC04828F8, 0xC000000E, 0x77B098C0, 0x9051FFF4)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



    On Sun 21/06/2009 22:09:49 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC0604000, 0xC000000E, 0x2594C880, 0xC0800000)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Sun 21/06/2009 21:47:42 your computer crashed
    This was likely caused by the following module: symevent.sys
    Bugcheck code: 0x7A (0xC040E550, 0xC000000E, 0x370AE860, 0x81CAA01F)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\symevent.sys
    product: SYMEVENT
    company: Symantec Corporation
    description: Symantec Event Library



    On Sat 20/06/2009 22:45:10 your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x7A (0xC040DCA8, 0xC000000E, 0x7373860, 0x81B957B6)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

  10. #10
    cricky is offline Newbie
    24 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

+ Reply to Thread
Page 1 of 2 1 2 LastLast