Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD again

23 Jul 2010   #1
LosT SpiriT

windows 7 64 bit
BSOD again

Hi everyone

just before 4 days i had an issue with BSOD

and i opened topic here

and the members help me a lot thankfully but now after everything was going alright

it reoccurs again

My System SpecsSystem Spec
23 Jul 2010   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by LosT SpiriT View Post
Hi everyone

just before 4 days i had an issue with BSOD

and i opened topic here

and the members help me a lot thankfully but now after everything was going alright

it reoccurs again
The DMP file blames a win 7 OS file which is nearly impossible. here are the things you can try
1-run a system file check to verify and repair your system files.
(type cmd in search>right click and run as admin>SFC /SCANNOW)
Let us know the results

2-run driver verifier.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If you are overclocking stop.

Let us know if you need assistance


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

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

Symbol search path is: SRV*C:\symbols*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Thu Jul 22 20:59:23.937 2010 (GMT-4)
System Uptime: 3 days 2:18:25.539
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 86000000, 0, 0}

GetPointerFromAddress: unable to read from fffff80002ca90e0
GetUlongFromAddress: unable to read from fffff80002c171b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+7338 )

Followup: MachineOwner

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

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.
Arg1: 0000000000000022, 
Arg2: 0000000086000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:

GetUlongFromAddress: unable to read from fffff80002c171b0

BUGCHECK_STR:  0x19_22

POOL_ADDRESS:  0000000086000000 



PROCESS_NAME:  firefox.exe


LAST_CONTROL_TRANSFER:  from fffff80002aca330 to fffff80002a72f00

fffff880`04688488 fffff800`02aca330 : 00000000`00000019 00000000`00000022 00000000`86000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`04688490 fffff800`02ba6518 : 00000000`00000000 fffff880`046885e0 fffff880`04688550 fffffa80`00000001 : nt! ?? ::FNODOBFM::`string'+0x7338
fffff880`04688520 fffff880`012ab8fa : fffffa80`04e21180 fffff880`046887e0 fffff8a0`01d5b250 00000000`00000000 : nt!ExFreePoolWithTag+0x468
fffff880`046885d0 fffff880`012b3adc : fffffa80`03f97b20 fffff8a0`01d5b380 fffff8a0`01d5b250 fffffa80`04e21180 : Ntfs!NtfsCommonClose+0x43a
fffff880`046886a0 fffff880`010f623f : fffff880`04688801 fffffa80`0431dc60 fffff880`04688000 00000000`00000003 : Ntfs!NtfsFsdClose+0x2dc
fffff880`046887a0 fffff880`010f46df : fffffa80`04cdf8e0 fffffa80`0431dc60 fffffa80`04ab4f00 fffffa80`0431dc60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`04688830 fffff800`02d8640e : fffffa80`03f35c70 fffffa80`04c8e820 fffffa80`040b1b30 fffffa80`04cdf8e0 : fltmgr!FltpDispatch+0xcf
fffff880`04688890 fffff800`02a780b4 : fffffa80`04e02bd0 fffff8a0`0e9c5a60 fffffa80`03cebde0 fffffa80`03cebde0 : nt!IopDeleteFile+0x11e
fffff880`04688920 fffff800`02d86194 : fffff8a0`0e9c5a60 00000000`00000000 fffffa80`045fab60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`04688980 fffff800`02d2f870 : 00000000`00000348 fffff8a0`0e9c5a60 fffff8a0`0844dd20 00000000`00000348 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`04688a10 fffff800`02d2f7e4 : 00000000`00000004 00000000`00000000 fffffa80`040b1b30 fffff800`02d18f21 : nt!ObpCloseHandleProcedure+0x30
fffff880`04688a50 fffff800`02d2e6ae : fffff8a0`0ac41a01 00000000`00000001 fffffa80`040b1b30 fffffa80`040b1c01 : nt!ExSweepHandleTable+0x74
fffff880`04688a90 fffff800`02d55724 : fffff8a0`0ac41a50 00000000`00000000 00000000`00000000 fffffa80`046ad090 : nt!ObKillProcess+0x62
fffff880`04688ad0 fffff800`02d2ecb8 : 00000000`00000000 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x3f4
fffff880`04688ba0 fffff800`02a72153 : fffffa80`040b1b30 00000000`00000000 fffffa80`045fab60 fffffa80`0404bc30 : nt!NtTerminateProcess+0x138
fffff880`04688c20 00000000`777c017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011def8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777c017a


nt! ?? ::FNODOBFM::`string'+7338
fffff800`02aca330 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+7338

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+7338

BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+7338

Followup: MachineOwner

ISODrv64.sys        fffff880`02cb4000    fffff880`02cd2000    0x0001e000    0x4991474a    2/10/2009 05:22:18                        
AsIO.sys        fffff880`03d7f000    fffff880`03d85000    0x00006000    0x49d9ad64    4/6/2009 03:21:08                        
spldr.sys        fffff880`015d8000    fffff880`015e0000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
ASACPI.sys        fffff880`0fe11000    0043f8b9`0fe19000    0x0044003900008000    0x4a0b72fd    5/13/2009 21:25:17                        
amdxata.sys        fffff880`010e8000    fffff880`010f3000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
Rt64win7.sys        fffff880`03c7a000    fffff300`03cb3000    0xfffffa8000039000    0x4a16bc2e    5/22/2009 10:52:30                        
viahduaa.sys        fffff880`06057000    fffff87f`061eb000    0xffffffff00194000    0x4a56b055    7/9/2009 23:07:01
My System SpecsSystem Spec
23 Jul 2010   #3
LosT SpiriT

windows 7 64 bit


I have done the first step

and the window found corrupt files unable to fix them

do i proceed to the next one ?
My System SpecsSystem Spec

24 Jul 2010   #4
LosT SpiriT

windows 7 64 bit

someone could help me?
My System SpecsSystem Spec
24 Jul 2010   #5

Microsoft Window 7 Professional 32 bit

Please run it again, if it keep saying it found corrupted files that unable to fix, please do a Repair Install


My System SpecsSystem Spec
24 Jul 2010   #6

Windows 7 Professional x64

Go ahead and enable driver verifier.

Using Driver Verifier to identify issues with Drivers
My System SpecsSystem Spec
24 Jul 2010   #7
LosT SpiriT

windows 7 64 bit

I tested it again with the same results (unable to fix corrupted files)

so what will i do?

repair install or driver verifier

sorry for the late response my internet connection was down
My System SpecsSystem Spec
24 Jul 2010   #8

Windows 7 Professional x64

Verifier first...

Actually, it's up to you. Personally, I doubt a repair install has a high likelihood of helping, but it will not hurt anything.
My System SpecsSystem Spec

 BSOD again

Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:48.
Twitter Facebook Google+