Blue screen of death while playing!

[apostrophejj]

This morning I played for 2 hours without incident, but then, 3 times since the afternoon, the game crashes and a blue screen of death jumps at me! I thought it happened only in build mode, but it also happened during a shootout.
What is going on?

Windows 7 64
AMD Phenom II x4 955 processor 3.20 ghz, 4gb
NVIDIA Gforce GTX 1060 6gb

Windows tells me of the last crash that it's a 6.1.7601.2.1.0.256.1 error
WhoCrashed say it ocurred in the NTFS file system; advised to runCHKDSK, I did, and it shows nothing's wrong.
This video card is one year old, and it's the first time it crashed like this. It's true I've mostly played game from 2014 and back... but FO4 ran smoothly up until the crashes =(
please help, i'm crazy to keep on playing.

[Nite69]

the hardrive windows is installed on is failing maybe?

Blue Screens are ussually a hardware issue, if it was game related it would only be crash to desktop

[Spec_Ops_Ape]

Nirsoft's bluscreen viewer will read the mini dump files generated by Windows, google the exception code and file/driver/program that is listed.
If your machine only has 4GB RAM then Windows will be using your page file HARD.

[apostrophejj]

Originally posted by Spec_Ops_Ape:

Nirsoft's bluscreen viewer will read the mini dump files generated by Windows, google the exception code and file/driver/program that is listed.
If your machine only has 4GB RAM then Windows will be using your page file HARD.

I don't see an exception code on BlueScreenView (Nirsoft's free software). Where is it?

what do you mean by page file HARD?

[raubrey]

What the two esteemed people above me said:

Also, because I'm lazy today:

"BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits"

These used to be mostly a software/DLL issue but often it is hardware. With a newer video card it shouldn't be a driver issue but making sure all your devices are updated wouldn't hurt.

Checking your temps would be the other easy thing to do.

[raubrey]

Originally posted by sudden death&general desolation:

Originally posted by Spec_Ops_Ape:

Nirsoft's bluscreen viewer will read the mini dump files generated by Windows, google the exception code and file/driver/program that is listed.
If your machine only has 4GB RAM then Windows will be using your page file HARD.

I don't see an exception code on BlueScreenView (Nirsoft's free software). Where is it?

what do you mean by page file HARD?

As in relying on it more than perhaps is healthy.
Since you ran Chkdsk - Memory/RAM would be the most likely culprit.

[apostrophejj]

Originally posted by raubrey:

Originally posted by sudden death&general desolation:

I don't see an exception code on BlueScreenView (Nirsoft's free software). Where is it?

what do you mean by page file HARD?

As in relying on it more than perhaps is healthy.
Since you ran Chkdsk - Memory/RAM would be the most likely culprit.

yeah, my RAM, as well as my processor are like 10 years old. thanks all.

[apostrophejj]

Originally posted by raubrey:

Originally posted by sudden death&general desolation:

I don't see an exception code on BlueScreenView (Nirsoft's free software). Where is it?

what do you mean by page file HARD?

As in relying on it more than perhaps is healthy.
Since you ran Chkdsk - Memory/RAM would be the most likely culprit.

Launching the game then quitting with Speccy on shows an increase of the Graphic card, but nothing close to 85 celsius mark.

4 of the crashes have been registered, and their logs can be read through WhoCrashed, below. It's strange; every time it's something different from the previous =/

On Sun 12/08/2018 00:56:06 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: unknown_module_0000000000000001.sys (0x0000000000000007) Bugcheck code: 0x50 (0xFFFFB8A00FBEC740, 0x0, 0xFFFFF880141C12EB, 0x7) Error: PAGE_FAULT_IN_NONPAGED_AREA 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. A third party driver was identified as the probable root cause of this system error. Google query: unknown_module_0000000000000001.sys PAGE_FAULT_IN_NONPAGED_AREA

On Sat 11/08/2018 19:32:47 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\081118-14851-01.dmp This was probably caused by the following module: ntfs.sys (0xFFFFF88001240A4D) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A962428, 0xFFFFF8800A961C80, 0xFFFFF88001240A4D) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: Sistema Operacional Microsoft® Windows® company: Microsoft Corporation description: Driver do Sistema de Arquivos NT Bug check description: This indicates a problem occurred in the NTFS file system. The crash took place in a file system 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 Sat 11/08/2018 16:29:37 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\081118-15834-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x50 (0xFFFFB8A00E7BB010, 0x0, 0xFFFFF8800441D2EB, 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 Sat 11/08/2018 15:59:09 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\081118-14742-01.dmp This was probably caused by the following module: z.sys (Unloaded_Z+0x1E) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032BA881, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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: z.sys . Google query: z.sys KMODE_EXCEPTION_NOT_HANDLED

[Spec_Ops_Ape]

How much space is spare on your c: drive?

[r.linder]

Seems like most of your BSODs are being caused by faulty/corrupt drivers.

[Spec_Ops_Ape]

Check your memory: https://technet.microsoft.com/en-us/library/ff700221.aspx
Check harddisk: https://www.hdsentinel.com/hard_disk_sentinel_trial.php download the trial