E
epycc7
Hello, Im randomly getting BSODs on my Lenovo ideapad 510-15IKB. I reinstalled windows 10 for few times, updated all drivers from lenovo support website, changed thermal paste, updated intel graphics and nvidia drivers from their website, update bios and firmware, changed hdd to ssd, checked ram with memtest and 2 other tests, checked laptop with lenovo diagnostic and nothing founded. I really dont know what other to do with this laptop. Please help me! Sorry for my bad english. My configuration: i5 7200u, Nvidia geforce 940mx, 12 gb ram(4 soldered), SSD Patriot Burst 120gb. Laptop serial number: PF0GNUZM.
Whocrashed:
On Wed 4.9.2019. 20:18:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-20968-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF805573A8FBB)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF805573A8FBB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Wed 4.9.2019. 20:18:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: storport.sys (0xFFFFF805573A8FBB)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF805573A8FBB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Wed 4.9.2019. 20:12:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-22281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x50 (0xFFFFF806CA7DE9D0, 0x10, 0xFFFFF806CA7DE9D0, 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 Wed 4.9.2019. 19:58:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-20234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8041984893A)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 4.9.2019. 14:12:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-7656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC900)
Bugcheck code: 0xA (0x2E74, 0xFF, 0x0, 0xFFFFF80039C228F0)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 4.9.2019. 11:10:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-6437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC900)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8013476E350)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...
Whocrashed:
On Wed 4.9.2019. 20:18:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-20968-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF805573A8FBB)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF805573A8FBB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Wed 4.9.2019. 20:18:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: storport.sys (0xFFFFF805573A8FBB)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF805573A8FBB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Wed 4.9.2019. 20:12:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-22281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x50 (0xFFFFF806CA7DE9D0, 0x10, 0xFFFFF806CA7DE9D0, 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 Wed 4.9.2019. 19:58:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-20234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8041984893A)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 4.9.2019. 14:12:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-7656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC900)
Bugcheck code: 0xA (0x2E74, 0xFF, 0x0, 0xFFFFF80039C228F0)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 4.9.2019. 11:10:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090419-6437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC900)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8013476E350)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...