Blue screen

jewellui · 20 Jan 2011

I keep getting the blue screen, any help would be greatly appreciated.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002C99448
BCP3: FFFFF88007E13F50
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\012011-21902-01.dmp
C:\Users\Jason\AppData\Local\Temp\WER-25802-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

yowanvista · 20 Jan 2011

https://www.sevenforums.com/crashes-d...tructions.html

jewellui · 20 Jan 2011

Sorry, hopefully this is right

x64
Think OEM

Hardware and OS is about 5 months old

yowanvista · 20 Jan 2011

Do you use any Symantec/Norton products?

Update your Video drivers

- 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 (This step is important)
- Reboot into safe mode with networking
- Install the latest drivers ATI Radeon
- Reboot into normal mode

Remove any ATi Overclocking Tool

Code:

atillk64.sys        fffff880`06fea000    fffff880`06ff1000    0x00007000    0x4321d736    09/09/2005 22:40:54

jewellui · 22 Jan 2011

'The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed.' so I followed these steps in normal mode but I still have the same problem.

Jonathan_King · 22 Jan 2011

Try doing a system files check.

JK said:

Open an elevated command prompt and enter sfc /scannow.

Also, run the Kaspersky TDSS Killer tool, see if it finds anything: How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)?

Test the hard drive with SeaTools; do both the Short DST and Long DST tests.

Run Memtest overnight: RAM - Test with Memtest86+

Run the "Blend" and "Small FFTs" Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

Yowan: No Symantec products are being used.

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 20 03:13:34.475 2011 (UTC - 5:00)
System Uptime: 0 days 19:36:35.536
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 19 04:12:42.941 2011 (UTC - 5:00)
System Uptime: 0 days 0:52:16.971
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 19 03:19:47.052 2011 (UTC - 5:00)
System Uptime: 0 days 18:15:20.457
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KeStackAttachProcess+115
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan 18 09:03:44.632 2011 (UTC - 5:00)
System Uptime: 0 days 8:38:55.036
Probably caused by : ntkrnlmp.exe ( nt!KxStartSystemThread+16 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_nt!KxStartSystemThread+16
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan 18 00:24:14.114 2011 (UTC - 5:00)
System Uptime: 0 days 12:00:48.144
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  schtasks.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 17 12:22:40.715 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:18.746
Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 17 12:08:39.251 2011 (UTC - 5:00)
System Uptime: 0 days 5:36:26.339
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )
BUGCHECK_STR:  0x1E_c0000096
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_c0000096_nt!KeStackAttachProcess+1ba
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 17 05:54:40.957 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:17.987
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  lpksetup.exe
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 17 05:53:50.302 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:17.707
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  RapportService
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 17 05:52:58.974 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:13.379
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 15 00:21:32.755 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:21.785
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+4ed )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!ObpQueryNameString+4ed
SystemProductName = H55M-UD2H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

fimble · 22 Jan 2011

Partially repeating yowanvistas advice, plus...

Do not use Windows update to look after your drivers. Its known to "update" your drivers to "older" versions.
Do not have Windows update set to the Install update automatically (recommended) setting.

AODDriver.sys Mon Oct 13 05:38:55 2008
GVTDrv64.sys Tue Sep 05 08:10:02 2006 EasyTune6 Uninstall

atillk64.sys Fri Sep 09 19:40:54 2005 ATi Overclocking Tool? Uninstall

Update:

Rt64win7.sys Thu Feb 26 09:04:13 2009 Realtek LAN RTL811

RTKVHD64.sys Tue Dec 08 10:20:05 2009 Realtek HD Audio

Caution!!:

atikmdag.sys Fri Nov 26 02:46:44 2010
atikmpag.sys Fri Nov 26 02:16:47 2010

Many people are having issues with the latest Catalyst, 10.12. See this thread for issues. It may be advisable to install one of the Previous Catalyst Versions.

Be sure to run Driver Sweeper in safe mode to clear Catalyst remnants before installing your "new" Catalyst drivers.

Also be aware that Catalyst v11.1 is due for release next week ??

jewellui · 22 Jan 2011

I did a systems file check 3 times, it said that some files were corrupt.
I was going to attach the log but its above the max file size, 15mb...

Kaspersky TDSS Killer tool run

Seatools passed

Golden · 22 Jan 2011

Hi,

Sometimes running the sfc /scannow a few times over will actually be able to fix some of the problems. Its worth a go.

Regards,
Golden

jewellui · 22 Jan 2011

Thanks, everyone. This issue is fixed but it seems a new one has appeared.

I noticed my msn crashes, also when I try to open a word file that I downloaded from firefox it crashes instantly. Although clicking them from the start menu loads fine?