1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

bsod from ntkrnlpa.exe after virus removal

Discussion in 'Windows 7' started by zling, Dec 8, 2011.

Thread Status:
Not open for further replies.
Advertisement
  1. zling

    zling Thread Starter

    Joined:
    Dec 8, 2011
    Messages:
    2
    after catching then removing win 7 home security 2012 (a rogue antivirus) i have been getting concistent bsods, according to blue screen view they are from ntkrnlpa.exe, but i have not been able to find a solution. im attaching my dump files. any help is greatly appreciated.
     

    Attached Files:

  2. Elvandil

    Elvandil

    Joined:
    Aug 1, 2003
    Messages:
    51,988
    That's the Windows kernel, so not much you can do about that file itself. But the kernel errors are usually caused by some other kernel-mode driver.

    These dumps are most often graphics or network card drivers, so try reinstalling/updating those, too.

    How did you catch and remove the infection?
     
  3. Elvandil

    Elvandil

    Joined:
    Aug 1, 2003
    Messages:
    51,988
    I've only done the first dump so far, but it was due to aswsp.sys, your AV driver.
     
  4. Elvandil

    Elvandil

    Joined:
    Aug 1, 2003
    Messages:
    51,988
    On Thu 2011-12-08 03:33:17 your computer crashed
    crash dump file: C:\windows\Minidump\120811-70886-01.dmp
    uptime: 00:25:04
    This was probably caused by the following module: nvm62x32.sys (nvm62x32+0x4616)
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82C797E3)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    On Thu 2011-12-08 01:47:57 your computer crashed
    crash dump file: C:\windows\Minidump\120711-57189-01.dmp
    uptime: 02:37:24
    This was probably caused by the following module: hal.sys ([email protected]@8+0x88)
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82C8B7E3)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    On Sat 2011-12-03 21:27:29 your computer crashed
    crash dump file: C:\windows\memory.dmp
    uptime: 21:32:32
    This was probably caused by the following module: win32k.sys (win32k!EngCreatePath+0x40D)
    Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF96939E60, 0xFFFFFFFFB1C639DC, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    file path: C:\windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
    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 Fri 2011-05-20 21:06:56 your computer crashed
    crash dump file: C:\windows\Minidump\052011-20732-01.dmp
    uptime: 09:55:26
    This was probably caused by the following module: lv302v32.sys (LV302V32+0x1252A)
    Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFFCBA4952A)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.





    On Sun 2011-01-09 19:05:00 your computer crashed
    crash dump file: C:\windows\Minidump\010911-26176-01.dmp
    uptime: 1 day, 05:57:38
    This was probably caused by the following module: aswsp.sys (aswSP+0x1D6B1)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B6B067, 0xFFFFFFFFA2BFDA3C, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\windows\system32\drivers\aswsp.sys
    product: avast! Antivirus System
    company: AVAST Software

    ============================================

    This looks like bad RAM.

    Memory Testing (including bootable CD's and floppies):

    Memtest86
    MemScope (Floppy and CD images.)
    Roadkil's RAM Test
    Microsoft Memory Test (floppy or CD ISO image)

    If you have enough memory sticks, you can test them by removing one at a time and see if the problem disappears.

    If you are running Vista or 7, tap F8 on boot and choose the memory diagnostic, or if you can boot up, go to Start > Search and type:

    mdsched.exe

    Choose to run a memory diagnostic on next boot. Or, you can boot from the DVD and run it from there.
     
  5. zling

    zling Thread Starter

    Joined:
    Dec 8, 2011
    Messages:
    2
    wow, you guys are great, thanks for the replies. im going to look into the things you listed and see if i can figure out whats going on.

    elvandil, i used my google-fu to figure out exactly what it was then i just went into safe mode and ran a bunch of scans n stuff
     
  6. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1030307

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice