Solved BSOD Help!

[mondena]

Good Day, i've had my Vista install for about 1.5 years, it has always BSOD'd about once a month, but not enough that it bothered me. The last month, it has become much more frequent, for sure once a day. It happens while watching movies, playing games, browsing the web, and even often during a reboot, it will BSOD and then reboot again. The BSOD is on the screen for just a split second, but if i watch carefully i've seen that they have many different messages inside them.

When i get to windows, there is normally a "windows has recovered from an unexpected shutdown" window. it says:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 18
BCP1: FFFFFA800123BB50
BCP2: FFFFF880170E1C40
BCP3: 0000000000000001
BCP4: 0000000000001000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini082311-02.dmp
C:\Windows\Temp\WER-30966-0.sysdata.xml
C:\Windows\Temp\WER9F5A.tmp.version.txt

i've tried to open the .dmp file, but could not do it. so i downloaded the microsoft debugger tool, but i couldn't figure out what to do with it.

The computer hardware and vista install are the same age, they are 1.5 years old. For testing purposes, i have installed different PSU/Memory/Video Card, and this doesn't change anything. I noticed in the reliability html, that is says i have no anti-virus, that is only because i reduced startup items for testing, i'm running Avast. i think i've attached the correct files.

Any help would be greatly appreciated, if you let me know what info i need, i'd be happy to provide it.
THANKS!

 

[tom982]

Hello mondena and welcome to the forums

Our BSOD experts are away at the moment, so I'll have a go at fixing your problem until they return

Follow this tutorial to run MemTest86+, let it run for 8 passes and let me know what the results are:

Guide to using Memtest86+ - Geeks to Go Forums

Tom

 

[mondena]

Hello mondena and welcome to the forums

Our BSOD experts are away at the moment, so I'll have a go at fixing your problem until they return

Follow this tutorial to run MemTest86+, let it run for 8 passes and let me know what the results are:

Guide to using Memtest86+ - Geeks to Go Forums

Tom

Good morning Tom, thanks for your suggestion. I have already ran memtest, and my results were good (memory was the first thing i suspected).

 

[tom982]

It appears we have one of our best experts currently looking at this thread I'll hold off for now until he posts - we don't want any confusion. In the mean time, it might be a good idea to run a SFC scan:

SFC Scan

1. Open the start menu
2. In the search box, type cmd
3. Right click on cmd and select Run as administrator
4. In command prompt, type:

sfc /scannow

5. Let it run and let me know if it finds any Integrity Violations

Tom

 

[richc46]

Your reports point toward hardware. My feeling is that it may be the hard drive. Take a hard drive test and make sure that you have sufficient space left on your hard drive. If not at least 15%, uninstall some of the crap that may be on the drive. Pics take a lot of space, if any are on the drive.

Test Hard Drive www.carrona.org/hddiag.html or this test www.tacktech.com/display.cfm?ttid=287

Run in safe mode, if you still get BSODs, it hardware related.

 

[tom982]

Your reports point toward hardware. My feeling is that it may be the hard drive. Take a hard drive test and make sure that you have sufficient space left on your hard drive. If not at least 15%, uninstall some of the crap that may be on the drive. Pics take a lot of space, if any are on the drive.

Test Hard Drive www.carrona.org/hddiag.html or this test www.tacktech.com/display.cfm?ttid=287

Run in safe mode, if you still get BSODs, it hardware related.

Are you now back at home then Rich?

Tom

 

[richc46]

Got back home, yesterday. Got off the plane in NY, 5 minutes later there was an earrthquake. 5.9 on the rickter scale.

 

[Jonathan_King]

EDIT: I see I'm several posts late, but rather than deleting the post, I'm leaving it here.

I'd expect some hardware problem is causing this:

Event[255]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2011-08-23T12:18:42.892
  Event ID: 5
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: princess
  Description: 
{Registry Hive Recovered} Registry hive (file): 'SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.

Event[6408]:
  Log Name: System
  Source: volmgr
  Date: 2011-08-16T09:49:05.833
  Event ID: 49
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: princess
  Description: 
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Try running some hardware tests, namely Memtest86 and each of the three Prime95 tests.

RAM - Test with Memtest86+ - Windows 7 Forums

CPU - Stress Test with Prime95 - Windows 7 Forums

Also run SeaTools: SeaTools for Windows | Seagate

Now what is this error all about, do you know?

Event[2147]:
  Log Name: System
  Source: PlugPlayManager
  Date: 2011-08-21T20:13:58.000
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: princess
  Description: 
The device 'NVIDIA GeForce 7900 GT/GTO'  (PCI\VEN_10DE&DEV_0291&SUBSYS_C5633842&REV_A1\4&3fae61e&0&0008)  disappeared from the system without first being prepared for removal.

What was the nVidia card doing?

...Summary of the dumps:

[FONT=lucida console]
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sat Aug 20 23:05:58.193 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:16.912
*** WARNING: Unable to verify timestamp for HDAudBus.sys
*** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : HDAudBus.sys ( HDAudBus+e09bb )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_HDAudBus+e09bb
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sat Aug 20 19:27:35.469 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:20.203
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for ecache.sys
*** ERROR: Module load completed but symbols could not be loaded for ecache.sys
Probably caused by : ecache.sys ( ecache+215e8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_ecache+215e8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sat Aug 20 19:14:16.493 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:15.244
Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  RAVCpl64.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4b
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sat Aug 20 19:11:00.207 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:17.316
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for pacer.sys
*** ERROR: Module load completed but symbols could not be loaded for pacer.sys
Probably caused by : pacer.sys ( pacer+14e86 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_pacer+14e86
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Fri Aug 19 21:41:28.942 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:17.066
*** WARNING: Unable to verify timestamp for HDAudBus.sys
*** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sun Aug 14 21:01:00.252 2011 (UTC - 4:00)
System Uptime: 2 days 8:01:09.943
Probably caused by : memory_corruption ( nt!MiComputeImagePteIndex+30 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GoogleUpdate.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiComputeImagePteIndex+30
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Wed Aug 10 22:54:03.063 2011 (UTC - 4:00)
System Uptime: 2 days 13:24:43.146
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1c42e )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  opera.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+1c42e
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Tue Aug 23 13:16:10.449 2011 (UTC - 4:00)
System Uptime: 0 days 3:26:36.458
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a2b8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  SDWinSec.exe
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+2a2b8
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Tue Aug 23 06:18:49.713 2011 (UTC - 4:00)
System Uptime: 0 days 8:13:53.031
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b8
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Mon Aug 22 12:22:30.023 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:25.022
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_f_nt!KiSystemServiceExit+209
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:43:47.628 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:20.752
Probably caused by : ntkrnlmp.exe ( nt!PspGetSetContextInternal+59 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!PspGetSetContextInternal+59
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:36:54.822 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:24.556
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  autochk.exe
BUGCHECK_STR:  0x24
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:28:32.750 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:43.858
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  setup.ovr
BUGCHECK_STR:  0x24
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:26:42.988 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:12.707
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1c42e )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  spoolsv.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+1c42e
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:17:01.272 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:25.381
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Ntfs.sys ( Ntfs+111c71 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  autochk.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+111c71
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 16:09:26.400 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:23.524
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Ntfs.sys ( Ntfs+995a9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  autochk.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+995a9
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 12:36:52.236 2011 (UTC - 4:00)
System Uptime: 0 days 2:00:36.792
Probably caused by : ntkrnlmp.exe ( nt!KiTimerListExpire+663 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Crysis.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerListExpire+663
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 01:19:37.839 2011 (UTC - 4:00)
System Uptime: 0 days 0:42:53.968
Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4b
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sun Aug 21 00:35:40.023 2011 (UTC - 4:00)
System Uptime: 0 days 0:24:09.856
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Ntfs.sys ( Ntfs+26f63 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  Crysis.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+26f63
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Debug session time: Sat Aug 20 23:54:48.100 2011 (UTC - 4:00)
System Uptime: 0 days 0:47:22.199
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : portcls.sys ( portcls!CPortWaveRT::NewIrpTarget+74 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x3B_portcls!CPortWaveRT::NewIrpTarget+74
BiosReleaseDate = 01/27/2010
SystemProductName = EP45-UD3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[mondena]

thank you all very much for your help, i greatly appreciate it. i was actually gone the last (almost) 2 days in the hospital as my wife gave birth to our 2nd child!

so, life is pretty good right now, despite this computer's problems.

i will start working through your lists of suggestions. some of them i have already done. for my hard drive, i had used sea tools, and both drives passed the short test and S.M.A.R.T test. i'm currently running the long test on the system drive. i have at least 15% available space on all partitions.

i have run memtest86+, it passes no problems.

i've been running prime 95, generally prime has been causing crashes after about 3-5 hours on the large FFT test (which has made me think either cpu or motherboard).

the reason the 7900gt nvidia drivers were there is because i'd been testing various parts trying to get it to run stable. so i had a Radeaon 4870 in first (system seemed to crash the most with it in), than i tried a couple older cards i had around, first the 7900gt (which was clearly dying), so i replaced it and put in a Radeon 1650pro. i always uninstalled old drivers before removing the card and putting a new one in, but i didn't use driver cleaner or similar programs, so there might have been some residue from that. my goal is once the system is stable again, to put the 4870 back in (provided it is healthy).

once sea tools is done, i will run the sfc scan. i have not tried running in safe mode for any longer length of time, so i can try that as well. since i'm already running sea tools, is it worth it to run the other hard drive checking programs that were mentioned?

*edit* i should mention this is my wife's computer, hence the name, "princess"...

 

[Jonathan_King]

Congratulations to you and your wife! I hope all went well...

What is the PSU in your rig? Do you know the brand and model?

In my experience, hard drive diagnostics are fairly accurate. If SeaTools (or just about any program for that matter) passes a drive, I don't usually recommend a second test. I'd consider your drive to be healthy for the sake of diagnostics.

In contrast to HD Diagnostics, RAM and CPU/Motherboards are a bit quirky. Between Prime95 and Memtest86, most bad RAM is flagged, but yet some RAM problems go undetected. Typically, these are caused by mismatches in speeds/brands/latencies between the sticks, but not always. Sometimes a defective stick gets the green mark.

Try removing all but one stick of RAM, and just watch system stability. If you get another crash, replace it with just one other stick. If it still crashes, I'd say RAM is not the most likely culprit here.

 

[mondena]

my PSU is a PC Power & Cooling, 610w.

my HD did pass the long test in Seatools.

i'm already on an extra set of ram, and they pass memtest, so i don't think it is the memory. i had to re-install windows, as after all these crashes it would no longer boot into windows. so at the same time i put in an older s775 cpu for testing, which is now underway...

so far, it is working, but for some reason when i try to use Intel burn test, i get a weird error that says, "the application has failed to start because its side-by-side configuration is incorrect."

 

[richc46]

Side by side configuration requires more than the skills that I have. Here is an example of an exchange in that area.
http://www.vistax64.com/general-discussion/283887-side-side-configuration.html

 

[Jonathan_King]

I'm not sure about that Intel program error either, I'll be honest. Try using Prime95 instead though: CPU - Stress Test with Prime95 - Windows 7 Forums

 

[mondena]

Well, after re-installing windows, i've run prime 95 small FFT for 8 hours, and i've let crysis run on it overnight, no crashes. This is with the original q9400/4870/original OCZ 520w PSU.

so maybe my problem was just some random vista problem?

i just installed vista on a random HD i had lying around, so i'm going to image it, and put it back on the original HD (hopefully i'll get to that tonight) and hopefully everything is now fixed...?!?!

 

[Jonathan_King]

I don't believe in "Random Vista Problems". Granted, there's always that small chance that a bug in Windows is causing the problem, but we typically rule that out as the cause and assume that either software or hardware is the problem.

I'm just wondering if the CPU change did the trick. Thoughts on this?

 

[mondena]

I was thinking it was the CPU at first. I had a Q9400 in it. However, now i don't believe that it was the problem because of 2 reasons. First, i put the Q9400 in a different computer, and in that computer it ran Prime 95 for 8 hours, no problem. And now, with the Q9400 back in this computer, it also seems to be working perfect (after the new copy of windows was installed). So, now i don't think it was the CPU.

Tonight, i will try to get this new windows onto my old hard drive i was using, at that point the system will be entirely back to its original specs, just with a new copy of Vista. i'm curious to see if it will cause any crashes then...

 

[mondena]

I don't believe in "Random Vista Problems".

well, it looks like you were right. i did not manage to get my old HD back in, but with the new HD, and the new copy of windows, i left the system to run the intro video of UT (not a very intensive task anymore, i know, just trying to give it something to do) overnight. Event viewer shows that at 6:49.02 the system experienced an unexpected shutdown. There were 3 error boxes on the screen, the "windows has experienced an unexpected shutdown box," a 2nd box that said something like "an error with windows shadow copy" and i don't remember the 3rd box. i used the snipping tool to take an image, but i was planning to run the BSOD file collection app before i posted, however, i got a IRQ BSOD before i saved the snip. so thats the 2nd blue screen this morning.

how can a system run prime 95 for 8 hours, and run crysis all night, and than the next night not make it with the original UT intro video, and than just simply crash in windows?!? Very frustrating...

i've attached the file collection app/reliability index.

 

[mondena]

i also ran the sfc scanner, and it said that windows resource protection found corrupt files but was unable to fix some of them. the file system repair changes will take effect after the next reboot.

i've attached the cbs.log file.

 

[mondena]

i started to run the intro to UT again, this time after about 5 mins, it crashed to desktop, there were 3 errors on the screen, including one that said "windows will restart in 1 minute," and another that started with, "the instruction at 0xff0c41c2 reference memory at..." and thats all i wrote down before it reset.

 

[Jonathan_King]

Did the system BSOD at all while the s775 was installed? If not, you might stick it back in for several days just to confirm; based on that we might forever absolve or definitively blame the Q9400. While Prime95 and the other stress tests are good for a lot of testing, their results are not 100% guaranteed.