Hello fanatiks.
The latest version of the display driver is buggy in some cases. It is causing some issues in your case, too. I'd suggest you to uninstall it and perform a clean install using the driver version 314.22 WHQL.
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed). - Now follow Drivers - Clean Left over Files after Uninstalling
- Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
Scan the system for possible virus infection with the following programs only.
And let us know which Antivirus you are using.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Seatool for dos: SeaTools | Seagate download.
- Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
- You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.
Let us know the results.
______________________________________________________________________________
BSOD ANALYSIS:
Code:
BugCheck 50, {ffffffffffffffb9, 1, fffff8800537ce94, 0}
Could not read faulting driver name
Probably caused by : hardware ( dxgmms1!VidSchiSendToExecutionQueueWithWait+2c )
Followup: MachineOwner
---------------------------------------------------------------
BugCheck 3B, {c0000005, fffff960002f6b87, fffff88002b9de60, 0}
Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+f )
Followup: MachineOwner
----------------------------------------------------------------
BugCheck 50, {fffff88007ce33b9, 0, fffff88001227141, 0}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+2e1 )
Followup: MachineOwner
----------------------------------------------------------------
BugCheck FC, {30fe03, 94d000003deef847, fffff80000ba2600, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+433ac )
Followup: MachineOwner
----------------------------------------------------------------
BugCheck 4E, {99, 0, 0, 0}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
-----------------------------------------------------------------
BugCheck 50, {fffff880098d5815, 1, fffff8800495120c, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+6620c )
Followup: MachineOwner
-------------------------------------------------------------------
BugCheck 1A, {5003, fffff781c0000000, 4885, 48830000810a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )
Followup: MachineOwner
---------
DV Next?
Quote