locked
BSOD RRS feed

  • Question

  • Hi everyone,

    Need help, my computer keeps crashing when booting up to Windows... I have several dumps....

    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 17155919872 total
    VM: 2147352576, free: 1935843328




    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Mon 28-01-2013 18:11:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012813-26457-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0x3398) 
    Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88001639398, 0xFFFFF8800789A700, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Mon 28-01-2013 18:11:58 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ndis.sys (ndis!NdisFOidRequestComplete+0x1E8) 
    Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88001639398, 0xFFFFF8800789A700, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Mon 28-01-2013 18:09:19 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012813-27830-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7A8C0) 
    Bugcheck code: 0x50 (0xFFFFB8A000004BE0, 0x0, 0xFFFFF8000318528D, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



    On Mon 28-01-2013 18:07:32 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012813-24882-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0x3398) 
    Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88001676398, 0xFFFFF88003762018, 0xFFFFF88003761870)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Sat 26-01-2013 13:43:00 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-26208-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0x3398) 
    Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88001603398, 0xFFFFF88003761F28, 0xFFFFF88003761780)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Fri 18-01-2013 00:15:38 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011813-25038-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0x3398) 
    Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF880016F5398, 0xFFFFF88003761F28, 0xFFFFF88003761780)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Mon 14-01-2013 18:03:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011413-18626-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7A8C0) 
    Bugcheck code: 0x50 (0xFFFFB8A000004BE0, 0x0, 0xFFFFF8000318528D, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



    On Fri 11-01-2013 19:52:50 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011113-24648-01.dmp
    This was probably caused by the following module: ndis.sys (0xFFFFF88001725FF0) 
    Bugcheck code: 0x109 (0xA3A039D8AA5AF673, 0xB3B7465EFCD8D475, 0xFFFFF88001725FF0, 0x1)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Sistema Operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Controlador NDIS 6.20
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    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 that cannot be identified at this time. 



    On Mon 07-01-2013 03:26:31 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011113-20763-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7A8C0) 
    Bugcheck code: 0x9F (0x3, 0xFFFFFA800D78BA10, 0xFFFFF80000B9C3D8, 0xFFFFFA8010335A10)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



    On Sat 29-12-2012 17:34:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122912-22245-01.dmp
    This was probably caused by the following module: netio.sys (NETIO+0xD38D) 
    Bugcheck code: 0xD1 (0x8024BC, 0x2, 0x1, 0xFFFFF8800178A38D)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\netio.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Network I/O Subsystem
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 



    On Fri 21-12-2012 01:39:06 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122212-19110-01.dmp
    This was probably caused by the following module: netio.sys (0xFFFFF8800140438B) 
    Bugcheck code: 0x50 (0xFFFFFA7F9765BCC9, 0x0, 0xFFFFF8800140438B, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\netio.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Network I/O Subsystem
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    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 that cannot be identified at this time. 





    Any help????????? PLZ

    Monday, January 28, 2013 7:05 PM

Answers

  • Hi,

     

    According to BSOD error codes, you can refer to Bug Check Code Reference.

     

    To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Before we could get your Minidump files, you can check following:

     

    1. Update your BIOS, chipset and the drivers

    2. Scan the system to check for the virus

    3. Test the issue in Clean Boot and Safe Mode

     

    Hope this helps.


    Vincent Wang
    TechNet Community Support

    Wednesday, January 30, 2013 3:23 AM

All replies


  • ndis.sys  is a network driver issue. I'd suggest you to install NIC driver in compatibility mode.

    See this thread, if you don't know how to do this:

    social.technet.microsoft.com/Forums/en/w7itprohardware/thread/80cae5ee-dc98-4a2f-8284-a1ab826059b7

    Good Luck!!


    • Edited by ajms1989 Tuesday, January 29, 2013 4:32 AM
    Tuesday, January 29, 2013 4:32 AM
  • Hi,

     

    According to BSOD error codes, you can refer to Bug Check Code Reference.

     

    To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Before we could get your Minidump files, you can check following:

     

    1. Update your BIOS, chipset and the drivers

    2. Scan the system to check for the virus

    3. Test the issue in Clean Boot and Safe Mode

     

    Hope this helps.


    Vincent Wang
    TechNet Community Support

    Wednesday, January 30, 2013 3:23 AM