Windows 10: Different types of BSOD while playing games

Hello everyone,

This website was recommended by a forum member of Tomshardware since they weren't able to help me much there and I was told my best bet is to ask help here.

Anyway back to the topic - I desperately need your help. I have been getting several amounts of different BSOD in my new pc which I just built a week ago. The very first BSOD I got was last Thursday while I was playing DayZ Standalone, and then it followed in Dota 2. This ONLY occurs during the game at random in game time.
I think I received every stop codes including Memory_Management, Page_Fault_In_NonPaged_Area, IRQL_Not_Less_Or_Equal, System Thread Exception Not Handled, and some more that I can't remember. I did a lot of research before I posted here and I tried them but none actually worked for me, or at least prevented my pc from getting BSOD while playing games.

LIST OF THE THINGS I TRIED
Use Windows Memory Diagnostic Tool and Memtest86 and the results are all good (WMDT: No Problem Found/Memtest86: 9 Passes and 0 Errors at 12 hours testing time)
Uninstall and change my Anti-Virus from ESET Smart Security to Avast Premier
Scan my whole pc and found zero problem using Avast
Update all the drivers and updates (OS, GPU, Audio, and Network Adapter)
Use CCleaner to fix registry files
Reinstall GPU Driver after DDU via safe mode
Reset my Virtual Memory
Use SFC Scanner via CMD
Disable C-States in Bios
Set my battery in high performance and change "turn off hard disk after" to 0 minutes
Reinstall Windows 10

MY PC SPECS
CPU: AMD Ryzen 5 1600 with stock cooler
GPU: MSI GTX 1060 Gaming X 6G
MB: ASRock AB350M Pro4
PSU: CX Corsair 550M 80+ Bronze
RAM: PC4-17000 4GBX2 2133 DDR4
SSD: MX300 CT275MX300SSD1
CASE: Versa H24
MONITOR: Asus VE248HR
WIFI: TP-Link ac1200 Wireless Dual Band USB Adapter Archer T4U V1
OS: Windows 10 Education

I no longer don't know what to do and I'm running out of options. Please I really need your help and support. Anything would be greatly appreciated. I don't want to play games with fear of BSOD in any moment and crash my system over and over again.
My video game settings are all in high. I don't overclock and my bios settings are untouched except for the C-State mode (all set to default or auto). I used MSI Afterburner and HWiNFO64 to monitor my GPU and CPU temperature and they're all good.

Break.....

I know this is sudden but I must ask only for clarification, if ever this problem is not solve, do you guys perhaps think my best solution is to downgrade my operating system to either Windows 7 or Windows 8 where these errors will less likely occur, or bring it to PC technician? What are your thoughts?

:)

 

BSOD while playing games

which game, some machine details would be useful too

 

BSOD while playing games

These were all related to directX. Remove your current video driver and install the newest driver available

Completely remove the current driver and install the newest driver available. For instructions on how to do that Read all about updating drivers by my partner JMH3143 here Updating a driver.

 

The first thing I would try is to uninstall AVAST: Use this link

Code: BugCheck 1E, {ffffffffc0000005, fffff800330b20a0, 0, ffffffffffffffff} *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys *** WARNING: Unable to verify timestamp for aswSP.sys *** ERROR: Module load completed but symbols could not be loaded for aswSP.sys[/quote]

 

Hi philc43,

Thanks for the reply. As you have recommended, I downloaded and used the Avast Uninstaller Tool to remove my anti-virus. However, it's still giving me BSOD when playing games. I have attached my updated BSOD logs in the thread in case you're interested. What's your other recommendation?

Edit:

I did MemTest86 once again since I wasn't satisfied with my previous results, and the number of passes I got earlier was 18 with 0 errors. I have a strong feeling that my issues are revolving around software/driver with Windows 10 Education.

 

I also noticed you are using MSI Afterburner. This has also been known to trigger BSODs so that was going to be my next recommendation -that you uninstall it.

I also notice that the last crash did not get recorded:
Code: Event[2270]: Log Name: System Source: volmgr Date: 2017-06-08T00:00:27.177 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Rebla Description: Crash dump initialization failed![/quote] Please post up another set of files if you get more crashes.

 

Code: BugCheck 1E, {ffffffffc0000005, fffff801808e8b7f, 0, ffffffffffffffff}Probably caused by : ntkrnlmp.exe ( nt!CcMapData+3f )[/quote] BugCheck 1E, {ffffffffc0000005, fffff800330b20a0, 0, ffffffffffffffff}
Code: BugCheck 21, {0, 0, 20000534, 1f7299f0}Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+1468ff )[/quote] Code: BugCheck 21, {0, 0, 20000534, 1f7299f0} Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+1468ff )[/quote] Code: *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys*** WARNING: Unable to verify timestamp for aswSP.sys*** ERROR: Module load completed but symbols could not be loaded for aswSP.sysProbably caused by : luafv.sys ( luafv!LuafvGenerateFileName+4c )[/quote] Code: luafv.sys LUA File Virtualization Filter Driver Windows Update [/quote] Code: BugCheck 1A, {41792, ffffbabfff7f1320, 8000000000000000, 0} Probably caused by : memory_corruption ( ONE_BIT )[/quote] Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64GetContextState failed, 0x8007001E Code: The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#89900000000000006CB02AA0&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.[/quote]
Code: WUDFRd.sys Windows Driver Foundation - User-mode Driver Framework Reflector Windows Update [/quote] Code: The driver \Driver\RtlWlanu failed to load for the device USB\VID_2357&PID_0101\123456.[/quote] This above driver was not on the list updated by John Carrona
The information below seems to be the closest match.
Code: rtwlanu.sys Realtek RTLxxxxx Wireless USB 2.0 Adapter Used by different manufacturer's Realtek [/quote] Code: Crash dump initialization failed![/quote] Code: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown. The file system structures need to be scanned online.[/quote] Code: Volume C: (\Device\HarddiskVolume4) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.[/quote] Code: Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_KINGSTON&PROD_DATATRAVELER_2.0&REV_1.00#89900000000000006CB02AA0&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.[/quote] Code: A driver package which uses user-mode driver framework version 2.21.0 is being installed on device SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_KINGSTON&PROD_DATATRAVELER_2.0&REV_1.00#89900000000000006CB02AA0&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}.[/quote]
The event log reported file corruption of C drive.
Open administrative command and run chkdsk /x /f /r (it may take many hours, plan to run overnight)


When it has completed to find the results and report in the forum see this link:

chkdsk txt command: Windows 10 Forums -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

or open eventvwr, use find with 26226
How to find chkdsk results in Windows 10 - Winaero

Uninstall and reinstall any Realtek driver (rtwlanu.sys)

 

From the event logs, this is pretty worrying, it also occurred 23 times. It indicates your Crucial MX300 SSD is encountering errors and could be causing the problems you've run into.

Code: Log Name: System Source: Microsoft-Windows-EnhancedStorage-EhStorTcgDrv Date: 2017-06-04T15:20:56.972 Event ID: 10 Task: Driver Level: Error Opcode: TcgLib Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Rebla Description: A TCG Command has returned an error. Desc: AuthenticateSession Param1: 0x1 Param2: 0x60000001C Param3: 0x900000006 Param4: 0x0 Status: 0x12[/quote] The TCG (Trusted Computing Group) command is used for drive encryption.

I noticed that Crucial somewhat recently released an update to the MX300's firmware. The release notes mention they improved error handling and reliability, I would strongly recommend updating the firmware for your device, but first backup all of your data. You can update your firmware using Crucial's Storage Executive.

Also, are you running bitlocker on this computer? If so, try disabling it temporarily to see if the crashes persist.

Lastly, I see you are running an older Nvidia drivers, version 382.05, whereas the latest release is 382.33. I'd suggest updating, it will likely improve performance as well.

EDIT: I should mention, I have the same SSD as you and have upgraded the firmware on mine without issue.

 

Hi philc43,

I uninstalled MSI Afterburner along with Rivatuner and HWiNFO64, and it didn't work. Here are the BSOD reports from WhoCrashed software. And I also uploaded my latest logs in the main thread.

On Thu 6/8/2017 2:33:54 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060817-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1A (0x41792, 0xFFFF8200FA37F8F0, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (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.

On Thu 6/8/2017 2:18:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060817-6234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2B7DD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8029604A7DD, 0xFFFF8001BD9915D8, 0xFFFF8001BD990E10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread generated an exception which the error handler did not catch.
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 Tue 6/6/2017 2:16:11 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060617-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801808E8B7F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 Tue 6/6/2017 1:54:37 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060617-6359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x21 (0x0, 0x0, 0x20000534, 0x1F7299F0)
Error: QUOTA_UNDERFLOW
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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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 6/5/2017 2:14:00 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060517-7859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800330B20A0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.

Conclusion

6 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswsp.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

--------------------------------------------------------------------------------

Hello zbook and Spectrum,

Thanks for the reply. I will certainly do what you tell me. Please give me a couple of hours to report back.

 

Hi zbook,

I have done what you told me before regarding Realtek drivers and I did it again to be sure and its giving me a message of "the best driver is already installed". Here's my report for C drive.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
350208 file records processed. File verification completed.
25974 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
413462 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 870 unused index entries from index $SII of file 0x9.
Cleaning up 870 unused index entries from index $SDH of file 0x9.
Cleaning up 870 unused security descriptors.
Security descriptor verification completed.
31628 data files processed. CHKDSK is verifying Usn Journal...
40277280 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
350192 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
52551302 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

268037119 KB total disk space.
57253824 KB in 144106 files.
105800 KB in 31629 indexes.
0 KB in bad sectors.
472283 KB in use by the system.
65536 KB occupied by the log file.
210205212 KB available on disk.

4096 bytes in each allocation unit.
67009279 total allocation units on disk.
52551303 allocation units available on disk.

Internal Info:
00 58 05 00 4a ae 02 00 30 d9 04 00 00 00 00 00 .X..J...0.......
a7 00 00 00 6f 00 00 00 00 00 00 00 00 00 00 00 ....o...........

Windows has finished checking your disk.
Please wait while your computer restarts.

--------------------------------------------------------------------------------

Hi Spectrum,

My BitLocker is already off/disabled. As for my GPU driver and SSD firmware, I have downloaded and updated them both and I still get BSOD. Here's what I got.

On Thu 6/8/2017 4:50:51 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060817-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0x10CE0000, 0x2, 0x1, 0xFFFFF8002BA351B4)
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.

On Thu 6/8/2017 4:36:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060817-6328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1A (0x41793, 0xFFFFB200000152E0, 0x9, 0x8)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (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.

 

The last bsod minidump was on 6/6/2017 per the zip files. The whocrashed had found 2 more bsod on 6/8/2017. The memtest86+ was ok multiple times. The chkdsk was ok. You have uninstalled Avast. Please confirm that you are using windows defender. Have you had any more bsod since the two above in the whocrashed report?

Are you comfortable navigating through the windows recovery or advanced troubleshooting menu?
To get practice open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
Navigate through troubleshooting to startup options (not startup repair)
In startup options there will be an option to restart and after restart choose safe mode with command prompt.

To trigger bsod there is a windows program named windows driver verifer. It will create bsod and display a stop code driver verifier detected violation. Sometimes it will display a driver as *.sys. The triggered bsod will create minidumps which can be analyzed to find the misbehaving drivers.
You already have used whocrashed and can use it nicely with windows driver verifier. After each bsod you will turn windows driver verifier off using safe mode with command prompt and entering the command: verifier /reset
When you are back on the desktop run whocrashed to find the offending driver. Uninstall the misbehaving driver and restart windows driver verifier.

Send a zip file to the forum so that we can analyze it too.

To start windows driver verifier you type verifier in the left lower corner search.
In the pop up use these settings: Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Once you no longer have bsod by uninstalling drivers reinstall the most up to date drivers. Then restart windows driver verifier making sure that the new drivers do not produce bsod.

Sometimes software applications produce bsod. For example cyberlink on one of my computers no matter how many times it is reinstalled will bsod when using windows driver veriifer. Optimally it would be better to switch to another media played such as VLC.

For windows driver verifier it is recommended to run it up to 36 hours with typical computer use after all the bsod have been fixed.

One other setting change will be useful when using windows driver verifier so that you have the opportunity to view the bsod screen and view any listed misbehaving driver (*.sys)

Type system in left lower corner search to open the system control panel > left pane click on advanced system settings > system properties start up and recovery click settings > un-check automatically restart

BSOD Finding and fixing them - Microsoft Community

 

Hello zbook,

Sorry for the late reply. I was busy two days ago. In response to your questions:

Please confirm that you are using windows defender.
Yes I am using it at the moment. In fact, I just did a quick scan and it found zero threats.

Have you had any more bsod since the two above in the whocrashed report?
Not yet. I believe the 6/8/2017 BSOD are my latest (before today) crash since I haven't used my PC for two days.

Are you comfortable navigating through the windows recovery or advanced troubleshooting menu?
If you meant doing advanced command prompt troubleshooting then no, but I am willing to do anything to resolve my problem as long as specific guideline is set for me to follow.

Now as for using windows driver verifier, I followed thoroughly all the steps you have given me including the links and it gave me two similar BSOD stop code while in desktop and after doing restart. Here's my report and I also included the logs (in the main thread) and zip file link below.

On Sat 6/10/2017 11:42:35 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-4984-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt+0x13D50)
Bugcheck code: 0xC4 (0x9200F, 0xFFFFF80462278470, 0xFFFFDC88A378EEB0, 0xFFFFDC88A378EFB8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

On Sat 6/10/2017 11:34:30 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-22609-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt+0x13D50)
Bugcheck code: 0xC4 (0x9200F, 0xFFFFF804CE6F8470, 0xFFFF958A53794DB0, 0xFFFF958A53794EB8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

Zip file link: Uploadfiles.io - new-folder.rar

 

Hi MJMampen,

Please upload a new zip from the DM Log Collector.

 

Hey axe0,

Thanks for the reply. Here's the link of my new zip DM log: Uploadfiles.io - rebla-wed_06_14_2017__02320_13.zip

Before I got the DRIVER IRQL NOT LESS OR EQUAL (What failed: NTFS.sys), I just want you to know while I was using windows driver verifier ten minutes ago I had two SYSTEM THREAD EXCEPTION NOT HANDLED (What failed: nvlddmkm.sys) and one Memory Management. The reason they're not in the DM log is because for some reason Windows 10 stopped collecting info or it got stuck while in the process and I had to hold down the power button to restart. Here's some additional info from WhoCrashed.

On Wed 6/14/2017 12:01:08 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061417-4406-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x15F920)
Bugcheck code: 0xD1 (0xFFFFF8029D60F920, 0x2, 0x8, 0xFFFFF8029D60F920)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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 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.

 

About the driver verifier crashes, I can't do much with WhoCrashed report, it doesn't contain the necessary information this time to provide a proper conclusion.
The mentioned driver, verifierext.sys, is a driver from Windows. Windows drivers are never the actual cause.



Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums