New
#1
Bugcheck code 0x00000109 after chitka/Adobe Flash HD virus removal
Hello,
I was going to submit a BSOD, but upon searching the forum, I found a similar incident:
BDSO error 0x00000109 with driver verifier issues
Recommendations on this incident included doing a memory check, a CHKDSK /F /R and a SFC /scannow. The memory check did not show up an issue, but CHKDSK /F /R showed up with the following issue:
SFC /scannow showed up the following problems:Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 5/29/2013 6:17:33 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DECO-TIM2011.Deco-Sign.local
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
206848 file records processed.
File verification completed.
Index entries referencing file 34772 will not be validated
because this file contains too many file names.
Index entries referencing file 37182 will not be validated
because this file contains too many file names.
Index entries referencing file 37453 will not be validated
because this file contains too many file names.
Index entries referencing file 37495 will not be validated
because this file contains too many file names.
Index entries referencing file 46544 will not be validated
because this file contains too many file names.
Index entries referencing file 46643 will not be validated
because this file contains too many file names.
Index entries referencing file 46807 will not be validated
because this file contains too many file names.
Index entries referencing file 46809 will not be validated
because this file contains too many file names.
Index entries referencing file 46843 will not be validated
because this file contains too many file names.
Index entries referencing file 46887 will not be validated
because this file contains too many file names.
2959 large file records processed.
0 bad file records processed.
2 EA records processed.
139 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
262214 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
206848 file SDs/SIDs processed.
Security descriptor verification completed.
27684 data files processed.
CHKDSK is verifying Usn Journal...
35733088 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
206832 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
58595761 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
302179327 KB total disk space.
67396684 KB in 119005 files.
79816 KB in 27685 indexes.
0 KB in bad sectors.
319783 KB in use by the system.
65536 KB occupied by the log file.
234383044 KB available on disk.
4096 bytes in each allocation unit.
75544831 total allocation units on disk.
58595761 allocation units available on disk.
Internal Info:
00 28 03 00 0d 3d 02 00 e0 47 04 00 00 00 00 00 .(...=...G......
67 02 00 00 8b 00 00 00 00 00 00 00 00 00 00 00 g...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
I have attached the CBS.log file. Should I still go about collecting the BSOD information or try to address these issues first? I'm unsure how to track back file number to a file name in the CHKDSK log file and the one reference I was able to find for a tool to do this doesn't seem to exist anymore. As for the SFC /scannow, I'm not sure how to proceed. The basic BSOD information is:C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
This was gathered by WhoCrashed utility.On Tue 5/28/2013 9:11:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-12916-01.dmp
This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
Bugcheck code: 0x109 (0xA3A039D896076583, 0xB3B7465EE885A181, 0xFFFFF80000B96BB0, 0x6)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_fffff80000b95000.sys .
Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION
Thanks,
Jeff