locked
BSOD 0x00000050, sometimes 0x0000008e RRS feed

  • Question

  • Hi

    BSOD 0x00000050 error shows up few times in month. Sometimes more than 5 times in week on 10 of 50 computers. All computers have different hardware but all are running Windows XP SP3 with Novell Client  and our software. BSOD most of the time shows up when button is pressed in our program when there is network activity (downloading information from servers).

    All of computers are tested with memtest, mhdd, have changed antivirus from kaspersky to nod, avg or panda, updated bios and latest drivers.

    I have read many articles and tryed many solution what i found, but nothing helps me..

    Can anyone help me to solve this problem? I can add some dmp files  if needed. 

    [PC1]


    CPU: Intel(R) Pentium(R) D CPU 2.80GHz
    RAM: 1016 MB
    OS:  Microsoft Windows XP
    SP:  Service Pack 3
    2009-06-10 17:37:58   0:08:26:06 10000050 e138f010 00000000 bf90bfab
    2009-06-15 10:41:28   0:01:32:22 10000050 e3681010 00000000 bf90c0bb
    2009-10-22 11:19:39   0:02:22:00 10000050 e3780010 00000000 bf90c0bb
    2009-11-13 10:07:19   0:01:05:25 10000050 e39d1010 00000000 bf90c866

    2011-07-13 10:26:19   0:00:57:36 10000050 e3331010 00000000 bf90d643

    2011-07-22 10:03:50   0:01:00:36 10000050 e379e010 00000000 bf90cadc

    2012-05-18 16:36:07   0:00:22:45 10000050 e3673010 00000000 bf90cd6b
    2012-07-19 13:09:38   0:04:08:59 10000050 e1f19010 00000000 bf90d966
    2012-07-19 14:53:33   0:01:43:30 10000050 e3586010 00000000 bf90d966
    2012-07-19 15:26:43   0:00:32:44 10000050 e37a7010 00000000 bf90d966
    2012-08-20 11:27:13   0:01:49:53 10000050 e3713010 00000000 bf90d976
    2012-08-23 16:39:05   0:02:33:19 10000050 e353b010 00000000 bf90d976
    2012-08-23 18:01:18   0:01:21:48 10000050 e33ec010 00000000 bf90d976
    2012-08-24 10:59:42   0:16:57:59 10000050 e359e010 00000000 bf90d976

    [PC2]

    CPU: Intel(R) Pentium(R) D CPU 2.80GHz
    RAM: 1016 MB
    OS:  Microsoft Windows XP
    SP:  Service Pack 3
    2008-02-26 13:58:17   0:01:57:18 10000050 e2f70010 00000000 bf90b8ba
    2009-05-07 10:12:40   0:01:02:41 10000050 e3725010 00000000 bf90bfab
    2010-04-28 12:46:41   0:03:57:25 10000050 e34bf010 00000000 bf90c866
    2011-12-13 12:13:57   0:00:11:35 10000050 e39df010 00000000 bf90cb2a
    2012-01-04 15:33:32   0:01:24:18 10000050 e3661010 00000000 bf90cb81
    2012-05-14 12:43:39   0:03:22:10 10000050 e32fa010 00000000 bf90cc5d
    2012-05-16 12:00:42   0:02:44:20 10000050 e319c010 00000000 bf90cd6b
    2012-08-07 10:13:55   0:00:10:11 10000050 e3de9010 00000000 bf90d966
    2012-09-04 10:36:44   1:22:10:03 10000050 e3273010 00000000 bf90d976


    ADDITIONAL_DEBUG_TEXT:  
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

    MODULE_NAME: win32k

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  45f013f6

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPagedPoolEnd
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     e2f1f010 

    FAULTING_IP: 
    win32k+10b8ba
    bf90b8ba 663901          cmp     word ptr [ecx],ax

    MM_INTERNAL_CODE:  1

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    LAST_CONTROL_TRANSFER:  from bf90b797 to bf90b8ba

    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a9744d18 bf90b797 00280000 002581c8 00000100 win32k+0x10b8ba
    a9744d50 804dd99f 00280000 002581c8 00000100 win32k+0x10b797
    a9744d64 7c90eb94 badb0d00 0021d94c 00000000 nt+0x699f
    a9744d68 badb0d00 0021d94c 00000000 00000000 0x7c90eb94
    a9744d6c 0021d94c 00000000 00000000 00000000 0xbadb0d00
    a9744d70 00000000 00000000 00000000 00000000 0x21d94c


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    win32k+10b8ba
    bf90b8ba 663901          cmp     word ptr [ecx],ax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k+10b8ba

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  win32k.sys

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner
    ---------

    Tuesday, November 27, 2012 10:56 AM

All replies

  • Did you try swapping out RAM?  We had some issues with RAM in the past that were generating BSOD error 50
    Tuesday, November 27, 2012 5:58 PM
  • There are diferent RAM kits in each computer. And all computers with this error has been tested with memetest.
    Wednesday, November 28, 2012 7:54 PM