Blue screen after cleaning computer

HI !

Yesterday I opened my computer and cleaned the inside because it was full of dust.
After I started it I have gotten a Blue Screen Error quite alot (every 15-30 mins)
This is not the first time I've cleaned the inside of this computer and have cleaned a few others too but nothing like that ever happend.

I have also tried reinstalling windows and formatting everything but it still happens (a little less often though)

Any advice is appreciated. THX :)
 
See if there are any minidump files in the C:\windows\minidump folder. Minidump files have a .dmp extension. Select all the .dmp files, and right-click sending these files to a compressed(zipped)folder. Upload that folder as a file here
 
The files were to big.

This is what I could get:


[FONT=Courier New]Crash dump file: C:\Windows\Minidump\MEMORY.DMP[/FONT]
[FONT=Courier New]Date/time: 27.1.2013 20:25:38 GMT[/FONT]
[FONT=Courier New]Uptime: 01:10:24[/FONT]
[FONT=Courier New]Machine: [/FONT]
[FONT=Courier New]Bug check name: KMODE_EXCEPTION_NOT_HANDLED[/FONT]
[FONT=Courier New]Bug check code: 0x1E[/FONT]
[FONT=Courier New]Bug check parm 1: 0x0[/FONT]
[FONT=Courier New]Bug check parm 2: 0x0[/FONT]
[FONT=Courier New]Bug check parm 3: 0x0[/FONT]
[FONT=Courier New]Bug check parm 4: 0x0[/FONT]
[FONT=Courier New]Probably caused by: ataport.sys[/FONT]
[FONT=Courier New]Driver description: ATAPI Driver Extension[/FONT]
[FONT=Courier New]Driver product: Microsoft® Windows® Operating System[/FONT]
[FONT=Courier New]Driver company: Microsoft Corporation[/FONT]
[FONT=Courier New]OS build: Built by: 7600.17118.amd64fre.win7_gdr.120830-0334[/FONT]
[FONT=Courier New]Architecture: x64 (64 bit)[/FONT]
[FONT=Courier New]CPU count: 2[/FONT]
[FONT=Courier New]Page size: 4096[/FONT]

[FONT=Courier New]Bug check description:[/FONT]
[FONT=Courier New]This indicates that a kernel-mode program generated an exception which the error handler did not catch.[/FONT]

[FONT=Courier New]Comments:[/FONT]
[FONT=Courier New]This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. [/FONT]
[FONT=Courier New]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 which cannot be identified at this time. [/FONT]

[FONT=Courier New]--------------------------------------------------------------------------------------------------[/FONT]

[FONT=Courier New]Crash dump file: C:\Windows\Minidump\012713-40281-01.dmp[/FONT]
[FONT=Courier New]Date/time: 27.1.2013 20:25:38 GMT[/FONT]
[FONT=Courier New]Uptime: 01:10:24[/FONT]
[FONT=Courier New]Machine: [/FONT]
[FONT=Courier New]Bug check name: KMODE_EXCEPTION_NOT_HANDLED[/FONT]
[FONT=Courier New]Bug check code: 0x1E[/FONT]
[FONT=Courier New]Bug check parm 1: 0x0[/FONT]
[FONT=Courier New]Bug check parm 2: 0x0[/FONT]
[FONT=Courier New]Bug check parm 3: 0x0[/FONT]
[FONT=Courier New]Bug check parm 4: 0x0[/FONT]
[FONT=Courier New]Probably caused by: ntoskrnl.exe[/FONT]
[FONT=Courier New]Driver description: NT Kernel & System[/FONT]
[FONT=Courier New]Driver product: Microsoft® Windows® Operating System[/FONT]
[FONT=Courier New]Driver company: Microsoft Corporation[/FONT]
[FONT=Courier New]OS build: Built by: 7600.17118.amd64fre.win7_gdr.120830-0334[/FONT]
[FONT=Courier New]Architecture: x64 (64 bit)[/FONT]
[FONT=Courier New]CPU count: 2[/FONT]
[FONT=Courier New]Page size: 4096[/FONT]

[FONT=Courier New]Bug check description:[/FONT]
[FONT=Courier New]This indicates that a kernel-mode program generated an exception which the error handler did not catch.[/FONT]

[FONT=Courier New]Comments:[/FONT]
[FONT=Courier New]This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. [/FONT]
[FONT=Courier New]The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. [/FONT]

[FONT=Courier New]--------------------------------------------------------------------------------------------------[/FONT]

[FONT=Courier New]Crash dump file: C:\Windows\Minidump\012713-39640-01.dmp[/FONT]
[FONT=Courier New]Date/time: 27.1.2013 12:14:07 GMT[/FONT]
[FONT=Courier New]Uptime: 00:51:05[/FONT]
[FONT=Courier New]Machine: [/FONT]
[FONT=Courier New]Bug check name: VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
[FONT=Courier New]Bug check code: 0x119[/FONT]
[FONT=Courier New]Bug check parm 1: 0x1[/FONT]
[FONT=Courier New]Bug check parm 2: 0xFF0000[/FONT]
[FONT=Courier New]Bug check parm 3: 0x0[/FONT]
[FONT=Courier New]Bug check parm 4: 0x0[/FONT]
[FONT=Courier New]Probably caused by: watchdog.sys[/FONT]
[FONT=Courier New]Driver description: Watchdog Driver[/FONT]
[FONT=Courier New]Driver product: Microsoft® Windows® Operating System[/FONT]
[FONT=Courier New]Driver company: Microsoft Corporation[/FONT]
[FONT=Courier New]OS build: Built by: 7600.17118.amd64fre.win7_gdr.120830-0334[/FONT]
[FONT=Courier New]Architecture: x64 (64 bit)[/FONT]
[FONT=Courier New]CPU count: 2[/FONT]
[FONT=Courier New]Page size: 4096[/FONT]

[FONT=Courier New]Bug check description:[/FONT]
[FONT=Courier New]This indicates that the video scheduler has detected a fatal violation.[/FONT]

[FONT=Courier New]Comments:[/FONT]

[FONT=Courier New]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 which cannot be identified at this time. [/FONT]

[FONT=Courier New]--------------------------------------------------------------------------------------------------[/FONT]

[FONT=Courier New]Crash dump file: C:\Windows\memory.dmp[/FONT]
[FONT=Courier New]Date/time: 27.1.2013 12:14:07 GMT[/FONT]
[FONT=Courier New]Uptime: 00:51:05[/FONT]
[FONT=Courier New]Machine: [/FONT]
[FONT=Courier New]Bug check name: VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
[FONT=Courier New]Bug check code: 0x119[/FONT]
[FONT=Courier New]Bug check parm 1: 0x1[/FONT]
[FONT=Courier New]Bug check parm 2: 0xFF0000[/FONT]
[FONT=Courier New]Bug check parm 3: 0x0[/FONT]
[FONT=Courier New]Bug check parm 4: 0x0[/FONT]
[FONT=Courier New]Probably caused by: atikmpag.sys[/FONT]
[FONT=Courier New]Driver description: AMD multi-vendor Miniport Driver[/FONT]
[FONT=Courier New]Driver product: AMD driver[/FONT]
[FONT=Courier New]Driver company: Advanced Micro Devices, Inc.[/FONT]
[FONT=Courier New]OS build: Built by: 7600.17118.amd64fre.win7_gdr.120830-0334[/FONT]
[FONT=Courier New]Architecture: x64 (64 bit)[/FONT]
[FONT=Courier New]CPU count: 2[/FONT]
[FONT=Courier New]Page size: 4096[/FONT]

[FONT=Courier New]Bug check description:[/FONT]
[FONT=Courier New]This indicates that the video scheduler has detected a fatal violation.[/FONT]

[FONT=Courier New]Comments:[/FONT]

[FONT=Courier New]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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.). [/FONT]

--------------------------------------------------------------------------------------------------------------------------------------------------------

I have read that the last one is probably connected to GPU and that the fans might not be spinning correctly. That is unusual since I cleaned the interior inclunding fans but anyway I opened the computer again and checked if the fans are spinning OK. It seems that they are.

The thing is that I don't get the BSOD at all now but what happens is that my screen freezes like this:

http://shrani.si/f/1Z/GQ/1N5FZVeN/vpgktd.jpg (not the actual picture but it's similar)

I have lowered the GPU clock setting on my AMD Overdrive and for now I don't have any problems. I don't really use this computer for any video games but I don't want it crashing when I'm working with some other programs or just browsing the internet.

Jojo :)
 
Yes. I even reinstalled it but it didn't fix the problem. It happens often if im running multiple programs, but it's ok for now since I lowered gpu. I don't know how come that started appearing now after I cleaned it
 
Another 1 just happend

[FONT=Courier New]Crash dump file: C:\Windows\Minidump\012813-23875-01.dmp
Date/time: 28.1.2013 10:42:22 GMT
Uptime: 00:05:29
Machine:
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF80002EC47A5
Bug check parm 3: 0xFFFFF8800A15E890
Bug check parm 4: 0x0
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
Architecture: x64 (64 bit)
CPU count: 2
Page size: 4096

Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Comments:
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 which cannot be identified at this time.
[/FONT]
 
Have you thought about replacing the GPU? The last BSOD shows just general Windows instability or a corrupt hard drive
 
Back