B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 5, 2014 #1 I keep getting freezes during certain games - NFS Rivals, Assassin's Creed IV: Black Flag, Borderlands 2 etc. The screen just freezes and the sound continues to play in the background - I am not able to Alt+Tab or even open up Task Manager to shut down the game. I have to hard-reboot the computer and upon rebooting, there is no error code. However, during Borderlands 2, I got a freeze with a bugcheck code of 0x119. I then turned on Driver Verifier and got several crashes - all the crashes with Driver Verifier showed a bugcheck code of 0xD6 DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION. They all pointed to the nvlddmkm.sys driver as the faulty driver. I am on the latest Beta drivers - 331.93. I've tried reinstalling the GPU drivers several times to no avail - even tried the WHQL (331.82) drivers but still get the freezing during games. I've attached the dumps here so can someone please help me fix this? I'm really struggling to find out the cause of these crashes/freezes! The strange thing is, I can run benchmarks all day and even played BF4 for about 1.5 hours without any issue - so it really seems like some sort of software conflict (?). Attachments BSOD_0xD6.zip 782.5 KB · Views: 4
I keep getting freezes during certain games - NFS Rivals, Assassin's Creed IV: Black Flag, Borderlands 2 etc. The screen just freezes and the sound continues to play in the background - I am not able to Alt+Tab or even open up Task Manager to shut down the game. I have to hard-reboot the computer and upon rebooting, there is no error code. However, during Borderlands 2, I got a freeze with a bugcheck code of 0x119. I then turned on Driver Verifier and got several crashes - all the crashes with Driver Verifier showed a bugcheck code of 0xD6 DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION. They all pointed to the nvlddmkm.sys driver as the faulty driver. I am on the latest Beta drivers - 331.93. I've tried reinstalling the GPU drivers several times to no avail - even tried the WHQL (331.82) drivers but still get the freezing during games. I've attached the dumps here so can someone please help me fix this? I'm really struggling to find out the cause of these crashes/freezes! The strange thing is, I can run benchmarks all day and even played BF4 for about 1.5 hours without any issue - so it really seems like some sort of software conflict (?).
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 5, 2014 #2 Hi, All of the attached DMP files are of the DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6) bug check. This indicates the driver accessed memory beyond the end of its pool allocation. Essentially, what happened here was there was a driver that allocated N bytes of memory (random #) and then went ahead and referenced way more than that original #. This bug check occurs when you have the Special Pool option enabled with Driver Verifier, which we can confirm: 2: kd> !verifier Verify Level 1aaedbf ... enabled options are: Special pool Special irql Inject random low-resource API failures All pool allocations checked on unload Io subsystem checking enabled Deadlock detection enabled DMA checking enabled Security checks enabled IRP Logging Miscellaneous checks enabled Click to expand... Also with -- DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP ...and - FAILURE_BUCKET_ID: X64_0xD6_VRF_nvlddmkm+50e48d We can also see from the FBID string that nvlddmkm.sys (nVidia video driver) was the driver that caused the bug check. Aside from the beta and the latest, have you tried a few versions behind? If so, there's likely a conflict going on here which we'll need a bit of detective work to find. Code: HWiNFO64A.SYS - Fri Nov 22 10:45:10 2013 ^^ HWiNFO32 Kernel Driver. I am very curious as to if HWiNFO is causing conflicts with its diagnostics, so let's go ahead and remove it for temporary troubleshooting purposes. Regards, Patrick
Hi, All of the attached DMP files are of the DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6) bug check. This indicates the driver accessed memory beyond the end of its pool allocation. Essentially, what happened here was there was a driver that allocated N bytes of memory (random #) and then went ahead and referenced way more than that original #. This bug check occurs when you have the Special Pool option enabled with Driver Verifier, which we can confirm: 2: kd> !verifier Verify Level 1aaedbf ... enabled options are: Special pool Special irql Inject random low-resource API failures All pool allocations checked on unload Io subsystem checking enabled Deadlock detection enabled DMA checking enabled Security checks enabled IRP Logging Miscellaneous checks enabled Click to expand... Also with -- DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP ...and - FAILURE_BUCKET_ID: X64_0xD6_VRF_nvlddmkm+50e48d We can also see from the FBID string that nvlddmkm.sys (nVidia video driver) was the driver that caused the bug check. Aside from the beta and the latest, have you tried a few versions behind? If so, there's likely a conflict going on here which we'll need a bit of detective work to find. Code: HWiNFO64A.SYS - Fri Nov 22 10:45:10 2013 ^^ HWiNFO32 Kernel Driver. I am very curious as to if HWiNFO is causing conflicts with its diagnostics, so let's go ahead and remove it for temporary troubleshooting purposes. Regards, Patrick
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 5, 2014 #3 Hi Patrick, Thanks for the response. I have not tried a driver earlier than 331.82 because many of the games I play seem to require the latest ones (even the beta) since I'm running 4-Way SLI. How do I remove the HWiNFO64A.SYS driver? I do NOT have HW-Info (diagnostic program) installed on my system so I'm not sure how that file is there? Should I also disable the "Special Pool" option you mentioned? If so, how do I do that?
Hi Patrick, Thanks for the response. I have not tried a driver earlier than 331.82 because many of the games I play seem to require the latest ones (even the beta) since I'm running 4-Way SLI. How do I remove the HWiNFO64A.SYS driver? I do NOT have HW-Info (diagnostic program) installed on my system so I'm not sure how that file is there? Should I also disable the "Special Pool" option you mentioned? If so, how do I do that?
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 5, 2014 #4 Running 4-way SLI may be part of the problem as that's quite a # of GPU's and when you start running that many, you're very prone to bugs due to the sheer number of processing needed, and possibly even 1 of the 4 being faulty. Have you tried an earlier version and not playing any of the games that require that driver just to test? Have you also tried one GPU at a time without SLI? How do I remove the HWiNFO64A.SYS driver? I do NOT have HW-Info (diagnostic program) installed on my system so I'm not sure how that file is there? Click to expand... We can make a Restore Point and rename the driver to stop it from loading - Restore Point - Create in Windows 8 Afterwards, navigate to C:\Windows\System32\Drivers find and rename HWiNFO64A.sys to HWiNFO64A.old Restart. ---------- Should I also disable the "Special Pool" option you mentioned? If so, how do I do that? Click to expand... No, but more specifically, let's change something with verifier. Disable it, and let's re-enable it. However, this time, check every 3rd party driver as you're supposed to, EXCEPT nvlddmkm.sys (leave it un-checked). I'd like to see if verifier catches anything else within 24-48 hours of system use. Regards, Patrick
Running 4-way SLI may be part of the problem as that's quite a # of GPU's and when you start running that many, you're very prone to bugs due to the sheer number of processing needed, and possibly even 1 of the 4 being faulty. Have you tried an earlier version and not playing any of the games that require that driver just to test? Have you also tried one GPU at a time without SLI? How do I remove the HWiNFO64A.SYS driver? I do NOT have HW-Info (diagnostic program) installed on my system so I'm not sure how that file is there? Click to expand... We can make a Restore Point and rename the driver to stop it from loading - Restore Point - Create in Windows 8 Afterwards, navigate to C:\Windows\System32\Drivers find and rename HWiNFO64A.sys to HWiNFO64A.old Restart. ---------- Should I also disable the "Special Pool" option you mentioned? If so, how do I do that? Click to expand... No, but more specifically, let's change something with verifier. Disable it, and let's re-enable it. However, this time, check every 3rd party driver as you're supposed to, EXCEPT nvlddmkm.sys (leave it un-checked). I'd like to see if verifier catches anything else within 24-48 hours of system use. Regards, Patrick
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 5, 2014 #5 Patrick said: Running 4-way SLI may be part of the problem as that's quite a # of GPU's and when you start running that many, you're very prone to bugs due to the sheer number of processing needed, and possibly even 1 of the 4 being faulty. Have you tried an earlier version and not playing any of the games that require that driver just to test? Have you also tried one GPU at a time without SLI? Click to expand... I have tested the GPUs individually and they all seem to work fine. I've run several benchmarks (3DMark 11/13, Heaven 4.0/Valley) and they all work great. Only certain games seem to freeze. We can make a Restore Point and rename the driver to stop it from loading - Restore Point - Create in Windows 8 Afterwards, navigate to C:\Windows\System32\Drivers find and rename HWiNFO64A.sys to HWiNFO64A.old Restart. Click to expand... Okay, I went ahead and did that. No, but more specifically, let's change something with verifier. Disable it, and let's re-enable it. However, this time, check every 3rd party driver as you're supposed to, EXCEPT nvlddmkm.sys (leave it un-checked). I'd like to see if verifier catches anything else within 24-48 hours of system use. Click to expand... I did that as well. The only thing was that I wasn't sure which options to select in that list of things to test (Special Pool etc.). I selected all of them except "Force Pending I/O Requests" and "Systematic Low Resources Simulation". I read somewhere not to select those. I then went ahead and selected all non-Microsoft drivers EXCEPT nvlddmkm.sys as you suggested and rebooted. I've been using the system for about 15 minutes so far and no crashes yet.
Patrick said: Running 4-way SLI may be part of the problem as that's quite a # of GPU's and when you start running that many, you're very prone to bugs due to the sheer number of processing needed, and possibly even 1 of the 4 being faulty. Have you tried an earlier version and not playing any of the games that require that driver just to test? Have you also tried one GPU at a time without SLI? Click to expand... I have tested the GPUs individually and they all seem to work fine. I've run several benchmarks (3DMark 11/13, Heaven 4.0/Valley) and they all work great. Only certain games seem to freeze. We can make a Restore Point and rename the driver to stop it from loading - Restore Point - Create in Windows 8 Afterwards, navigate to C:\Windows\System32\Drivers find and rename HWiNFO64A.sys to HWiNFO64A.old Restart. Click to expand... Okay, I went ahead and did that. No, but more specifically, let's change something with verifier. Disable it, and let's re-enable it. However, this time, check every 3rd party driver as you're supposed to, EXCEPT nvlddmkm.sys (leave it un-checked). I'd like to see if verifier catches anything else within 24-48 hours of system use. Click to expand... I did that as well. The only thing was that I wasn't sure which options to select in that list of things to test (Special Pool etc.). I selected all of them except "Force Pending I/O Requests" and "Systematic Low Resources Simulation". I read somewhere not to select those. I then went ahead and selected all non-Microsoft drivers EXCEPT nvlddmkm.sys as you suggested and rebooted. I've been using the system for about 15 minutes so far and no crashes yet.
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 6, 2014 #6 I just had a BSOD - 0x3B which pointed to a lvrs64.sys driver. This refers to the Logitech Webcam Software - I have the Logitech C910 webcam and installed the webcam software a few weeks ago. What should I do? Still keep running Driver Verifier or reset it like before and deselect this lvrs64.sys driver?
I just had a BSOD - 0x3B which pointed to a lvrs64.sys driver. This refers to the Logitech Webcam Software - I have the Logitech C910 webcam and installed the webcam software a few weeks ago. What should I do? Still keep running Driver Verifier or reset it like before and deselect this lvrs64.sys driver?
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 6, 2014 #7 Go ahead and uninstall that software for troubleshooting purposes and keep verifier enabled. I don't think I've ever seen DV flag drivers that weren't a problem, but I've never seen LWS cause issues either (I use it). Regards, Patrick
Go ahead and uninstall that software for troubleshooting purposes and keep verifier enabled. I don't think I've ever seen DV flag drivers that weren't a problem, but I've never seen LWS cause issues either (I use it). Regards, Patrick
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Jan 6, 2014 #8 Hi. . . Driver Verifier flagged it and will likely do so again. I agree with Patrick - uninstall it - Code: lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC) lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8) http://sysnative.com/drivers/driver.php?id=lvrs64.sys http://sysnative.com/drivers/driver.php?id=lvuvc64.sys Unfortunately, Realtek only has (the above) drivers for Windows 8 -- no driver updates for Windows 8.1 - http://www.logitech.com/en-us/support/hd-pro-webcam-c910?crid=405§ion=downloads&osid=23&bit=64 http://www.logitech.com/en-us/support/hd-pro-webcam-c910?osid=14&bit=64&crid=405 You're not the only one with Windows 8.1 + C910 webcam experiencing BSODs - http://forums.logitech.com/t5/Video...andled-BSOD/m-p/1149165/highlight/true#M15474 I don't know what the PM mentioned in post #2 by Vanessa1031 was about. Is drive i: an SSD ? Code: ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 159.4 GB Total Space: 217.0 GB File System: NTFS Model: Intel Raid 0 Volume Drive: E: Free Space: 1896.0 GB Total Space: 1907.7 GB File System: NTFS Model: WDC WD2002FAEX-007BA0 Drive: F: Free Space: 346.4 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: G: Free Space: 723.7 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: I: Free Space: 801.1 GB Total Space: 975.8 GB File System: NTFS Model: ATA OCZ-VERTEX4 SCSI Disk Device Check for firmware upgrade - http://ocz.com/consumer/download/firmware Regards. . . jcgriff2
Hi. . . Driver Verifier flagged it and will likely do so again. I agree with Patrick - uninstall it - Code: lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC) lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8) http://sysnative.com/drivers/driver.php?id=lvrs64.sys http://sysnative.com/drivers/driver.php?id=lvuvc64.sys Unfortunately, Realtek only has (the above) drivers for Windows 8 -- no driver updates for Windows 8.1 - http://www.logitech.com/en-us/support/hd-pro-webcam-c910?crid=405§ion=downloads&osid=23&bit=64 http://www.logitech.com/en-us/support/hd-pro-webcam-c910?osid=14&bit=64&crid=405 You're not the only one with Windows 8.1 + C910 webcam experiencing BSODs - http://forums.logitech.com/t5/Video...andled-BSOD/m-p/1149165/highlight/true#M15474 I don't know what the PM mentioned in post #2 by Vanessa1031 was about. Is drive i: an SSD ? Code: ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 159.4 GB Total Space: 217.0 GB File System: NTFS Model: Intel Raid 0 Volume Drive: E: Free Space: 1896.0 GB Total Space: 1907.7 GB File System: NTFS Model: WDC WD2002FAEX-007BA0 Drive: F: Free Space: 346.4 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: G: Free Space: 723.7 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: I: Free Space: 801.1 GB Total Space: 975.8 GB File System: NTFS Model: ATA OCZ-VERTEX4 SCSI Disk Device Check for firmware upgrade - http://ocz.com/consumer/download/firmware Regards. . . jcgriff2
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 6, 2014 #9 Patrick said: Go ahead and uninstall that software for troubleshooting purposes and keep verifier enabled. I don't think I've ever seen DV flag drivers that weren't a problem, but I've never seen LWS cause issues either (I use it). Regards, Patrick Click to expand... I tried to uninstall it but I got an error message saying it was unable to complete the process but it asked me whether I wanted to remove the Registry entries associated with it (I use YourUninstaller 7 to remove programs). I went ahead and did that. I then went into the Program Files (x86), Program Data, Users>>AppData>>Local folders and deleted all folders associated with Logitech. Is that okay? I don't know how else I could uninstall that Logitech Webcam Software.
Patrick said: Go ahead and uninstall that software for troubleshooting purposes and keep verifier enabled. I don't think I've ever seen DV flag drivers that weren't a problem, but I've never seen LWS cause issues either (I use it). Regards, Patrick Click to expand... I tried to uninstall it but I got an error message saying it was unable to complete the process but it asked me whether I wanted to remove the Registry entries associated with it (I use YourUninstaller 7 to remove programs). I went ahead and did that. I then went into the Program Files (x86), Program Data, Users>>AppData>>Local folders and deleted all folders associated with Logitech. Is that okay? I don't know how else I could uninstall that Logitech Webcam Software.
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 6, 2014 #10 jcgriff2 said: Hi. . . Driver Verifier flagged it and will likely do so again. I agree with Patrick - uninstall it - Code: lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC) lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8) http://sysnative.com/drivers/driver.php?id=lvrs64.sys http://sysnative.com/drivers/driver.php?id=lvuvc64.sys Unfortunately, Realtek only has (the above) drivers for Windows 8 -- no driver updates for Windows 8.1 - Support + Downloads: HD Pro Webcam C910 - Logitech Support + Downloads: HD Pro Webcam C910 - Logitech You're not the only one with Windows 8.1 + C910 webcam experiencing BSODs - Webcam C910 - Lvrs64.sys System Thread Exception N... - Logitech Forums I don't know what the PM mentioned in post #2 by Vanessa1031 was about. Is drive i: an SSD ? Code: ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 159.4 GB Total Space: 217.0 GB File System: NTFS Model: Intel Raid 0 Volume Drive: E: Free Space: 1896.0 GB Total Space: 1907.7 GB File System: NTFS Model: WDC WD2002FAEX-007BA0 Drive: F: Free Space: 346.4 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: G: Free Space: 723.7 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: I: Free Space: 801.1 GB Total Space: 975.8 GB File System: NTFS Model: ATA OCZ-VERTEX4 SCSI Disk Device Check for firmware upgrade - Download OCZ Toolbox and Firmware Updates Regards. . . jcgriff2 Click to expand... Hi JCGriff2, Thanks for your response. As mentioned in my previous reply to Patrick, I removed the Logitech Webcam software - wasn't a clean uninstall but it's not on my system any more - used CCleaner to completely remove any traces of Logitech. Regarding drive "I:", yes, it is actually an 8-SSD RAID-0 array. That's the drive all my games are installed on. Regarding the firmware update, would I lose any of the info if I update the firmware on the SSDs? Do I need to break the RAID-0 array to update the firmware? I suppose I could clone the disk and save the image on an external HDD and then break the array, secure erase all 8 SSDs, update the firmware and then rebuild the array and finally re-image the drive? Would that work? Or can I just update the firmware without doing any of that?
jcgriff2 said: Hi. . . Driver Verifier flagged it and will likely do so again. I agree with Patrick - uninstall it - Code: lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC) lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8) http://sysnative.com/drivers/driver.php?id=lvrs64.sys http://sysnative.com/drivers/driver.php?id=lvuvc64.sys Unfortunately, Realtek only has (the above) drivers for Windows 8 -- no driver updates for Windows 8.1 - Support + Downloads: HD Pro Webcam C910 - Logitech Support + Downloads: HD Pro Webcam C910 - Logitech You're not the only one with Windows 8.1 + C910 webcam experiencing BSODs - Webcam C910 - Lvrs64.sys System Thread Exception N... - Logitech Forums I don't know what the PM mentioned in post #2 by Vanessa1031 was about. Is drive i: an SSD ? Code: ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 159.4 GB Total Space: 217.0 GB File System: NTFS Model: Intel Raid 0 Volume Drive: E: Free Space: 1896.0 GB Total Space: 1907.7 GB File System: NTFS Model: WDC WD2002FAEX-007BA0 Drive: F: Free Space: 346.4 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: G: Free Space: 723.7 GB Total Space: 953.9 GB File System: NTFS Model: SAMSUNG HD204UI USB Device Drive: I: Free Space: 801.1 GB Total Space: 975.8 GB File System: NTFS Model: ATA OCZ-VERTEX4 SCSI Disk Device Check for firmware upgrade - Download OCZ Toolbox and Firmware Updates Regards. . . jcgriff2 Click to expand... Hi JCGriff2, Thanks for your response. As mentioned in my previous reply to Patrick, I removed the Logitech Webcam software - wasn't a clean uninstall but it's not on my system any more - used CCleaner to completely remove any traces of Logitech. Regarding drive "I:", yes, it is actually an 8-SSD RAID-0 array. That's the drive all my games are installed on. Regarding the firmware update, would I lose any of the info if I update the firmware on the SSDs? Do I need to break the RAID-0 array to update the firmware? I suppose I could clone the disk and save the image on an external HDD and then break the array, secure erase all 8 SSDs, update the firmware and then rebuild the array and finally re-image the drive? Would that work? Or can I just update the firmware without doing any of that?
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 6, 2014 #11 I just checked the OCZ website and although they have a newer version of the OCZ Toolbox, the actual firmware for the OCZ Vertex 4 SSD shows 1.5.1. Using CrystalDiskInfo, I checked that the firmware on the Vertex 4 SSDs is 1.5 (doesn't show up as 1.5.1?). So, I wonder if I still need to update it(?). *EDIT: I opened the Toolbox and tried to "update" it, and it said I have the latest version. So I guess that's settled.
I just checked the OCZ website and although they have a newer version of the OCZ Toolbox, the actual firmware for the OCZ Vertex 4 SSD shows 1.5.1. Using CrystalDiskInfo, I checked that the firmware on the Vertex 4 SSDs is 1.5 (doesn't show up as 1.5.1?). So, I wonder if I still need to update it(?). *EDIT: I opened the Toolbox and tried to "update" it, and it said I have the latest version. So I guess that's settled.
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 6, 2014 #12 Keep us updated since removing LWS. Regards, Patrick
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 6, 2014 #13 Hi Patrick, After uninstalling the Logitech Webcam Software, there have been no crashes! How much longer should I keep Driver Verifier enabled? Should we try the DV with the nvlddmkm.sys driver enabled now? I think the freezing during certain games is due to an unstable overclock on the GPUs - I lowered it slightly and was able to play Borderlands 2 (while having DV enabled) for about 30 minutes without issue. :smile9:
Hi Patrick, After uninstalling the Logitech Webcam Software, there have been no crashes! How much longer should I keep Driver Verifier enabled? Should we try the DV with the nvlddmkm.sys driver enabled now? I think the freezing during certain games is due to an unstable overclock on the GPUs - I lowered it slightly and was able to play Borderlands 2 (while having DV enabled) for about 30 minutes without issue. :smile9:
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 6, 2014 #14 Good to hear. I think the freezing during certain games is due to an unstable overclock on the GPUs Click to expand... That will definitely do it, probably even the crashes too. If you crash again, put the clock to default. As for verifier, sure, you can tick it for nVidia. Regards, Patrick
Good to hear. I think the freezing during certain games is due to an unstable overclock on the GPUs Click to expand... That will definitely do it, probably even the crashes too. If you crash again, put the clock to default. As for verifier, sure, you can tick it for nVidia. Regards, Patrick
B BUHD Member Joined Jan 5, 2014 Posts 10 Location USA Jan 11, 2014 #15 Well I've been using the computer for a few days now without any crashes! Thank you all very much for helping me out. Back to using the rig as it was meant to be! :)
Well I've been using the computer for a few days now without any crashes! Thank you all very much for helping me out. Back to using the rig as it was meant to be! :)
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jan 11, 2014 #16 Great to hear, thanks for the update. Marked as solved. Regards, Patrick