Windows 7: BSoDs after Windows updates

amccombs · 18 Jun 2010

I did a Windows update today, these updates were installed today, got more than 4 BSoD since then, could it be one of these or is it coincidence?

Security Update for Windows 7 for x64-based Systems (KB979482)
Windows Malicious Software Removal Tool x64 - June 2010 (KB890830)
Cumulative Security Update for ActiveX Killbits for Windows 7 for x64-based Systems (KB980195)
Security Update for the 2007 Microsoft Office System (KB982312)
Microsoft .NET Framework 3.5 SP1 Security Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB979916)
Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB973688) Security Update for Microsoft Office Excel 2007 (KB982308)
Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB954430)
Security Update for Microsoft Office InfoPath 2007 (KB979441)
Security Update for Microsoft Office PowerPoint 2007 (KB982158)
Security Update for Microsoft Office Publisher 2007 (KB982124)
Security Update for Windows 7 for x64-based Systems (KB980218)
Update for Microsoft Office Outlook 2007 Junk Email Filter (KB983486)
Security Update for Windows 7 for x64-based Systems (KB979559)
Security Update for Microsoft Office Word 2007 (KB982135)
Security Update for the 2007 Microsoft Office System (KB982331)
Cumulative Security Update for Internet Explorer 8 for Windows 7 for x64-based Systems (KB982381)

Windows 7 Ultimate x64
Asus M4A78T-E
AMD Phenom II x4 955 Black Edition 3.2GHz
8GB G.Skill DDR3 1333 RAM
OCZ 700w
WD 750GB SATA

attached are mini-dmps

ttran · 18 Jun 2010

Are you using AVG anti-virus software, third party security programs is notorious fo causing BSODs and avg is not an expception. I would recommend to uninstall AVG just for testing purpose only
Beside that, the bugcheck indicated exception code fffffffc000005, it might be problem related to memory, I would download third party called memtest86, burn it to cd and let it run for at least 7 passes

Bugcheck 24 usually points to hard drive. In addition, NTFS.sys is a hard drive controller driver, so a check disk and diagnostic are in order. The instruction is below:

Code:

http://www.carrona.org/hddiag.html

You can also open a command prompt and enter chkdsk /r /f.

bugcheck:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88003e28a8c, fffff880009a8bf8, fffff880009a8460}
Probably caused by : avgldx64.sys ( avgldx64+28a8c )
Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002d0acc3, fffff880033f2198, fffff880033f1a00}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4e92c )
Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88007424b38, fffff880074243a0, fffff880012e915b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+736 )
Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff880046f6718, fffff880046f5f80, fffff88001309c27}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
Followup: MachineOwner
---------

Regard

Tuan

JMH · 18 Jun 2010

Quote: Originally Posted by amccombs

I did a Windows update today, these updates were installed today, got more than 4 BSoD since then, could it be one of these or is it coincidence?

Security Update for Windows 7 for x64-based Systems (KB979482)
Windows Malicious Software Removal Tool x64 - June 2010 (KB890830)
Cumulative Security Update for ActiveX Killbits for Windows 7 for x64-based Systems (KB980195)
Security Update for the 2007 Microsoft Office System (KB982312)
Microsoft .NET Framework 3.5 SP1 Security Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB979916)
Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB973688) Security Update for Microsoft Office Excel 2007 (KB982308)
Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB954430)
Security Update for Microsoft Office InfoPath 2007 (KB979441)
Security Update for Microsoft Office PowerPoint 2007 (KB982158)
Security Update for Microsoft Office Publisher 2007 (KB982124)
Security Update for Windows 7 for x64-based Systems (KB980218)
Update for Microsoft Office Outlook 2007 Junk Email Filter (KB983486)
Security Update for Windows 7 for x64-based Systems (KB979559)
Security Update for Microsoft Office Word 2007 (KB982135)
Security Update for the 2007 Microsoft Office System (KB982331)
Cumulative Security Update for Internet Explorer 8 for Windows 7 for x64-based Systems (KB982381)

Windows 7 Ultimate x64
Asus M4A78T-E
AMD Phenom II x4 955 Black Edition 3.2GHz
8GB G.Skill DDR3 1333 RAM
OCZ 700w
WD 750GB SATA

attached are mini-dmps

Hi amccombs and welcome;

These were probably caused by several sources. One specifically mentioned is your AVG anti-virus. I would remove it and replace with Microsoft Security Essentials. It has a much smaller resource footprint and is more stable.

The others point to a memory exception not handled, and because of that I would download a 3rd party app called memtestx86, burn it to cd, and run it for at least 7 passes.

I would also run a chkdsk as it is mentioned in the usual causes.

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Because Windows 7 files are mentioned I would run a system file check

To run a system file check type cmd in search, then right click and run as administrator. Finally type sfc /scannow

Please let us know how you go.

Jan

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

7E
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,

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 19:47:22.727 2010 (GMT-4)
System Uptime: 0 days 0:00:15.397
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88003e28a8c, fffff880009a8bf8, fffff880009a8460}
Probably caused by : avgldx64.sys ( avgldx64+28a8c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 10:29:51.401 2010 (GMT-4)
System Uptime: 0 days 0:11:13.071
BugCheck 1000007E, {ffffffffc0000005, fffff80002d0acc3, fffff880033f2198, fffff880033f1a00}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4e92c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 10:17:02.716 2010 (GMT-4)
System Uptime: 0 days 0:00:35.386
BugCheck 24, {1904fb, fffff880046f6718, fffff880046f5f80, fffff88001309c27}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
PROCESS_NAME:  services.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 10:14:51.803 2010 (GMT-4)
System Uptime: 0 days 0:00:58.473
BugCheck 24, {1904fb, fffff88007424b38, fffff880074243a0, fffff880012e915b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+736 )
PROCESS_NAME:  Skype.exe
BUGCHECK_STR:  0x24

amccombs · 20 Jun 2010

what I don't like about Microsoft Security Essentials. is that it does not have an outgoing firewall, I like to setup some apps to prevent them from phoning home.

I ran memtest 3.4, as 3.5 would just reboot the computer. 3.4 did not find any errors, that program could use work as to show people when it's done with a pass, and not just go into an indefinite loop.

What did you guys run in the mini-dumps to get the Bugcheck code?

Code:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
Cleaning up instance tags for file 0x156eb.
  161792 file records processed.                                          File verification completed.
  258 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              61 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  207972 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  161792 file SDs/SIDs processed.                                         Cleaning up 420 unused index entries from index $SII of file 0x9.
Cleaning up 420 unused index entries from index $SDH of file 0x9.
Cleaning up 420 unused security descriptors.
Security descriptor verification completed.
  23091 data files processed.                                            CHKDSK is verifying Usn Journal...
  34816856 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  161776 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  10219800 free clusters processed.                                         Free space verification is complete.
Windows has made corrections to the file system.

 474527969 KB total disk space.
 433291548 KB in 129457 files.
     80336 KB in 23092 indexes.
         0 KB in bad sectors.
    276881 KB in use by the system.
     65536 KB occupied by the log file.
  40879204 KB available on disk.

      4096 bytes in each allocation unit.
 118631992 total allocation units on disk.
  10219801 allocation units available on disk.

Internal Info:
00 78 02 00 ee 53 02 00 3f 26 04 00 00 00 00 00  .x...S..?&......
d4 62 00 00 3d 00 00 00 00 00 00 00 00 00 00 00  .b..=...........
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.

CarlTR6 · 20 Jun 2010

Quote: Originally Posted by amccombs

what I don't like about Microsoft Security Essentials. is that it does not have an outgoing firewall, I like to setup some apps to prevent them from phoning home.

I ran memtest 3.4, as 3.5 would just reboot the computer. 3.4 did not find any errors, that program could use work as to show people when it's done with a pass, and not just go into an indefinite loop.

What did you guys run in the mini-dumps to get the Bugcheck code?

WinDbg is what we use for debugging.

You can always reinstall AVG after you are finished diagnosing the problem. If the problem goes away when you uninstall AVG, you have found your problem.

JMH · 20 Jun 2010

amccombs,

Confirming - What CarlTR6 said is correct.

Did you follow all of the procedures that I recommended above?

Jan.

Windows 7: BSoDs after Windows updates

BSoDs after Windows updates problems?