random BSOD win32k.sys


  1. Posts : 3
    windows 7
       #1

    random BSOD win32k.sys


    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 of 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.

    attached are my dump files
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    21 memory dumps from 08 Feb 2010 to the present.
    8 different STOP errors, at least 5 different causes blamed.

    I'd have to suspect a hardware problem here - either broken hardware or an incompatible piece of hardware or software.

    The Driver Verifier enabled memory dump and the STOP 0x10E memory dump both point at video issues - so I'd suggest that you start by replacing your video drivers.

    Then run this video stress test to see if it points at your video:
    FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    - Click "Quit" to exit
    Summary of the BSOD's:
    Code:
    
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Sat May  1 22:58:13.049 2010 (GMT-4)
    System Uptime: 0 days 5:59:39.081
    BugCheck 1000008E, {c0000005, 933a41a8, 97c3799c, 0}
    Probably caused by : hardware ( win32k!GreGetDIBitsInternal+163 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  msnmsgr.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Sat May  1 16:49:13.434 2010 (GMT-4)
    System Uptime: 0 days 0:08:07.465
    BugCheck 1000008E, {c0000005, 82c4d5d3, a32c7b44, 0}
    Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+28 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  taskhost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Sat May  1 00:30:57.947 2010 (GMT-4)
    System Uptime: 0 days 3:02:34.978
    BugCheck 1000008E, {c0000005, 97bfbf9b, 88110a60, 0}
    Probably caused by : win32k.sys ( win32k!EXLATEOBJ::vAltUnlock+6 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Fri Apr 30 21:27:47.054 2010 (GMT-4)
    System Uptime: 0 days 0:57:49.070
    BugCheck 1000008E, {c0000005, 9777d1fa, a29d6c88, 0}
    Probably caused by : hardware ( win32k!SURFREF::vAltCheckLockIgnoreStockBit+11 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Tue Apr 13 22:08:44.841 2010 (GMT-4)
    System Uptime: 0 days 0:21:17.873
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Mon Apr 12 23:21:44.475 2010 (GMT-4)
    System Uptime: 0 days 1:28:20.491
    BugCheck 1000008E, {c0000005, 82080834, 8ed0b894, 0}
    Probably caused by : win32k.sys ( win32k!EngpMovePointer+26 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Apr  3 17:44:47.963 2010 (GMT-4)
    System Uptime: 0 days 16:39:15.979
    BugCheck 1000008E, {c0000005, 97814cff, a2df38f4, 0}
    Probably caused by : win32k.sys ( win32k!ReleaseCacheDC+2f )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Apr  3 01:04:55.893 2010 (GMT-4)
    System Uptime: 1 days 1:08:00.924
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    BUGCHECK_STR:  0xF7
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Thu Apr  1 23:56:20.569 2010 (GMT-4)
    System Uptime: 0 days 0:22:09.600
    BugCheck 1000008E, {c0000005, 821fe1eb, a3765c58, 0}
    Probably caused by : hardware ( win32k!XDCOBJ::bCleanDC+9 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Wed Mar 31 21:32:01.168 2010 (GMT-4)
    System Uptime: 0 days 0:35:51.200
    BugCheck A, {c0005130, 0, 0, 82a7a6a1}
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+175 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Wed Mar 24 16:08:52.351 2010 (GMT-4)
    System Uptime: 0 days 4:44:57.351
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Mar 20 18:59:27.080 2010 (GMT-4)
    System Uptime: 1 days 21:41:55.354
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    BugCheck 1000008E, {c0000005, 976d7315, a349bae8, 0}
    Probably caused by : win32k.sys ( win32k+77315 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Thu Mar 11 21:48:23.680 2010 (GMT-4)
    System Uptime: 0 days 0:36:43.727
    BUGCHECK_STR:  0x10e_1f
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Tue Mar  2 00:29:13.106 2010 (GMT-4)
    System Uptime: 0 days 2:22:55.153
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Mon Mar  1 00:04:10.007 2010 (GMT-4)
    System Uptime: 0 days 2:28:02.054
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Feb 20 22:13:30.953 2010 (GMT-4)
    System Uptime: 0 days 0:00:19.031
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    BUGCHECK_STR:  0xc9_c
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Wed Feb 17 23:38:35.995 2010 (GMT-4)
    System Uptime: 0 days 3:19:53.026
    BugCheck 1000008E, {c0000005, 968f0ed5, 8eb17af4, 0}
    Probably caused by : win32k.sys ( win32k!DCESpeedHitTest+39 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Feb 13 22:45:36.974 2010 (GMT-4)
    System Uptime: 0 days 3:52:53.021
    BugCheck 1000008E, {c0000005, 96f1c7f7, 98e93c5c, 0}
    Probably caused by : hardware ( win32k!_GetDCEx+2da )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Feb 13 18:52:12.184 2010 (GMT-4)
    System Uptime: 0 days 4:24:47.200
    BugCheck A, {c000e6a8, 0, 0, 828856a1}
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+175 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Debug session time: Sat Feb 13 00:51:36.888 2010 (GMT-4)
    System Uptime: 1 days 3:37:06.935
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 00:28:12.770 2010 (GMT-4)
    System Uptime: 0 days 3:01:40.801
    BugCheck 1000008E, {c0000005, 822cd913, 8cf5fc68, 0}
    Probably caused by : win32k.sys ( win32k!hbmSelectBitmap+165 )
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  firefox.exe
    
      My Computer


  3. Posts : 3
    windows 7
    Thread Starter
       #3

    Thanks for the reply. I ran FurMark and i didnt encounter a problem while it was running, temperature started at 50'C and maxed out at 64'C. Before that i updated to the latest Nvidia drivers. I removed a tv turner pci card and a wireless pci card. I don't use them anyways and maybe one of these two was the culprit. I also removed the original 2X512 sticks and left the 2X1GB sticks which i recently bought just in case. I did not leave the original 2X512 instead because when i first tried installing windows 7 with the 2X512 sticks it would not install, thats why i had to buy more ram. Thank you for your help! any other suggestion will be appreciated. I'll report if i encounter more crashes, hopefully i dont. Thanks once again.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    If it gives you more problems, try these free tests:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

    *****
    Additional tests for certain specific circumstances:

    Try this free stress test: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    The Test selection box and the stress.txt file describes what components that the program stresses.
      My Computer


  5. Posts : 3
    windows 7
    Thread Starter
       #5

    well its been a week and since then i have not had a single crash! i'm thinking my problem has been solved, thank you.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 06:32.
Find Us