Ocassionally BSODs... driver problem?

Faboulous

Reputable
Nov 15, 2015
11
0
4,510
Hello,

I have a notebook (Asus g551jm) and i get bsods now and then. I never shut down my notebook, only close the lid and let it sleep, sometimes when I return i notice it's restarted because of a bsod, but it can happen also when I'm doing something (gaming, or even browsing on chrome).
It's caused by ntoskrnl.exe, but different messages everytime(IRQL NOT LESS OR EQUAL, DRIVER POWER STATE FAILURE for example) I know these are caused by wrong drivers or something like that, but how could I find which drivers and what driver version should I install. I had one a serius driver fault, got bsods everyday, That was because of graphic card driver. I updated it to the latest, that was the problem, since I have a notebook it doesn't support the newer ones. Since then I use only that Asus recommend but I still encounter some of these as you see.
Do you have any advice what could I do in this matter? If you need more details I'll provide.
Thank you!
 
Solution
The second error tells you to check ram so run this: http://www.memtest86.com/

try running driver booster and see what drivers it finds as upgrades.

Colif

Win 11 Master
Moderator
download and run this: http://www.resplendence.com/whocrashed
it looks at the error logs and will tell us more information on them
it sometimes tells us driver names but often just blames Windows

Copy/paste result here
Also, can you do option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then this step under it Have Windows Create a Small Memory Dump (Minidump) on BSOD

this will create a file in c/windows/minidump
copy that file to your documents and then upload that copy to a cloud server and share a link here

someone who can read the logs will look at them and tell us more, if we can't work it out from the who crashed report.
 

Faboulous

Reputable
Nov 15, 2015
11
0
4,510
Slyverine!
Thanks for the support, but those are the ones I'm using.

Colif!
Thank you for your response.
I have done the dump file settings (in fact it was done by default).
I downloaded Whocrashed, also I use bluescreenview. I'm gonna share all the information about 3 different errors.

Whocrashed:

On Sun 2016. 06. 12. 22:04:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061316-11156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00039056060, 0xFFFFD0015ABFA990, 0xFFFFE0003E384850)
Error: DRIVER_POWER_STATE_FAILURE
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 2016. 06. 11. 7:28:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061116-10109-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xAF5, 0x207A53A21B0, 0xFFFFD00028C71000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 2016. 06. 06. 18:11:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060616-8218-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsCopyReadA+0x217)
Bugcheck code: 0xA (0xFFFF8E5686D2347D, 0x2, 0x1, 0xFFFFF802DBA2E0AF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® operációs rendszer
company: Microsoft Corporation
description: NT fájlrendszer-illesztő
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 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.


Bluescreenview + dump:

Dump files and the report in an excel file are uploaded in the link below.

https://drive.google.com/open?id=0B8QSbmm37S8aMWprUy0zQ2Jhd3M

Thanks for your further help.