Windows 7: BSODS, The continuing problem

Chalky Skipper · 06 Jul 2010

Hi,

I am very much in need of expertise to,hopefully, stabilise my system.

I built my own system,using Windows 7 ultimate x 64. From day one have had big troubles with BSODS. Generally they are from cold starts ( more than 1 day ). I have reinstalled OS on two occasions,and have done clean install, with new hard drive as well. Have tested with memtest86, memory passing with flying colours.Changed video card,still no joy.

Other than that my computer knowledge is extremely limited and really have no idea what I am looking at when reviewing blue screen views.

I have saved 7 bsods from Blue Screen view program and also dxdiag of my computer at Chalky's SkyDrive - Windows Live. I would appreciate it if someone could take time to have a quick look and maybe solve the problem for me.

Thank you

ttran · 07 Jul 2010

Can you please upload your minidump files to forum, here is instruction so that someone here can help you:
http://www.sevenforums.com/crash-loc...d-problem.html

Thank you

Tuan

Chalky Skipper · 07 Jul 2010

Thanks for advice.

herewith minidump files as requested

Regards Chalky

ttran · 08 Jul 2010

Hi and welcome to SF

Quote:

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

First of all, please do a disk check:
Disk Check

ntfs.sys is hard drive controller driver, it is blamed in many dmp file, please go to your manufacture website to download hard drive diagnostic tool:
HD Diagnostic

Please Uninstall ThreatFire Filesystem Monitor, it is potential cause for the BSODs you had. I saw it appear in many dmp files

There is one exception code ffffffc000005 appear in some dmp files that make me think of memory corruption. It would be best if you can download third party called memtestx86, burn it to CD using Iso recorder ISO Recorder v3 , and let it run for at least 5 passes

Finally, scan system for file check:
SFC /SCANNOW Command - System File Checker

Code:

BugCheck 1A, {41790, fffffa80014e9c80, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

Followup: MachineOwner
---------
BugCheck 50, {fffff8a002d9fdf0, 0, fffff880018a5190, 2}


Could not read faulting driver name
Probably caused by : Npfs.SYS ( Npfs!memmove+b0 )

Followup: MachineOwner
---------
BugCheck 1A, {41790, fffffa8000ec5cb0, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88008724aa8, fffff88008724310, fffff88001227cc0}

Unable to load image TfFsMon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TfFsMon.sys
*** ERROR: Module load completed but symbols could not be loaded for TfFsMon.sys
Probably caused by : Ntfs.sys ( Ntfs!memcmp+10 )

Followup: MachineOwner
---------
BugCheck 1A, {41790, fffffa80014de2b0, ffff, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff800032d2497, ffffffffffffffff, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff8000329b54c, fffff88007879d90, 0}

Probably caused by : win32k.sys ( win32k!DestroyClass+18c )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff800033bdf8c, fffff8800a68d930, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------
BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
---------
BugCheck 50, {fffff6fcd00181d0, 0, fffff800030d539e, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff96000117e4b, 0, ffffffffffffffff}

Probably caused by : win32k.sys ( win32k!xxxDestroyThreadInfo+5eb )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002f78726, fffff880031c4968, fffff880031c41d0}

Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )

Followup: MachineOwner
---------

Update your directx as well:
Download details: DirectX End-User Runtime

Let us know if you need further help

Tuan

Chalky Skipper · 11 Jul 2010

Thanks for the reply Tuan,have now done all tests,as requested.

1.. Disk check,with both options, automatically fix system errors and scan for and attempt recovery of bad sectors.No problems
2.. HD Diagnostic, passed short and long test.
3.. Memtestx86, 6 passes, nil errors.
4..SFC/Scannow-system file checker, Windows resource protection found corrupt files but was unable to fix some of the problem.
5..have updated directx.
6..Uninstall Threatfire. Only threatfire I could find was part of program,Spydoctor and anti virus. It evidently controls thing called Behaviour Guard within the program.I have disabled that part of it. I hope it isn't necessary to uninstall whole thing.

Shut computer down last night and will not restart for approx 48 hours.As previously mentioned, problem of BSODS only occur on cold start. Have been just been putting to sleep for past few days and hasn't missed a beat. Will update when I "fire" it up again.

Regards, Chalky

ttran · 11 Jul 2010

Quote:

4..SFC/Scannow-system file checker, Windows resource protection found corrupt files but was unable to fix some of the problem.

this is system file check. As you can see it found corrupt files but was unable to fix it-->it's not ok. I'm thinking about Repair Install , it will preserve your data ,account users, driver etc...

Regard,

Tuan

Chalky Skipper · 11 Jul 2010

Hi Tuan,
That was certainly quick reply. Will Repair Install as you suggest. Will then wait 48 hours, or thereabouts, to try system. Will advise accordingly.

Thanks again,

Regards, Chalky

Chalky Skipper · 12 Jul 2010

Hi Tuan,

Just attempted Repair Install. Halfway through, at the expanding files stage got the following .
The upgrade was cancelled Then following message Quote " Windows cannot install required files.The
file may be corrupt or missing. Make sure all files required for installation are available and restart the installation. Error code 0x80070570". unquote.

The plot is thickening. Will wait for your reading of this.

Regards, Chalky

Tews · 12 Jul 2010

Run chkdsk /f then try running the repair install ... hopefully you wont have to do a full reinstall..

ttran · 12 Jul 2010

I agree with Tews, please follow what he suggest. Also, where do u get the copy of window 7? retail, downloaded etc...?

Windows 7: BSODS, The continuing problem

BSODS, The continuing problem problems?