Blue screen after cleaning computer

[Trikotnik]

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

 

[Tmagic650]

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

 

[Trikotnik]

The files were to big.

This is what I could get:


Crash dump file: C:\Windows\Minidump\MEMORY.DMP
Date/time: 27.1.2013 20:25:38 GMT
Uptime: 01:10:24
Machine:
Bug check name: KMODE_EXCEPTION_NOT_HANDLED
Bug check code: 0x1E
Bug check parm 1: 0x0
Bug check parm 2: 0x0
Bug check parm 3: 0x0
Bug check parm 4: 0x0
Probably caused by: ataport.sys
Driver description: ATAPI Driver Extension
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 a kernel-mode program generated an exception which the error handler did not catch.

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 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.

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

Crash dump file: C:\Windows\Minidump\012713-40281-01.dmp
Date/time: 27.1.2013 20:25:38 GMT
Uptime: 01:10:24
Machine:
Bug check name: KMODE_EXCEPTION_NOT_HANDLED
Bug check code: 0x1E
Bug check parm 1: 0x0
Bug check parm 2: 0x0
Bug check parm 3: 0x0
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 a kernel-mode program generated an exception which the error handler did not catch.

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.

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

Crash dump file: C:\Windows\Minidump\012713-39640-01.dmp
Date/time: 27.1.2013 12:14:07 GMT
Uptime: 00:51:05
Machine:
Bug check name: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check code: 0x119
Bug check parm 1: 0x1
Bug check parm 2: 0xFF0000
Bug check parm 3: 0x0
Bug check parm 4: 0x0
Probably caused by: watchdog.sys
Driver description: Watchdog Driver
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 the video scheduler has detected a fatal violation.

Comments:

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.

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

Crash dump file: C:\Windows\memory.dmp
Date/time: 27.1.2013 12:14:07 GMT
Uptime: 00:51:05
Machine:
Bug check name: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check code: 0x119
Bug check parm 1: 0x1
Bug check parm 2: 0xFF0000
Bug check parm 3: 0x0
Bug check parm 4: 0x0
Probably caused by: atikmpag.sys
Driver description: AMD multi-vendor Miniport Driver
Driver product: AMD driver
Driver company: Advanced Micro Devices, Inc.
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 the video scheduler has detected a fatal violation.

Comments:

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.).

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

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

 

[Tmagic650]

Yes GPU, do you have the latest AMD/ATI driver installed?

 

[Trikotnik]

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

 

[Trikotnik]

Another 1 just happend

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.

 

[Tmagic650]

Have you thought about replacing the GPU? The last BSOD shows just general Windows instability or a corrupt hard drive