locked
Blue screen crash RRS feed

  • Question

  • Hi I just got my new Vostro 230 computer a week ago and it keeps blue screen crashing everyday.

    Here is the report I got from the dumpfile:

     

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7600.2.0.0.768.3
    Locale ID:    1033

    Extra information about the problem
    BCCode:    50
    BCP1:    80000024
    BCP2:    00000000
    BCP3:    90DD9BE7
    BCP4:    00000000
    OS Version:    6_1_7600
    Service Pack:    0_0
    Product:    768_1
    Bucket ID:    0x50_tmcomm!ModUnLoadModule+1ac3
    Server information:    77de5a78-0b85-496f-ac1a-36302532fa58

    It would be so helpful if some 1 can give me the steps to get rid of this please!

     

    Thanks!

    Thursday, March 3, 2011 10:25 PM

Answers

  • 1- Run a full scan to detect and uninstall malware programs (It is possible that tmcomm.sys was installed by a malware program). You can download and install Microsoft Security Essentials to perform that.

    2- If you perform the scan and you have not found any malware programs then you should update the faulty driver. The faulty driver belongs to TrendMicro Common module. So, search an update for that driver on www.trendmicro.com website and install it.

    3- If you update the driver and the problem persists, you should contact Trend Micro Technical Support to solve your problem.

    4- You can also uninstall TrenMicro Common module driver if you don't need it.

    That should solve your problem.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

     

    • Marked as answer by Cloud_TS Tuesday, March 22, 2011 8:52 AM
    Friday, March 4, 2011 10:23 PM

All replies

  • Bug Check Code 0x50: The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

    For more information, refer to this Microsoft article.

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps) and post a link here so that I upload them and I determine the cause of your problem.

    If you want to debug yourself your dump files, refer to this Microsoft article.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, March 3, 2011 10:34 PM
  • Ok I put the minidump on the Microsoft Skydriver.

     

    Heres the address

     

    http://cid-d6849437ea6dc47a.office.live.com/self.aspx/Crashing%20Blue%20screen/030311-25287-01.dmp

    Thursday, March 3, 2011 11:23 PM
  • heres the address to the mindump file

     

    http://cid-d6849437ea6dc47a.office.live.com/self.aspx/Crashing%20Blue%20screen/030311-25287-01.dmp

    Thursday, March 3, 2011 11:49 PM
  • Hi I just got my new Vostro 230 computer a week ago and it keeps blue screen crashing everyday.

    Here is the report I got from the dumpfile:

     

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7600.2.0.0.768.3
    Locale ID:    1033

    Extra information about the problem
    BCCode:    50
    BCP1:    80000024
    BCP2:    00000000
    BCP3:    90DD9BE7
    BCP4:    00000000
    OS Version:    6_1_7600
    Service Pack:    0_0
    Product:    768_1
    Bucket ID:    0x50_tmcomm!ModUnLoadModule+1ac3
    Server information:    77de5a78-0b85-496f-ac1a-36302532fa58

    It would be so helpful if some 1 can give me the steps to get rid of this please!

     

    Thanks!

     

     

    I also uploaded the dump file  at Microsfot Skydrive

    This is the address:  

    http://cid-d6849437ea6dc47a.office.live.com/self.aspx/Crashing%20Blue%20screen/030311-25287-01.dmp

    • Merged by Cloud_TS Monday, March 7, 2011 7:41 AM duplicate
    Friday, March 4, 2011 12:55 AM
  • 1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: 80000024, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 90dd9be7, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000000, (reserved)

    Debugging Details:
    ------------------

    Unable to load image \SystemRoot\system32\DRIVERS\tmcomm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for tmcomm.sys
    *** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys

    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82973718
    Unable to read MiSystemVaType memory at 829531e0
     80000024

    FAULTING_IP:
    tmcomm+fbe7
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h]

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    TRAP_FRAME:  97867b78 -- (.trap 0xffffffff97867b78)
    ErrCode = 00000000
    eax=80000000 ebx=8288f98e ecx=00989680 edx=8293f350 esi=00000000 edi=00989680
    eip=90dd9be7 esp=97867bec ebp=97867c18 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    tmcomm+0xfbe7:
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h] ds:0023:80000024=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 8284fa48 to 82892368

    STACK_TEXT: 
    97867b60 8284fa48 00000000 80000024 00000000 nt!MmAccessFault+0x106
    97867b60 90dd9be7 00000000 80000024 00000000 nt!KiTrap0E+0xdc
    WARNING: Stack unwind information not available. Following frames may be wrong.
    97867c18 90dd9de0 8293f350 97867c30 938ab0d8 tmcomm+0xfbe7
    97867c38 90ddb1b6 8293f350 97867c60 8293f350 tmcomm+0xfde0
    97867c64 90ddb99c 00000000 938ab01c 938ab080 tmcomm+0x111b6
    97867c80 90ddc177 938ab0d8 00000000 938ab01c tmcomm+0x1199c
    97867c9c 90ddc34d 0758ff82 00000000 872b09dc tmcomm+0x12177
    97867cf8 90dcd782 ae42bb50 90dd199c 0758fe4e tmcomm+0x1234d
    97867d34 90dd1c71 00000000 00000000 872b0398 tmcomm+0x3782
    97867d50 82a19f9b 872b0398 b9e193ba 00000000 tmcomm+0x7c71
    97867d90 828ccae9 90dd189c 872b0398 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    tmcomm+fbe7
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h]

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  tmcomm+fbe7

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: tmcomm

    IMAGE_NAME:  tmcomm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a519551

    FAILURE_BUCKET_ID:  0x50_tmcomm+fbe7

    BUCKET_ID:  0x50_tmcomm+fbe7

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

    1: kd> lmvm tmcomm
    start    end        module name
    90dca000 90df6000   tmcomm   T (no symbols)          
        Loaded symbol image file: tmcomm.sys
        Image path: \SystemRoot\system32\DRIVERS\tmcomm.sys
        Image name: tmcomm.sys
        Timestamp:        Mon Jul 06 08:10:25 2009 (4A519551)
        CheckSum:         0002DD9A
        ImageSize:        0002C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    ---------------------------------------------------------------------------------------

    Your BSOD was caused by tmcomm.sys driver. It is possible that this is a malware program so please perform a full scan on your computer to detect and uninstall malware programs.

    If it is not a malware program, this process belongs to TrendMicro Common module (www.trendmicro.com) so try to update it or contact Trend Micro Technocal Support.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

     

    Friday, March 4, 2011 8:39 AM
  • 1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: 80000024, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 90dd9be7, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

    Debugging Details:
    ------------------

    Unable to load image \SystemRoot\system32\DRIVERS\tmcomm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for tmcomm.sys
    *** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys

    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82973718
    Unable to read MiSystemVaType memory at 829531e0
     80000024 

    FAULTING_IP: 
    tmcomm+fbe7
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h]

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    TRAP_FRAME:  97867b78 -- (.trap 0xffffffff97867b78)
    ErrCode = 00000000
    eax=80000000 ebx=8288f98e ecx=00989680 edx=8293f350 esi=00000000 edi=00989680
    eip=90dd9be7 esp=97867bec ebp=97867c18 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    tmcomm+0xfbe7:
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h] ds:0023:80000024=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 8284fa48 to 82892368

    STACK_TEXT:  
    97867b60 8284fa48 00000000 80000024 00000000 nt!MmAccessFault+0x106
    97867b60 90dd9be7 00000000 80000024 00000000 nt!KiTrap0E+0xdc
    WARNING: Stack unwind information not available. Following frames may be wrong.
    97867c18 90dd9de0 8293f350 97867c30 938ab0d8 tmcomm+0xfbe7
    97867c38 90ddb1b6 8293f350 97867c60 8293f350 tmcomm+0xfde0
    97867c64 90ddb99c 00000000 938ab01c 938ab080 tmcomm+0x111b6
    97867c80 90ddc177 938ab0d8 00000000 938ab01c tmcomm+0x1199c
    97867c9c 90ddc34d 0758ff82 00000000 872b09dc tmcomm+0x12177
    97867cf8 90dcd782 ae42bb50 90dd199c 0758fe4e tmcomm+0x1234d
    97867d34 90dd1c71 00000000 00000000 872b0398 tmcomm+0x3782
    97867d50 82a19f9b 872b0398 b9e193ba 00000000 tmcomm+0x7c71
    97867d90 828ccae9 90dd189c 872b0398 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    tmcomm+fbe7
    90dd9be7 8b7824          mov     edi,dword ptr [eax+24h]

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  tmcomm+fbe7

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: tmcomm

    IMAGE_NAME:  tmcomm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a519551

    FAILURE_BUCKET_ID:  0x50_tmcomm+fbe7

    BUCKET_ID:  0x50_tmcomm+fbe7

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

    ---------------------------------------------------------------------------------------

    Your BSOD was caused by tmcomm.sys driver. It is possible that this is a malware program so please perform a full scan on your computer to detect and uninstall malware programs.

    If it is not a malware program, this process belongs to TrendMicro Common module (www.trendmicro.com) so try to update it or contact Trend Micro Technocal Support.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    • Proposed as answer by Andre.Ziegler Friday, March 4, 2011 11:55 AM
    Friday, March 4, 2011 10:48 AM
  • don't double post the same issue:

    http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/6307fee2-4aeb-4873-9094-0ce058fee0af/


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    Friday, March 4, 2011 11:57 AM
  • Wait I don't get what steps to take.

     

    ---------------------------------------------------------------------------------------

    Your BSOD was caused by tmcomm.sys driver. It is possible that this is a malware program so please perform a full scan on your computer to detect and uninstall malware programs.

    If it is not a malware program, this process belongs to TrendMicro Common module (www.trendmicro.com ) so try to update it or contact Trend Micro Technocal Support.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     

    Can you give me baby steps to solve this problem?

     

    Sorry I'm slow

    Friday, March 4, 2011 10:14 PM
  • 1- Run a full scan to detect and uninstall malware programs (It is possible that tmcomm.sys was installed by a malware program). You can download and install Microsoft Security Essentials to perform that.

    2- If you perform the scan and you have not found any malware programs then you should update the faulty driver. The faulty driver belongs to TrendMicro Common module. So, search an update for that driver on www.trendmicro.com website and install it.

    3- If you update the driver and the problem persists, you should contact Trend Micro Technical Support to solve your problem.

    4- You can also uninstall TrenMicro Common module driver if you don't need it.

    That should solve your problem.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

     

    • Marked as answer by Cloud_TS Tuesday, March 22, 2011 8:52 AM
    Friday, March 4, 2011 10:23 PM