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.

multiple BSOD win32k.sys

Discussion in 'Windows 7' started by Rafis69, May 2, 2010.

Thread Status:
Not open for further replies.
  1. Rafis69

    Rafis69 Thread Starter

    Joined:
    May 1, 2002
    Messages:
    23
    Hi, i've been having multiple BSOD ever since i installed windows 7 86bit on my computer! before i had windows vista. Before installing windows 7 i had to upgrade my computer with memory, i installed 2X1G memory sticks, the computer already had 2X512mb installed. I also installed a 1G nvidia GeForce 9500 GT graphics card. The blue screens appear every day or every 2-3 days, sometimes two times in the same day. It always points to the win32k.sys. I've have installed the latest updates for my drivers, have run memtest run overnight with no errors. Have tried formatting and installing windows7 two times but the BSOD keep appearing. I also ran a chkdsk on the drive an still getting the errors. I ran the system health report on windows and everything passed. I have googled my problem with no luck. Mys specs are
    Hp pavilion a1357c pc
    amd athlon 64x2 Dual core processor 4200+
    3GB or Ram
    240 GB hard disk
    motherboard model A8AE-LE (AmberineM)

    Please help with any kind of suggestion, I would apprecciate your help in trying to resolve this problem. Thank you.

    here is a whocrashed report that might help!
    On Sun 5/2/2010 2:59:35 AM your computer crashed
    This was likely caused by the following module: hardware
    Bugcheck code: 0x1000008E (0xC0000005, 0x933A41A8, 0x97C3799C, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\050110-40625-01.dmp



    On Sat 5/1/2010 8:50:25 PM your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1000008E (0xC0000005, 0x82C4D5D3, 0xA32C7B44, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\050110-30046-01.dmp
    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. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 5/1/2010 4:32:28 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x97BFBF9B, 0x88110A60, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\043010-33687-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 5/1/2010 1:28:55 AM your computer crashed
    This was likely caused by the following module: hardware
    Bugcheck code: 0x1000008E (0xC0000005, 0x9777D1FA, 0xA29D6C88, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\043010-32656-01.dmp



    On Wed 4/14/2010 2:09:59 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x50 (0xE7010995, 0x1, 0x81FBC3F4, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\041310-25671-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Tue 4/13/2010 3:23:14 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x82080834, 0x8ED0B894, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\041210-29250-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 4/3/2010 9:46:13 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x97814CFF, 0xA2DF38F4, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\040310-24890-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 4/3/2010 5:05:57 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0xF7 (0x371AF2AD, 0x979566B6, 0x686A9949, 0x0)
    Error: DRIVER_OVERRAN_STACK_BUFFER
    Dump file: C:\Windows\Minidump\040210-25859-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Fri 4/2/2010 3:57:19 AM your computer crashed
    This was likely caused by the following module: hardware
    Bugcheck code: 0x1000008E (0xC0000005, 0x821FE1EB, 0xA3765C58, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\040110-24671-01.dmp



    On Thu 4/1/2010 1:33:02 AM your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0xA (0xC0005130, 0x0, 0x0, 0x82A7A6A1)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\033110-26875-01.dmp
    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. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Wed 3/24/2010 8:11:03 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x50 (0xA34B0CCC, 0x0, 0x97288186, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\032410-32375-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 3/20/2010 11:00:25 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x976D7315, 0xA349BAE8, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\032010-25984-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Fri 3/12/2010 1:49:47 AM your computer crashed
    This was likely caused by the following module: dxgmms1.sys
    Bugcheck code: 0x10E (0x1F, 0x97C009B8, 0x0, 0xC5F4)
    Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
    Dump file: C:\Windows\Minidump\031110-24921-01.dmp
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Tue 3/2/2010 4:30:35 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1A (0x5003, 0x96630000, 0x2F80, 0xBC4FA2)
    Error: MEMORY_MANAGEMENT
    Dump file: C:\Windows\Minidump\030110-25609-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Mon 3/1/2010 4:05:33 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1A (0x5003, 0xC0802000, 0xDF42, 0x13E28009)
    Error: MEMORY_MANAGEMENT
    Dump file: C:\Windows\Minidump\022810-26218-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sun 2/21/2010 2:14:28 AM your computer crashed
    This was likely caused by the following module: nvlddmkm.sys
    Bugcheck code: 0xC9 (0xC, 0x87B274F4, 0x8EB68F68, 0x0)
    Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
    Dump file: C:\Windows\Minidump\022010-29328-01.dmp
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 197.45
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 197.45



    On Thu 2/18/2010 3:40:16 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x968F0ED5, 0x8EB17AF4, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\021710-35250-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sun 2/14/2010 2:46:37 AM your computer crashed
    This was likely caused by the following module: hardware
    Bugcheck code: 0x1000008E (0xC0000005, 0x96F1C7F7, 0x98E93C5C, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\021310-24656-01.dmp



    On Sat 2/13/2010 10:53:08 PM your computer crashed
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0xA (0xC000E6A8, 0x0, 0x0, 0x828856A1)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\021310-24906-01.dmp
    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. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Sat 2/13/2010 4:52:45 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x50 (0xFFFFFF55, 0x0, 0x8287B7D5, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\021210-24234-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



    On Tue 2/9/2010 4:29:51 AM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x822CD913, 0x8CF5FC68, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\020810-35468-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
     
  2. unbidden

    unbidden

    Joined:
    Jun 9, 2005
    Messages:
    1,469
    There is 32 bit and 64 bit installs. Do you mean x86 based? x86 is 32 bit. If running 32 bit, try installing the original RAM only and see if you have the errors; my thinking is incompatible RAM. You may also want to try removing the 2 x 512 banks and try the 2 x 1gb only.

    =============
    To see if your computer is running a 32-bit or 64-bit version of Windows, do the following:

    1. Open System by clicking the Start button Windows, clicking Control Panel, clicking System and Security, and then clicking System.
    2. Under System, you can view the system type.
     
  3. Rafis69

    Rafis69 Thread Starter

    Joined:
    May 1, 2002
    Messages:
    23
    thanks for the reply, i meant to say the 32-bit x86 based, when i first tried installing windows 7 with the original 2x512 banks it would not let me install it thats why i bought the kingston 2x1GB sticks. I just removed the 2X512 banks and hopefully it will do the trick, sometimes it takes up to 3 days to crash, i'll just have to wait and see if it works. Thanks once again and i will report if i encounter a crash or if after a week i dont get a crash then i will also report and assume it was the 512 mixed with the 1gb ram that was causing the crashes!
     
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/920589

  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