BSOD problem is getting out of hand.

[ben4933]

Hi i recently bought a new pc and for the first week it was great. But recently i have been getting a load of blue screens. Im talking once every 10 minutes. I have tried to sort out the problem for a fair few days with no help, unfortunatly nothing has helped. So i have come here in search on an answer any help would be very helpfull as im pulling my hair out

windows 7 home premium x64
yes the original operating system that the computer came with.
oem = pre installed version.
the computer is about 3 weeks old.
i have re installed the operating system with a backup disk i had created, no luck the blue screens only apeared more.


i will upload the dump files i have got when the computer blue screens
thanks and i hope someone may be able to help me.

 

[ben4933]

i would love an answer please im pulling my hair out

 

[yowanvista]

Dumps blame Windows Defender

Turn it off and run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BugCheck A, {90, 2, 0, fffff80002c92995}

Probably caused by : msrpc.sys ( msrpc!LRPC_CASSOCIATION::OpenSecurityContext+118 )

 

[ben4933]

thanks for your reply, however it is still hapening

any other advice please!?

 

[ben4933]

no other help?
it seemed when i went to ntoskrnl.exe hit back prev versions, there wer about 50 different versions, i decided to pick the earliest one. i believe something is causing ntoskrnl to play up. also i hit sfc /scannow and it recognised it as a corrupt version and fixed it. This has solved most of the blue screens, it has only blue screened once today. heres the latest one i got before

 

[yowanvista]

This new dump blames your ATI display drivers, atikmdag.sys

- Boot into safe mode with networking
- Uninstall the ATI drivers including Catalyst Control Center
- Use driver sweeper to remove leftover ATI display driver files Guru3D - Driver Sweeper
- Install the latest drivers ATI Radeon
- Reboot into normal mode

BugCheck 3B, {c0000005, fffff880046ae817, fffff880053db900, 0}

Probably caused by : atikmdag.sys ( atikmdag+90817 )