Hello!
I have an issue that has plagued me since the "birth" of this custom-DIY PC.
Issue: Whenever I play any graphically-intensive game or push its settings to near/full maximum, be it BF4, GW2, CS: GO, Tomb Raider, or TF2, eventually after playing for a while (~30 minutes - 1 hour?) I would get a BSOD. The bizarre thing is, after I restarted the PC and re-launched whatever I was playing, the BSOD would never come again until I shut down my PC and turn it on another time. The whole process then repeats itself.
This occurred since when I was still using W7 x64. I used to overclock in the past and at first, I thought it was because of that but after resetting the settings back to default, I realize it wasn't. I used to closely monitor the temps and all back when I was frantically trying to resolve this issue but now I just monitor the LED reflecting off my MSI N780 Lightning. I noticed that if I stepped down the graphical settings of my games to a point where it's barely putting much load onto my GPU, there's a decent chance that it may not crash.
Opinion: Nowadays since I have no idea what else to do, I just try not to shut down as much as possible. More often on W7 x64, the BSOD errors might specifically indicate memory-related errors according to Google and have been considering to replace my RAM. Now on W8.1, not so much. But I still believe this might be a driver issue.
Whatever I've tried:
1) Re-installed GPU drivers
2) Chkdsk
3) Updated ALL drivers (from MSI website)
4) Reformatted, re-installed ALL drivers (from MSI website)
5) Reformatted, re-installed basic drivers (from Windows Update)
6) Memtest after 2 passes, no errors
7) Reformatted, re-installed most drivers, except "bloatware"
8) Reformatted, installed W8, re-installed ALL drivers
9) Overclock RAM voltage*
My PC specifications:
Computer Type: Desktop
OS: Windows 8.1 Pro
CPU: Intel Core i5-4670k @ 3.40GHz + Corsair H100i
Motherboard: MSI Z87 MPower
Graphics Card: MSI N780 Lightning
Memory: Corsair Dominator Platinum 8GB DDR3 1600MHz (2 x 4GB)
Display: BenQ XL2420T (120hz) + XL2420TE (120hz)
Storage: Plextor M5 Pro 256GB SSD, Seagate Barracuda 3TB HDD (7200 RPM)
PSU: Seasonic X-650 650W
Case: Fractal Design Define R4
Keyboard: CM Storm Quickfire Stealth
Mouse: Razer Orochi
Headset: Plantronics GameCom 780
Antivirus: Norton 360**
*Just recently tried this out of curiosity after some search, but it was a soft OC. Didn't work anyway.
**I've seen some people said this software is buggy, but my issue occurred even before I used this. It was cheap on Amazon and didn't bothered much with the BSOD anymore because I could "work around it".
I noticed a previous user with a similar thread title did a WhoCrashed analysis, and so shall I BTW, this log I copied over coincidentally has a conclusion pointing to a particular driver (see below) but previous times I ran WhoCrashed, the conclusion identified nothing.
Attachments: View attachment 54204, View attachment 54205
I think that's about it? I hope that's enough! Have a nice day ahead.
I have an issue that has plagued me since the "birth" of this custom-DIY PC.
Issue: Whenever I play any graphically-intensive game or push its settings to near/full maximum, be it BF4, GW2, CS: GO, Tomb Raider, or TF2, eventually after playing for a while (~30 minutes - 1 hour?) I would get a BSOD. The bizarre thing is, after I restarted the PC and re-launched whatever I was playing, the BSOD would never come again until I shut down my PC and turn it on another time. The whole process then repeats itself.
This occurred since when I was still using W7 x64. I used to overclock in the past and at first, I thought it was because of that but after resetting the settings back to default, I realize it wasn't. I used to closely monitor the temps and all back when I was frantically trying to resolve this issue but now I just monitor the LED reflecting off my MSI N780 Lightning. I noticed that if I stepped down the graphical settings of my games to a point where it's barely putting much load onto my GPU, there's a decent chance that it may not crash.
Opinion: Nowadays since I have no idea what else to do, I just try not to shut down as much as possible. More often on W7 x64, the BSOD errors might specifically indicate memory-related errors according to Google and have been considering to replace my RAM. Now on W8.1, not so much. But I still believe this might be a driver issue.
Whatever I've tried:
1) Re-installed GPU drivers
2) Chkdsk
3) Updated ALL drivers (from MSI website)
4) Reformatted, re-installed ALL drivers (from MSI website)
5) Reformatted, re-installed basic drivers (from Windows Update)
6) Memtest after 2 passes, no errors
7) Reformatted, re-installed most drivers, except "bloatware"
8) Reformatted, installed W8, re-installed ALL drivers
9) Overclock RAM voltage*
My PC specifications:
Computer Type: Desktop
OS: Windows 8.1 Pro
CPU: Intel Core i5-4670k @ 3.40GHz + Corsair H100i
Motherboard: MSI Z87 MPower
Graphics Card: MSI N780 Lightning
Memory: Corsair Dominator Platinum 8GB DDR3 1600MHz (2 x 4GB)
Display: BenQ XL2420T (120hz) + XL2420TE (120hz)
Storage: Plextor M5 Pro 256GB SSD, Seagate Barracuda 3TB HDD (7200 RPM)
PSU: Seasonic X-650 650W
Case: Fractal Design Define R4
Keyboard: CM Storm Quickfire Stealth
Mouse: Razer Orochi
Headset: Plantronics GameCom 780
Antivirus: Norton 360**
*Just recently tried this out of curiosity after some search, but it was a soft OC. Didn't work anyway.
**I've seen some people said this software is buggy, but my issue occurred even before I used this. It was cheap on Amazon and didn't bothered much with the BSOD anymore because I could "work around it".
I noticed a previous user with a similar thread title did a WhoCrashed analysis, and so shall I BTW, this log I copied over coincidentally has a conclusion pointing to a particular driver (see below) but previous times I ran WhoCrashed, the conclusion identified nothing.
Code:
[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dump directory: C:\WINDOWS\Minidump[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Fri 21/11/2014 1:36:13 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\112114-6765-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x1A (0x41289, 0x1ACA6000, 0xFC31, 0x115E6409)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+MEMORY_MANAGEMENT"]MEMORY_MANAGEMENT[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Fri 21/11/2014 1:36:13 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41289, 0x1ACA6000, 0xFC31, 0x115E6409)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+MEMORY_MANAGEMENT"]MEMORY_MANAGEMENT[/URL][/COLOR][/SIZE][/FONT]
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Fri 21/11/2014 3:13:42 AM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\112114-6500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00068C878C0, 0xFFFFF800C1856960, 0xFFFFE00068E5C900)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 20/11/2014 5:48:27 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\112114-6421-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000A81A88C0, 0xFFFFD0016F39E960, 0xFFFFE000A8771BD0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 18/11/2014 5:43:00 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111914-6718-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00172B538C0, 0xFFFFF80246856960, 0xFFFFE0016F76CBD0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 17/11/2014 4:44:21 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111814-6593-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=afd.sys"]afd.sys[/URL][/COLOR][/SIZE][/FONT] (afd+0x4EBA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0002DE37060, 0xFFFFF80065C56960, 0xFFFFE0002F8D46E0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\drivers\afd.sys
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Ancillary Function Driver for WinSock
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Sun 16/11/2014 6:35:36 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111714-6484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=afd.sys"]afd.sys[/URL][/COLOR][/SIZE][/FONT] (afd+0x4EBA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001A2A83060, 0xFFFFF80066256960, 0xFFFFE001AAC38010)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\drivers\afd.sys
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Ancillary Function Driver for WinSock
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Sat 15/11/2014 4:52:47 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111614-6812-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000F32BB060, 0xFFFFD0011A27E960, 0xFFFFE000F4651010)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Sat 15/11/2014 12:35:51 AM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111514-7515-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=rzudd.sys"]rzudd.sys[/URL][/COLOR][/SIZE][/FONT] (rzudd+0x1742C)
Bugcheck code: 0xD1 (0xFFFFF801B6CD542C, 0x2, 0x8, 0xFFFFF801B6CD542C)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\drivers\rzudd.sys
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Razer%20Rzudd%20Engine"]Razer Rzudd Engine[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Razer%20Inc"]Razer Inc[/URL][/COLOR][/SIZE][/FONT]
description: Razer Rzudd Engine
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.
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: rzudd.sys (Razer Rzudd Engine, Razer Inc).
Google query: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=rzudd.sys+Razer%20Inc+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]Razer Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 13/11/2014 4:16:51 PM GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\111514-6671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0006AC3F880, 0xFFFFF8012804D960, 0xFFFFE0006C7F2BD0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_POWER_STATE_FAILURE"]DRIVER_POWER_STATE_FAILURE[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=4][B][HR][/HR]Conclusion[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000]25 crash dumps have been found and analyzed. Only 10 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:
[FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=rzudd.sys+Razer%20Inc+Razer%20Rzudd%20Engine"]rzudd.sys (Razer Rzudd Engine, Razer Inc)[/URL][/COLOR][/SIZE][/FONT]
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.[/COLOR][/SIZE][/FONT]
Attachments: View attachment 54204, View attachment 54205
I think that's about it? I hope that's enough! Have a nice day ahead.
My Computer
System One
-
- OS
- Windows 8.1 Pro
- Computer type
- PC/Desktop
- CPU
- Intel Core i5-4670k @ 4.6GHz
- Motherboard
- MSI Z87 MPower
- Memory
- Corsair Dominator Platinum 8GB DDR3 (2 x 4GB)
- Graphics Card(s)
- MSI N780 Lightning
- Monitor(s) Displays
- 2 x XL2420T/E
- Screen Resolution
- 1080p
- Hard Drives
- Plextor M5 Pro 256 GB SSD, Seagate Barracuda 3TB HDD (7200 RPM)
- PSU
- Seasonic X-650 650W
- Case
- Fractal Design Define R4
- Cooling
- Corsair H100i (CPU)
- Keyboard
- CM Storm Quickfire Stealth
- Mouse
- Razer Orochi
- Internet Speed
- Fiber 100Mbps
- Browser
- Chrome, Firefox
- Antivirus
- Norton 360
- Other Info
- Headset - Plantronics GameCom 780