Display driver and 2 types of BSOD nvlddmkm.sys & ntoskrnl.exe


  1. Posts : 1
    Windows 7 64-Bit
       #1

    Display driver and 2 types of BSOD nvlddmkm.sys & ntoskrnl.exe


    EDIT : Added file extension to download.

    So after 1 and a half years I've had like 7 BSOD's, and most of them were ntoskrnl.exe which I would like to know how to solve, now I get nvidia display driver kernel stopped working and has recovered, followed by a black screen then recovering.

    So what I would like to know is, how do I fix it? I have the latest nvidia drivers, tried reinstalling them, this only happened recently, and I ran memtest and my ram is fine apparently, aswell as valleybenchmark, so the BSOD's seem random.

    Here is the crash report for my old BSOD which still happens sometimes :


    crash dump file: C:\Windows\Minidump\022814-15787-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x1, 0xFFFFF80002E82DAC, 0x0)
    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.


    And here is my latest BSOD which is making gaming unplayable :

    crash dump file: C:\Windows\Minidump\032014-16458-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80003092F1F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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.




    Specs (taken from speccy)

    Operating System
    Windows 7 Professional 64-bit SP1
    CPU
    Intel Core i7 4820K @ 3.70GHz
    Ivy Bridge-E 22nm Technology
    RAM
    8.00GB Dual-Channel DDR3 @ 799MHz (11-11-11-28)
    Motherboard
    Gigabyte Technology Co., Ltd. X79-UP4 (SOCKET 0)
    Graphics
    2269W (1920x1080@60Hz)
    DELL 1504FP (1024x768@60Hz)
    3071MB NVIDIA GeForce GTX 780 (EVGA)
    Storage
    232GB ATA Samsung SSD 840 SCSI Disk Device (SSD)
    931GB ATA WDC WD10EZEX-00B SCSI Disk Device (SATA)
    Optical Drives
    HL-DT-ST BDDVDRW UH12NS30 SCSI CdRom Device
    Audio
    Razer Kraken 7.1 Chroma



    Thanks in advance!
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #2

    Hiya and welcome to SevenForums!
    Snap a picture when the BSOD occurs. Also run Magician on your SSD. Magician comes with your SSD CD:s.
      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 15:56.
Find Us