BSOD While playing World of Tanks

[Brixxx]

Hi everyone

I upgraded my video card last year before Christmas with a GeForce GTX 650, in february i also changed my old hdd and added a 1TB WD Blue.

Problems started like two weeks before Easter in which i received BSOD's almost every day and i didn't knew what was the problem. On 2nd day of Easter my old 500 watt Raidmax PSU "died" while i was playing World of Warcraft, so then i thought the PSU was the problem that made BSOD's appear because it was like 4 years old and the new video card was in need of more power. This month on 4th of july i bought a Corsair CX 600 watt PSU, the computer worked normally until two days ago on 29th, in the morning i pushed the power button but only the fans and the power led were on, nothing on monitor, after on/off the pc a few times and on/off the PSU once it finally started. Today same scenario with power up, then i decied to play some World of Tanks, after first fight...like 5-10mins of playing i got BSOD and restard, tryed again and same think happened, also the computer blocked i think twice and i had to reset it and once i saw in bios at cpu temperature all kind of strange numbers.

This is what i saw in Who Crashed:

[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.

[/FONT]
[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]On Wed 7/31/2013 7:59:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-16484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]unknown_module_00000000`17011c01.sys[/FONT] (Unloaded_Unknown_Module_00000000`17011c01+0xE8FEBD49)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800333EE26, 0xFFFFF88003B786A8, 0xFFFFF88003B77F00)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
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.
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: unknown_module_00000000`17011c01.sys .
Google query: [FONT=Segoe UI, Arial]unknown_module_00000000`17011c01.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT][/FONT]
[FONT=Segoe UI, Arial]On Wed 7/31/2013 9:32:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-13875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA80FF00AF08, 0x2, 0x0, 0xFFFFF80002CCDCEB)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.



I don't know what is the problem now and i hope someone can help me, thank you.
Sorry for my bad english:huh:

[/FONT]

 

[x BlueRobot]

You appear to have a Dell OEM_SLP key on a retail ASRock motherboard, your installation is clearly counterfeit, please install and format with a genuine key.

 

[Brixxx]

Thank you for the fast answer, but are u sure its not a hardware problem ?, if u read my post i said that two days ago and today i had issues starting the computer, basically everything was "spinning" inside but nothing showed on monitor.

 

[x BlueRobot]

The problem is you have a counterfeit installation, which is against forum rules and impossible to debug since counterfeit installations are highly unpredictable, and have many security and stability problems associated with them, such as the modification of Windows files to bypass activation.