Results 1 to 7 of 7

Thread: BlueScreen

  1. #1
    Member
    Join Date
    Feb 2015
    Posts
    4
    Points
    0

    Default BlueScreen

    Hello

    I have a problem with my computer. It restarts without any reason (that i know), when i less expect. The screen becomes blue and some info appears.

    After restart this is the info that windows gives:

    Assinatura do problema:
    Nome do Evento de Problema: BlueScreen
    VersŃo do SO: 6.1.7601.2.1.0.256.1
    ID de RegiŃo: 2070

    Informaš§es adicionais sobre o problema:
    BCCode: d1
    BCP1: 000000000475B6B8
    BCP2: 000000000000000A
    BCP3: 0000000000000000
    BCP4: FFFFF8800101E9C5
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Ficheiros que ajudam a descrever o problema:
    C:\Windows\Minidump\020215-20966-01.dmp
    C:\Users\Nuno Freire\AppData\Local\Temp\WER-41293-0.sysdata.xml


    Please let me know what can i do to stop this to happen.

    Thanks all.

    Nuno

    Links for the files:

    https://www.dropbox.com/s/zguc2dr7k8...66-01.dmp?dl=0
    https://www.dropbox.com/s/x1ozk0crtj...sdata.xml?dl=0
    Last edited by chopsuey78; 02-02-2015 at 04:46 AM.

  2. #2
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,173
    Points
    1307

    Default

    Hello,

    Can you run this for us;

    Download WhoCrashed
    This program checks for any drivers which may have been causing your computer to crash....

    Click on the file you just downloaded and run it.

    • Put a tick in Accept then click on Next.
    • Put a tick in the Don't create a start menu folder then click Next.
    • Put a tick in Create a Desktop Icon.
    • then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish.
    • Click Analyze
    • It will want to download the Debugger and install it Say Yes

    WhoCrashed will create report but you have to scroll down to see it.
    Copy and paste it into your next reply.

    Thanks
    Joe

  3. #3
    Member
    Join Date
    Feb 2015
    Posts
    4
    Points
    0

    Default

    Hi Joe,

    I will do what you say and will reply you as soon as possible.

    Thanks
    Nuno

  4. #4
    Member
    Join Date
    Feb 2015
    Posts
    4
    Points
    0

    Default

    Hi Joe

    Here it 's the report. I copy all...

    computer name: NUNO
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    Hardware: ASUSTeK Computer INC., P5QL
    CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 4294041600 total




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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Mon 02-02-2015 09:17:21 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020215-20966-01.dmp
    This was probably caused by the following module: atapi.sys (0xFFFFF8800101E9C5)
    Bugcheck code: 0xD1 (0x475B6B8, 0xA, 0x0, 0xFFFFF8800101E9C5)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atapi.sys
    product: Microsoft« Windows« Operating System
    company: Microsoft Corporation
    description: ATAPI IDE Miniport Driver
    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 Mon 02-02-2015 09:17:21 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: atapi.sys (atapi+0x29C5)
    Bugcheck code: 0xD1 (0x475B6B8, 0xA, 0x0, 0xFFFFF8800101E9C5)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atapi.sys
    product: Microsoft« Windows« Operating System
    company: Microsoft Corporation
    description: ATAPI IDE Miniport Driver
    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 Thu 29-01-2015 09:07:44 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012915-20202-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x731C0)
    Bugcheck code: 0x50 (0xFFFFFFFF830ECA1A, 0x1, 0xFFFFF80002C094F6, 0x5)
    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 Tue 13-01-2015 16:17:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011315-17300-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xCE2E7)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600012E2E7, 0xFFFFF8800AC46F60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32k.sys
    product: Sistema operativo Microsoft« Windows«
    company: Microsoft Corporation
    description: Controlador Win32 para vßrios utilizadores
    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 01-12-2014 11:50:47 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120114-20436-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002CBA167)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    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 Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 19-11-2014 09:56:27 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111914-30264-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
    Bugcheck code: 0x50 (0xFFFFF8802A772C50, 0x0, 0xFFFFF80002F95EBC, 0x2)
    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 10-10-2014 09:23:00 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101014-20982-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F742EC2)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF8800F742EC2)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 340.52
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 340.52
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation).
    Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Tue 22-07-2014 08:03:31 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\072214-17752-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
    Bugcheck code: 0x50 (0xFFFFFA7FAAB0BE8C, 0x0, 0xFFFFF80002F96D3F, 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 07-07-2014 08:12:41 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\070714-20092-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x9F7C, 0x9F7E00013EE8)
    Error: MEMORY_MANAGEMENT
    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 a severe memory management error occurred.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 27-06-2014 07:19:57 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062714-20264-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
    Bugcheck code: 0x1 (0x7739062A, 0x0, 0xFFFF, 0xFFFFF8800A862C60)
    Error: APC_INDEX_MISMATCH
    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 there has been a mismatch in the APC state index.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    12 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

  5. #5
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,173
    Points
    1307

    Default

    Hello,

    You have had numerous blue screen errors, I'm not an Analyst and you may need one. I'll suggest you open a topic in the forum below.

    Sysnative Forums

    They can provide better assistance and in a much quicker manner that I can. Please link to this thread so they can see what you have posted so far as they will be interested in the dump files.

    Thanks
    Joe

  6. #6
    Member
    Join Date
    Feb 2015
    Posts
    4
    Points
    0

    Default

    Hi Joe

    I will do that. Thanks for your help.

    Regards
    Nuno

  7. #7
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,173
    Points
    1307

    Default

    Looks like you're getting the help you need.

    Joe