BSOD caused by ntoskrn.exe

[s2kroma]

So I'm having a problem with my laptop, i'm getting BSOD using it normally to navigate in the internet. https://puu.sh/zoBmo/4e303b3055.jpg this is the BSOD I get from it. The model of the laptop is an Asus X44C. What i did until now is, I formatted it, installed all drivers and updated it, and in the next day using chrome I got the bluescreen, so I started to look for a way to fix, I did a memory test and had no errors, did an HDD test with Hdtune and had no badblocks, did a test with Western digital software to check HDD too and no errors, I utilized Prime95 to check if was a temperature issue and it didn't pass 80°C. So I tried whocrashed and thats what it says about the error. https://puu.sh/zoBja/bb15a13d74.png
It's weird for me that it says to be a thermal issue, since with prime95 was everyting okay, can anyone help me? I don't know more what to do :S

 

[Colif]

Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

Who crashed is great at showing what crashed but not why. I used to recommend it but its really a waste of time in most cases.

Its useful for one thing though, can you go to c:\windows\minidump folder
copy the minidump files to documents
Upload the copies from Documents to a file sharing site ands show a Link here, I will get someone to read them for usi and get closer to the truth... as its not what it blames.

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause. If NTOSKRNL crashes, windows has no choice but to follow. Its the brains of the outfit.


Try this as well as some BSOD are just windows and not hardware
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

 

[s2kroma]

Thank you for answer me!, i'm currently trying the powershell method, and here's the minidump files. I uploaded it to Google drive. https://drive.google.com/open?id=1fc4ylsBZjDUlpQ1BNfxv7YRoEzRzLNLh

 

[s2kroma]

Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

Who crashed is great at showing what crashed but not why. I used to recommend it but its really a waste of time in most cases.

Its useful for one thing though, can you go to c:\windows\minidump folder
copy the minidump files to documents
Upload the copies from Documents to a file sharing site ands show a Link here, I will get someone to read them for usi and get closer to the truth... as its not what it blames.

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause. If NTOSKRNL crashes, windows has no choice but to follow. Its the brains of the outfit.


Try this as well as some BSOD are just windows and not hardware
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Thank you for answer me!, i'm currently trying the powershell method, and here's the minidump files. I uploaded it to Google drive. https://drive.google.com/open?id=1fc4ylsBZjDUlpQ1BNfxv7YRoEzRzLNLh

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/eouV.html

File: 021418-26847-01.dmp (Feb 14 2018 - 11:02:31)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: ntkrnlmp.exe (Process: wininit.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 02 Sec(s)

File: 021418-26754-01.dmp (Feb 13 2018 - 22:03:29)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: hardware_disk (Process: csrss.exe)
Uptime: 0 Day(s), 10 Hour(s), 46 Min(s), and 04 Sec(s)

File: 021418-25178-01.dmp (Feb 14 2018 - 10:42:51)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: hardware_disk (Process: csrss.exe)
Uptime: 0 Day(s), 2 Hour(s), 35 Min(s), and 28 Sec(s)

Motherboard: https://www.asus.com/br/Laptops/X44C/HelpDesk_Download/
There appears to be a BIOS update for your system, however, I'm an English only speaker so I can't verify what I'm seeing. You have BIOS v1.0. I think the latest version is BIOS 2.10.

I can't help you with this. Wait for additional replies. Good luck.

 

[s2kroma]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/eouV.html

File: 021418-26847-01.dmp (Feb 14 2018 - 11:02:31)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: ntkrnlmp.exe (Process: wininit.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 02 Sec(s)

File: 021418-26754-01.dmp (Feb 13 2018 - 22:03:29)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: hardware_disk (Process: csrss.exe)
Uptime: 0 Day(s), 10 Hour(s), 46 Min(s), and 04 Sec(s)

File: 021418-25178-01.dmp (Feb 14 2018 - 10:42:51)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: hardware_disk (Process: csrss.exe)
Uptime: 0 Day(s), 2 Hour(s), 35 Min(s), and 28 Sec(s)

Motherboard: https://www.asus.com/br/Laptops/X44C/HelpDesk_Download/
There appears to be a BIOS update for your system, however, I'm an English only speaker so I can't verify what I'm seeing. You have BIOS v1.0. I think the latest version is BIOS 2.10.

I can't help you with this. Wait for additional replies. Good luck.

Thanks for reply, now that i've seen your comment and theres 2 errors cause by a hardware disk, I took a look in Hdtune again at health section and it had those errors. https://puu.sh/zp8to/c3ddd1f3dc.jpg but I read about them and people say that I can't really trust Hdtune in that section, so I kind ignored it, since in the error scan showed nothing, and with the western digital tool neither. Yea it does seems to have an update for the Bios, do you think it could solve my problem? also on the bios for the Sata configuration has 2 options IDE and AHCI, didn't try to change it, would differ in something? thank you again

 

[Colif]

csrss.exe = the client for your user.

Winit.exe

(Windows Initialize) was made by Microsoft and is core system process that originated in Windows XP, since it has been passed down to both Windows 7 and Vista. The file was created to allow uninstallers to run and process commands stored in the file WinInit.ini. This allows programs to take action while the computer is still booting up. In Windows 7 and Vista, it primarily acts as a launcher for the majority of the background applications that are always running.

well, I can see how Windows isn't getting anywhere. It can't start or do anything without either of the processes that are crashing.

2 of the errors blame the hdd, and that hdtune warning perhaps shouldn't be ignored - why did you run WD software? IS drive made by them?

this is advice based on just 31, not 191 -

Backup this drive as soon as you can.
Learn how your backup software restore process works.
Watch that number and the number of uncorrectable errors.
- Reallocated sectors are sectors that failed and the drive was able to recover the data and move it to a new sector
- Uncorrectables are failed sectors that the drive was not able to recover the data
- Pending Sector count is the number of sectors that the drive has flagged for testing but hasn't tested yet.

31 is alot IMO. I would be replacing it already but its ok just to be ready to do so (ie- recent backup readily available) and then do so if the numbers increases. Everytime you add new software or update, run a new backup so that when you do replace the drive you have an easy restore process.

BTW - important files should always have a backup copy (or two) stored on other devices.

http://www.tomshardware.com/answers/id-3411038/reallocated-event-count-warning.html

note: some hdd makers start their count at 200 and work down, so the actual count might be 9 uncorrected, not 191. Once I know what make drive is, I can work from there.

 

[s2kroma]

csrss.exe = the client for your user.

Winit.exe

(Windows Initialize) was made by Microsoft and is core system process that originated in Windows XP, since it has been passed down to both Windows 7 and Vista. The file was created to allow uninstallers to run and process commands stored in the file WinInit.ini. This allows programs to take action while the computer is still booting up. In Windows 7 and Vista, it primarily acts as a launcher for the majority of the background applications that are always running.

well, I can see how Windows isn't getting anywhere. It can't start or do anything without either of the processes that are crashing.

2 of the errors blame the hdd, and that hdtune warning perhaps shouldn't be ignored - why did you run WD software? IS drive made by them?

this is advice based on just 31, not 191 -

Backup this drive as soon as you can.
Learn how your backup software restore process works.
Watch that number and the number of uncorrectable errors.
- Reallocated sectors are sectors that failed and the drive was able to recover the data and move it to a new sector
- Uncorrectables are failed sectors that the drive was not able to recover the data
- Pending Sector count is the number of sectors that the drive has flagged for testing but hasn't tested yet.

31 is alot IMO. I would be replacing it already but its ok just to be ready to do so (ie- recent backup readily available) and then do so if the numbers increases. Everytime you add new software or update, run a new backup so that when you do replace the drive you have an easy restore process.

BTW - important files should always have a backup copy (or two) stored on other devices.

http://www.tomshardware.com/answers/id-3411038/reallocated-event-count-warning.html

note: some hdd makers start their count at 200 and work down, so the actual count might be 9 uncorrected, not 191. Once I know what make drive is, I can work from there.

Yes it is a drive made by them, It has a Western Digital 320gb seems to be the blue model, I tested with hdtune and started to look for answers about those errors I found, and after reading a lot, there were several people saying that hdtune wasn't that trustable with the health tab, so I was trying other softwares and with the western digital software it got passed with no errors, so I don't really know... So since I wasn't sure i was looking for something else to blame

 

[Colif]

WD drives start at 200 in the 1st two columns so the values there aren't the concern, you better off looking at raw scores instead of the current column, the 9 raw on reallocated event count might show good or bad attempts at fixing sectors, its hard to tell.

Reallocation Event Count S.M.A.R.T. parameter indicates a count of remap operations (transferring data from a bad sector to a special reserved disk area - spare area).

The raw value of this attribute shows the total number of attempts to transfer data from reallocated sectors to a spare area. Unsuccessful attempts are counted as well as successful. Since this is a count value, it can only increase.

https://kb.acronis.com/content/9132

I looked at the wrong colours, yellow grabbed my eyes amd I didn't see that the raw in Reallocated sector count was at 162 in the raw column and above the threshold of 140, the max lvl being 181 before the drive has no fresh sectors to swap out for retired sectors.

Try running crystaldisk info as well for more ppoints of view.

I would think about backing up anyway, always safer then.

Can you show screen shots of the WD results? did you run the long and short tests?

 

[s2kroma]

WD drives start at 200 in the 1st two columns so the values there aren't the concern, you better off looking at raw scores instead of the current column, the 9 raw on reallocated event count might show good or bad attempts at fixing sectors, its hard to tell.

Reallocation Event Count S.M.A.R.T. parameter indicates a count of remap operations (transferring data from a bad sector to a special reserved disk area - spare area).

The raw value of this attribute shows the total number of attempts to transfer data from reallocated sectors to a spare area. Unsuccessful attempts are counted as well as successful. Since this is a count value, it can only increase.

https://kb.acronis.com/content/9132

I looked at the wrong colours, yellow grabbed my eyes amd I didn't see that the raw in Reallocated sector count was at 162 in the raw column and above the threshold of 140, the max lvl being 181 before the drive has no fresh sectors to swap out for retired sectors.

Try running crystaldisk info as well for more ppoints of view.

I would think about backing up anyway, always safer then.

Can you show screen shots of the WD results? did you run the long and short tests?

Did a runk with crystaldisk info and it showed this http://puu.sh/zqnHv/f164117c17.png, the status on the WD program showed this http://puu.sh/zqnJs/30b46f89cc.png, both long and short test got passed. I think it really is the HD, Is the only thing that showed any problem so...

 

[Colif]

Buy new hdd and backup anything you can't afford to lose. Its not like they are that expensive and 320gb isn't very big anymore.

Shame raw is in hex but its still showing as a caution

WD test does seem to show its okay. though it doesn't show the raw scores so it might have higher threshold before it starts to warn you

 

[s2kroma]

Buy new hdd and backup anything you can't afford to lose. Its not like they are that expensive and 320gb isn't very big anymore.

Shame raw is in hex but its still showing as a caution

WD test does seem to show its okay. though it doesn't show the raw scores so it might have higher threshold before it starts to warn you

Thank you for everything !