BSODs galore

[jmack]

Hey Stoneys,
Looks like power management was a big factor in the problems. Long story short, I found solid timings, multipliers and voltages for the CPU and RAM and any BSOD's during normal operation vanished (i.e. web browsing, excel, and general OS exploration).

Then I went back to tackling the GTX 285 issue. It turns out the Nvidia drivers don't do well when the card is set to 'adaptive power management.' I made a simiple preference switch to how the card demands power and so far no BSOD's with a dozen hours or so of gaming.

I'm going to remove Avast and put Norton back on and -knock on wood- that should be a wrap.

Thanks for your support and encouragement as I've muddled through this.

 

[stoneys-nutz]

Glad you are on your way to solid gaming. I will keep my fingers crossed.
Hope all goes well and have a merry Christmas.

 

[jmack]

Sadly, more BSOD's. These appear entirely random, usually occuring while browsing or when the system is idle on the desktop. I've updated the minidump list. This includes all dumps since my reinstall.

I still have not heard back from the memory manufacturer after a couple of follow-ups regarding specific timings for this board. I'm still running what my motherboard manufacturer consideres my best options.

Cheers,
Jason

 

[usasma]

Not much info on the memory dumps. The most common error is in fileinfo.sys - a Microsoft file system filter driver.

Because of the fileinfo.sys errors and the presence of NTFS.SYS in the stack text of one of the memory dumps - I'd start by suspecting issues with your hard drive.

So, please try these 2 things and let us know what the results are:
1 - a free hard drive diagnostic: HD Diagnostic
2 - CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

Here's a summary of the memory dump analysis':

Debug session time: Sat Nov 28 14:54:13.275 2009 (GMT-5)
System Uptime: 0 days 0:12:52.084
BugCheck A, {8, c, 0, fffff80001ea2ee1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sat Nov 28 15:46:01.555 2009 (GMT-5)
System Uptime: 0 days 0:32:11.353
BugCheck C2, {7, 110b, bc1f000a, fffff8800137f970}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLogForNL+1f7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Debug session time: Tue Dec  1 22:07:46.381 2009 (GMT-5)
System Uptime: 0 days 0:05:36.287
BugCheck A, {ffffffffffffff86, 2, 0, fffff80001ec0809}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Wed Dec  2 10:52:18.230 2009 (GMT-5)
System Uptime: 0 days 0:00:48.980
BugCheck 18, {fffffa8005aef080, fffffa800a735a40, 1, 20000}
Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceClose+48 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  steam.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sun Dec  6 11:48:52.181 2009 (GMT-5)
System Uptime: 0 days 0:17:56.957
BugCheck 1A, {5001, fffff70001080000, 94, f4fffdfffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+154ff )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Mon Dec  7 10:44:50.569 2009 (GMT-5)
System Uptime: 0 days 0:10:20.335
BugCheck 40, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+dfa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[jmack]

Hello again usamsa,
Thanks for the guidance and support. I ran the seagate disk checking tool and it passed with no errors. I also ran a chkdsk with the results pasted below (found under wininit in the source column).

Cheers,
Jason

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
270848 file records processed. 1386 large file records processed. 0 bad file records processed. 0 EA records processed. 88 reparse records processed. 367868 index entries processed. 0 unindexed files processed. 270848 security descriptors processed. Cleaning up 9401 unused index entries from index $SII of file 0x9.
Cleaning up 9401 unused index entries from index $SDH of file 0x9.
Cleaning up 9401 unused security descriptors.
CHKDSK is compacting the security descriptor stream...
48511 data files processed. CHKDSK is verifying Usn Journal...
35700552 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
270832 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
70106920 free clusters processed. Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
488384511 KB total disk space.
207426360 KB in 206988 files.
138764 KB in 48514 indexes.
0 KB in bad sectors.
391707 KB in use by the system.
65536 KB occupied by the log file.
280427680 KB available on disk.
4096 bytes in each allocation unit.
122096127 total allocation units on disk.
70106920 allocation units available on disk.
Internal Info:
00 22 04 00 18 e6 03 00 3d 60 07 00 00 00 00 00 ."......=`......
d0 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00 ....X...........
30 c7 c6 77 00 00 00 00 50 23 fa ff 00 00 00 00 0..w....P#......
Windows has finished checking your disk.
Please wait while your computer restarts.

 

[usasma]

The physical hard drive is presumed to be OK since it passed the test.
The file system on the hard drive was damaged (CHKDSK reported that it fixed it).

I'd wait for the next BSOD, then run CHKDSK /R to see if the disk has errors again.
The alternatives then become:
- attempt to find out what's corrupting the file system (not real easy to do)
- wipe the hard drive clean and then reinstall windows (this will help to eliminate software causes)
- replace the hard drive (if all else fails)