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: 3 different BSOD's


22 Apr 2012   #1

widows 7 ultimate x64
 
 
3 different BSOD's

I recently got 3 different BSOD's....

I got the 0x124 when playing skyrim and when running a stress test on my computer

I got the 0x101 when webcamming

and just now I got the 0x19 when trying to visit a website that I ALWAYS visit...

I'm very frustrated and I tried posting another thread with this to no success...I stopped using webcam so the 101 stopped, the 124 hasn't happened in awhile even when playing skyrim for awhile, but this new one worries me...I've included a .dmp file if someone wants to have a look at it for me and if anyone has steps I can take to prevent any and all of these or prgrams to help please help me, I don't want to buy a new computer


My System SpecsSystem Spec
.

22 Apr 2012   #2

widows 7 ultimate x64
 
 

btw all these errors just started a week ago, I've had this computer for 2 years, I hope that helps a little
My System SpecsSystem Spec
23 Apr 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\jayman123\042212-25521-01 - Copy.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`0304b650
Debug session time: Sun Apr 22 15:11:45.454 2012 (UTC - 6:00)
System Uptime: 0 days 15:13:55.874
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8008750cb0, fffffa8008751350, 46a4768}

Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceClose+48 )

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

3: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8008750cb0, The pool entry we were looking for within the page.
Arg3: fffffa8008751350, The next pool entry.
Arg4: 00000000046a4768, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b5100
 fffffa8008750cb0 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fb0cae to fffff80002e83c80

STACK_TEXT:  
fffff880`088d7fa8 fffff800`02fb0cae : 00000000`00000019 00000000`00000020 fffffa80`08750cb0 fffffa80`08751350 : nt!KeBugCheckEx
fffff880`088d7fb0 fffff800`031bf153 : fffffa80`08750d08 00000000`00000000 fffffa80`63664d46 fffffa80`08750d08 : nt!ExDeferredFreePool+0x12da
fffff880`088d8060 fffff880`010e7e6c : fffffa80`046ec630 fffff880`088d81c0 fffffa80`0a5829e0 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1db03
fffff880`088d8090 fffff880`010e7107 : fffff880`088d81c0 fffff800`02fb1dd7 00000000`00000010 fffff8a0`000019b0 : fltmgr!FltpGetStartingCallbackNode+0x38c
fffff880`088d8120 fffff880`010e56c7 : fffff8a0`000019b0 fffffa80`03cd5040 fffffa80`0a5829b0 00000000`00000000 : fltmgr!FltpPassThrough+0xb7
fffff880`088d81a0 fffff800`0317f12e : fffffa80`0a5829e0 fffffa80`04bcb860 fffffa80`03cd5040 fffffa80`04c478e0 : fltmgr!FltpDispatch+0xb7
fffff880`088d8200 fffff800`02e8cef4 : fffffa80`04347210 fffffa80`0b0cf940 fffffa80`03ce47b0 00000000`0000000b : nt!IopDeleteFile+0x11e
fffff880`088d8290 fffff800`03179ce4 : fffffa80`0b0cf940 00000000`00000000 fffffa80`0a6f1060 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`088d82f0 fffff800`0317a294 : 00000000`0000142c fffffa80`0b0cf940 fffff8a0`000019b0 00000000`0000142c : nt!ObpCloseHandleTableEntry+0xc4
fffff880`088d8380 fffff800`02e82f13 : fffffa80`0a6f1060 fffff880`088d8450 fffff880`088d85c0 00000000`00000008 : nt!ObpCloseHandle+0x94
fffff880`088d83d0 fffff800`02e7f4d0 : fffff880`0113b66c 00000000`00000000 fffff8a0`02e0c470 fffff880`088d85c0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`088d8568 fffff880`0113b66c : 00000000`00000000 fffff8a0`02e0c470 fffff880`088d85c0 fffff800`02e8cefc : nt!KiServiceLinkage
fffff880`088d8570 fffff800`031f15e5 : fffff880`088d8748 fffff880`088d8740 fffff8a0`0dde2d68 00000000`000007ff : fileinfo!FIPfInterfaceClose+0x48
fffff880`088d85a0 fffff800`0327b577 : fffff8a0`0dde1a48 fffff8a0`0dde1a48 fffff8a0`0dde2d68 fffff880`088d8740 : nt!PfpOpenHandleClose+0x55
fffff880`088d85f0 fffff800`032dee41 : 00000000`00000000 00000000`00000000 fffffa80`4c506343 00000000`00000000 : nt!PfSnCleanupPrefetchSectionInfo+0x57
fffff880`088d8620 fffff800`032df007 : fffff880`088d8740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x4b1
fffff880`088d8710 fffff800`032df42f : 00000000`04379ed0 fffffa80`0b0cf940 fffff8a0`0de34000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187
fffff880`088d8980 fffff800`031de7df : 00000000`00000000 00000000`1124b760 fffffa80`0a5cd160 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`088d8a50 fffff800`03170d2c : fffffa80`0a6f1060 fffffa80`0a5cd160 00000000`14050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x50eb0
fffff880`088d8a80 fffff800`02e74af5 : fffff880`009ea180 00000000`00000000 fffff800`03170be4 fffffa80`0a6f1060 : nt!PspUserThreadStartup+0x148
fffff880`088d8ae0 fffff800`02e74a77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`088d8c20 00000000`7767c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0012fa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767c500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fileinfo!FIPfInterfaceClose+48
fffff880`0113b66c 488bcb          mov     rcx,rbx

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  fileinfo!FIPfInterfaceClose+48

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481

FAILURE_BUCKET_ID:  X64_0x19_20_fileinfo!FIPfInterfaceClose+48

BUCKET_ID:  X64_0x19_20_fileinfo!FIPfInterfaceClose+48

Followup: MachineOwner
---------
The above crash usually indicates a driver at fault. Yours appears to be due to hard disk errors or hard disk controller corruption or missing controllers. Start by checking for data corruption.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.

  • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Also, for the other two crashes:
My System SpecsSystem Spec
.


Reply

 3 different BSOD's




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 02:00 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33