sudden BSOD twice or three times daily

[James7679]

my gpu is set up to run higher during gaming modes only, the crashes dont usually occur during gaming. when you say memory problems what do you mean? i know that when the blu screen comes up it gives some kind of memory error

 

[zigzag3143]

my gpu is set up to run higher during gaming modes only, the crashes dont usually occur during gaming. when you say memory problems what do you mean? i know that when the blu screen comes up it gives some kind of memory error

James it doesn't have to show you an error. butin the dumps one comman thing is memory corruption.

Are these blue screens new? or did they always happen? if new have you changed anything (memory, gpu, HD, etc)? Ill be back with the rest of them shortly

In the mean time you might want to download memtestx86 and start running some short memory tests. to be truely valid you need to run it overnight at least.

en

 

[zigzag3143]

James

Are you running a RAID???

 

[zigzag3143]

James

this is an example of the kind of results I have been getting. I checked to see if any of the Guru's with BSOD's are on becasue they have been doing this longer.

this one was probably caused by fltmgr.sys but the memory is to corrupted for me to make much of. I did notice that you are running 7100 which you should update.


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\101509-30890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e96e90
Debug session time: Thu Oct 15 12:23:18.658 2009 (GMT-4)
System Uptime: 0 days 3:23:42.439
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a01747f620, fffff8a01747f620, fa800836a1e004c0}

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

Followup: Pool_corruption
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a01747f620, the pool entry being checked.
Arg3: fffff8a01747f620, the read back flink freelist value (should be the same as 2).
Arg4: fa800836a1e004c0, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR: 0x19_3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: FlashUtil10b.e

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002dfd49c to fffff80002cdbf80

STACK_TEXT:
fffff880`0a6dadf8 fffff800`02dfd49c : 00000000`00000019 00000000`00000003 fffff8a0`1747f620 fffff8a0`1747f620 : nt!KeBugCheckEx
fffff880`0a6dae00 fffff800`02dfc6c6 : 00000000`081a3000 fffff8a0`02c4cd90 fffff880`0a6db1c0 fffffa80`0a9b4010 : nt!ExDeferredFreePool+0xc6c
fffff880`0a6dae90 fffff880`013123f0 : fffffa80`07cca180 fffff880`0a6db160 fffff8a0`6366744e fffff880`0a6db068 : nt!ExFreePoolWithTag+0x406
fffff880`0a6daf40 fffff880`0130591c : fffffa80`08100d10 fffff8a0`061477a0 fffff8a0`06147670 fffffa80`07cca180 : Ntfs!NtfsCommonClose+0x520
fffff880`0a6db010 fffff880`0118027f : fffff880`0a6db501 fffffa80`081a3010 00000000`00000200 fffffa80`00000002 : Ntfs!NtfsFsdClose+0x2dc
fffff880`0a6db110 fffff880`0117e6df : fffffa80`0941d2b0 fffffa80`081a3010 fffffa80`081a3000 fffffa80`081a3010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0a6db1a0 fffff800`02fb16ae : fffffa80`0809a070 fffffa80`07cb73a0 fffffa80`06d22b30 fffffa80`0941d2b0 : fltmgr!FltpDispatch+0xcf
fffff880`0a6db200 fffff800`02cd15b4 : fffffa80`083608a0 fffffa80`0836d370 fffffa80`06d334b0 fffffa80`06d334b0 : nt!IopDeleteFile+0x11e
fffff880`0a6db290 fffff800`02fb14a7 : fffffa80`0836d370 00000000`00000000 fffffa80`07f41b60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`0a6db2f0 fffff800`02fb10b4 : 00000000`00002f70 fffffa80`0836d370 fffff8a0`00001830 00000000`00002f70 : nt!ObpCloseHandleTableEntry+0xb7
fffff880`0a6db380 fffff800`02cdb1d3 : fffffa80`07f41b60 fffff880`0a6db450 fffff880`0a6db5c0 fffff800`02dfb571 : nt!ObpCloseHandle+0x94
fffff880`0a6db3d0 fffff800`02cd7770 : fffff880`011d366c 00000000`00000000 fffff8a0`06076fb0 fffff880`0a6db5c0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a6db568 fffff880`011d366c : 00000000`00000000 fffff8a0`06076fb0 fffff880`0a6db5c0 fffff800`02cd15bc : nt!KiServiceLinkage
fffff880`0a6db570 fffff800`0303db05 : fffff880`0a6db748 fffff880`0a6db740 fffff8a0`17490b60 00000000`000007ff : fileinfo!FIPfInterfaceClose+0x48
fffff880`0a6db5a0 fffff800`030c5bf7 : fffff8a0`174904e0 fffff8a0`174904e0 fffff8a0`17490b60 fffff880`0a6db740 : nt!PfpOpenHandleClose+0x55
fffff880`0a6db5f0 fffff800`03126ea1 : 00000000`00000000 00000000`00000000 fffffa80`4c506343 00000000`00000000 : nt!PfSnCleanupPrefetchSectionInfo+0x57
fffff880`0a6db620 fffff800`03127067 : fffff880`0a6db740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x4b1
fffff880`0a6db710 fffff800`0312748f : 00000017`44954bfd fffffa80`0836d370 fffff8a0`17491000 00000000`c00000ce : nt!PfSnPrefetchScenario+0x187
fffff880`0a6db980 fffff800`02f2006f : 00000000`00000000 00000000`2a64407d fffffa80`0ca43e00 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`0a6dba50 fffff800`02f6698c : fffffa80`07f41b60 fffffa80`0ca43e00 00000000`16050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x51340
fffff880`0a6dba80 fffff800`02c8ebb5 : fffff800`02e43e80 00000000`00000000 fffff800`02f66844 fffffa80`07f41b60 : nt!PspUserThreadStartup+0x148
fffff880`0a6dbae0 fffff800`02c8eb37 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`0a6dbc20 00000000`7743be30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0008fcf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7743be30


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+c6c
fffff800`02dfd49c cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+c6c

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c6c

BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c6c

Followup: Pool_corruption
---------

Sorry about the length of this but Im leaving it so it can be looked at without having to be re-run

Ken

 

[James7679]

first thing, when you ask if im running RAID, what do you mean? second thing when you say 7100, do you mean build 7100, and how am i supposed to upgrade that? and third of all what is corrupt pool? I REALLY APPRECIATE YOUR TIME AND HELP. please dont get frustrated with me, i really dont know anything about software and faults, errors etc. but if you can tell me what i need to do to fix this i will be indebted to you.

 

[zigzag3143]

first thing, when you ask if im running RAID, what do you mean? second thing when you say 7100, do you mean build 7100, and how am i supposed to upgrade that? and third of all what is corrupt pool? I REALLY APPRECIATE YOUR TIME AND HELP. please dont get frustrated with me, i really dont know anything about software and faults, errors etc. but if you can tell me what i need to do to fix this i will be indebted to you.

James

Im sorry. trying to do 10 things at once. It is build 7100. If you look at the debug I hgihlighted it. amd 64bit 7100. the current version is 7600. 7100 had some problems and they were fixed in later builds

Dont worry about corrupt pool. that only means for some reason the memory couldn't be read so there is less information.

the raid thing. the file probably responsible for this bsod was fltmgr.sys that is a file usually associated with a RAID controller. raid is a collection of HD's and the thing to control it is built into the motherboard.

Im not at all frustrated James. Six months ago I was on your end and someone was helping me. We like what we do, and get satisfaction from solving problems.

I was hoping one of our experts (no Im not one) on BSOD's would be online but no such luck. they will find the dumps that I can tell you.

Ken

 

[usasma]

Your nVidia Storage drivers are from 2007, please update them ASAP.
The errors are primarily related to memory - so I'd suggest a memory diagnostic as the first step: Memory Diagnostics

Please let us know the results of the memory diagnostic

Summary of the memory dumps:

Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Tue Oct 13 06:54:19.992 2009 (GMT-4)
System Uptime: 0 days 7:33:26.789
BugCheck 19, {3, fffffa8006c99660, fffffa8006c19660, fffffa8006c99660}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a54 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Wed Oct 14 15:06:43.606 2009 (GMT-4)
System Uptime: 0 days 2:26:04.403
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 50, {fffff680008538e8, 0, fffff80002cbdb1c, 2}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Oct 15 14:13:30.356 2009 (GMT-4)
System Uptime: 0 days 1:49:10.137
BugCheck 1E, {ffffffffc0000005, fffff80002cdaf44, 0, 0}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  FlashUtil10b.e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Oct 15 12:23:18.658 2009 (GMT-4)
System Uptime: 0 days 3:23:42.439
BugCheck 19, {3, fffff8a01747f620, fffff8a01747f620, fa800836a1e004c0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  FlashUtil10b.e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Oct 15 08:58:56.921 2009 (GMT-4)
System Uptime: 0 days 0:01:38.687
BugCheck 1E, {ffffffffc000001d, fffff80002c8ff0e, 2, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiServiceTable+80e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Oct 16 10:43:55.887 2009 (GMT-4)
System Uptime: 0 days 0:20:35.668
BugCheck 1A, {41201, fffff683ff7f1298, 21a00001df590025, fffffa800baa9ec0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13286 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Oct 16 13:53:04.673 2009 (GMT-4)
System Uptime: 0 days 3:08:06.455
BugCheck 1A, {5003, fffff70001080000, e3e, e400000187c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34435 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.

 

[James7679]

ok, well 26 hours later, i have isolated the problem to a driver conflict from win update. win update has dld an update for my card once before with slight problems. the thing is i looked in my updates and it dld the driver again, comparing the dates of when the computer started crashing regularly it made sense. so i tried to use sys restore to restore at a date prior to the update. when i did this i got an error msg stating that i needed to run a disk check cause there are errors on my hard drive. rebooted, ran disk check allowed repairs and then used sysrest to restore from my backup drive to a previous iso of hard drive. then the computer still crashed. i remembered with the previous occurance of this problem i was directed to uninstall all hardware, clear cmos, reinstall all hardware and reboot. so i did it this time and so far so good, no crashes, no bugs, no bsod. for now.....i will let you know what happens when it happens. this driver(i know is the problem) is somehow totally screwing my computer up. and with no way to report it to microsoft?

 

[James7679]

Ok , after trying to use all of windows 7 diagnose and repair features(it has more than any OS ever) and not being able to get any of them to work, I realized that my registry was corrupted along with a lot of my files. SOLUTION; ran REPAIR INSTALL and fixed everything. Thank you all for your help. Its great to see that you can get knowledgable people on at least one Windows 7 forum.