BSOD Errors

Hi, having problems with a new system I've built myself 2 months ago build went successful until started blue screening quite frequently over the holidays.

Getting different blue screens each time, tested ram with memtest found errors, RMA'd ram with the retailer. Tested system with new ram, no errors.

crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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.


Bugcheck code: 0xF7 (0x2000730C8A5, 0x24C20D31896A, 0xFFFFDB3DF2CE7695, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

This was probably caused by the following module: Unknown ()
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D13518)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

Uninstalled NEC USB3 controller driver yesterday, still getting BSOD but not as many still thinking I have drivers that are the problem.

BSODs were caused when CurseClient.exe was running, its a program from Curse Inc or from Adobe Air
Remove such program(s)

Code:

PROCESS_NAME:  CurseClient.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cf8e58 to fffff80002c89740

Removed curseclient hoping it has not left traces of itself in my system. Noticed yesterday kespersky has left traces behind anyway to remove these?

I will post back if I get new BSOD

Sav said:

Removed curseclient hoping it has not left traces of itself in my system. Noticed yesterday kespersky has left traces behind anyway to remove these?

I will post back if I get new BSOD

You can use the trial version of Revo uninstaller to remove any leftover from curesclient using the 'forced uninstalled' feature
Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Curse was uninstalled and stopped to run at startup. Checkdisk was also ran since then Windows has being stable no blue screens and being playing games without any problems