BSOD - Multiple types, almost always just after login

dantheman999 · 18 Jul 2011

Hi everyone,

I've been having this problem for quite some time now. On most start ups (I'd probably go with 75%) I'll get a bluescreen somewhere between 10 seconds - 1 minute of signing into the computer. However once it breaks past this barrier it usually runs perfectly fine (including stressful tasks such as gaming).

Now I've had a brief look myself at the dump files and the one common thing between the lot is that ntoskrnl.exe is always there. I've had a brief look and a lot of people have suggested either a memory issue or hard drive issue but I'm not too sure. Just to be safe I've already run Memtest over night and it reported no issues and I've found no issues with ehtier hard drive I have doing chkdsk but whether that is useful or not remains to be seen. I thought it was unlikely to be either of those just due to how specific it was at only crashing just after logging in but some of you may know a lot better than me.

Right so other than that, basic system info.

Windows Home Preimum 64 bit - Full retail. Original installed OS.

Hardware has mixed age (It's a custom system).
OS Installation is probably only a month or two old. My old OS got a bit slow and I felt a full clean was necessary.

As for actual Specs:
CPU - AMD 1090T
Motherboard - MSI 70A-G54
4 gig RAM.
Graphics card - Nvidia 460 GTX SE
No Sound card
Screen - Samsung SyncMaster T200
HD - WDC - 1TB (OS installed on this one) and WDC 0.5TB.

If there is anything else you need, I'll be happy to give more info.

And as per instructions attached are the files needed.

Thanks in advanced to any help!

Jonathan_King · 18 Jul 2011

Hello,

Try testing your RAM with Memtest86 immediately upon booting up for the first time in the morning. Run it for about 10 minutes or so, anything above that is overkill in this situation.

...Summary of the dumps:

Code:


Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun Jun  5 12:13:57.628 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:57.595
Probably caused by : ntkrnlmp.exe ( nt!AlpcpSectionDeleteProcedure+5b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  avguard.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!AlpcpSectionDeleteProcedure+5b
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  8 12:36:44.388 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:11.354
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt!CcFlushCache+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!CcFlushCache+103
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 03:01:55.176 2011 (UTC - 4:00)
System Uptime: 0 days 14:10:45.002
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 12:45:21.017 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:23.204
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  drvinst.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 12:41:22.918 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:40.744
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1de
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 10 02:46:39.933 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:33.119
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul  3 22:32:34.793 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:57.979
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+114 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 25 10:51:32.179 2011 (UTC - 4:00)
System Uptime: 0 days 5:44:27.005
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 25 04:14:14.137 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:07.963
Probably caused by : win32k.sys ( win32k!ValidateHwnd+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!ValidateHwnd+7a
BiosReleaseDate = 05/18/2010
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

dantheman999 · 18 Jul 2011

Jonathan_King said:

Hello,

Try testing your RAM with Memtest86 immediately upon booting up for the first time in the morning. Run it for about 10 minutes or so, anything above that is overkill in this situation.

Cheers, I'll try that, not even thought of doing it.