BSOD after windows update,

alexlomba87 · 21 Dec 2012

Hi everyone,

I've absolutely no clue about this. I've searched for any help on the internet but it seems something like an unique case.

The problem is, as title says, a BSOD "BAD_POOL_CALLER"; this happened after a normal Windows update. Windows promped me with the same "restart your computer to install the updates". I restarted and left my computer installing the updates. When back, it was on the BSOD.
From then on, my system didn't restart on normal mode (BSOD some time after the loading windows logo).

I've already tried just every system restore tool given by default by windows.
The automatic restore procedure didn't work: "the system couldn't be restored" (or something like that).
The return to a previous system configuration didn't work as well: for every previous system point that I could choose from the list, I had the same result "the recovery procedure failed, error ...".
After that, I tryied the memory check option, with no result.

The only thing working is the safe mode boot, and I will be working from this mode from now on.
As suggested, I launched sfc /scannow from cmd. The result was "impossible to repair some of the found damaged files. The details are available in the CBS.Log file".

I'll attach the Zip folder containg every files from the SF Diagnostic Tool; I've also included in the folder that CBS.log file.

Too bad I've no recovery disk at all. Before proceeding to a complete reset, I hope in some help on this.
Thanks in advance.
Attachment 246577

koolkat77 · 21 Dec 2012

Welcome to SevenForums.

Daemon Tools

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88002f88324, fffff9800d198ea0, 0}

*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

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

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Uninstall AVG: AVG | Download tools and utilities

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

Microsoft Security Essentials - Free Antivirus for Windows
- Malwarebytes - Free
  - Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Disk Check on your hard drive for file system errors and bad sectors on it:

Disk Check

Perform a System File Check:

Click on the start
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 200042, fffffa800c1df430}

*** WARNING: Unable to verify timestamp for btmhsf.sys
*** ERROR: Module load completed but symbols could not be loaded for btmhsf.sys
GetPointerFromAddress: unable to read from fffff80003316100
GetUlongFromAddress: unable to read from fffff800033161c0
Probably caused by : btmhsf.sys ( btmhsf+667b )

Go to this link: Intel® Driver Update Utility. Check the system for latest updates. Download and install all that it finds.

Reduce items at start-up. Nothing except anti-virus is required:

Post back results

alexlomba87 · 22 Dec 2012

A step forward, but nothing really helpful, the problem still exist.

After unistalling Daemon tools, the BSOD changed and occurred after the "loading windows" screen; the computer now just arrives to the Window screen where you select a user to login. When there, it's a matter of millisecs and this BSOD happens:
"Device driver attempting to corrupt system [...] currently on kernel stack [...] must be replaced.
***STOP: 0x00000C4 (0x000000000,0x000000000,0x000000000)".

Then, I tried all of your suggestions. I performed a clean startup; I unistalled AVG (I cannot install most of the programs because I work from the safe mode); I've checked for Intel drivers update with no result.

As a clue, the last installation performed during my last working session, in addition to the windows update, was the installation of BlueSoleil 5.3. I've unistalled it from the Safe mode though, and that don't seems to help (especially since I've tryied the clean startup).

I'm now going to perform a Disk Check (even if it's only a month since my last, where it already repaired some damaged sectors) and then a new SFC, as suggested.
Thanks for now. I'll post the results ASAP.

koolkat77 · 22 Dec 2012

When did you last re-install windows on your PC?

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

alexlomba87 · 22 Dec 2012

Thanks for the help.

After completing the Disk Check the BSOD re-appeared again.
Then, just out of curiosity, I tried to perform again the System Restore.
The result was, again, this:
"System Restore did not complete successfully: files and settings not changed.
Details:
an unspecified error occurred during System Restore. (0x8000ffff)"
Which was exactly the same error that I've had before. After that, I simply tried again to normally boot windows.
Surprise: Windows' boot was a success. When started, it prompted me with the warning that the system was restored to the previous selected point (even if the procedure failed as always).
The restored point included the necessity to shut down the PC in order to install the last windows updates at that point already prepared.
After creating a repair disk (boot disk) I turned off my pc and, after the installation of the updates, the boot didn't present any BSOD. As normal.

All this story is pretty strange, I'd really like to understand what was happening. Anyway, thanks so much for the help.

P.S. The computer is pretty new, I have it since 4 months, never re-installed windows. Anyway, I had this problem with a BSOD after installing windows updates already once two months ago, and I solved immediately with the system restore. Now I'm really unhappy with this thing of the updates, could be wise to turn them off? I appreciate any suggestion to avoid this problem again.

koolkat77 · 22 Dec 2012

It might just actually be a software conflict.

IMO, you should perform a clean install and install all updates first.
Before you even install a software.
Clean Reinstall - Factory OEM Windows 7

Avoid the bloatware that comes with the system.
Clean Up Factory Bloatware

Install the basic things MSE & Mbam as your security software, latest drivers from relevant manufacturing websites.

Post if there are BSODs.

alexlomba87 · 22 Dec 2012

Thanks,
I'm not sure I can proceed with a clean reinstall, since there's no listed italian installer of Win7. I'd like not risking to compromise my warranty with a different installation.
I thought the problem was linked to the windows update since it was happening just after them, but you could be right about the software conflict.
About the bloatware, they're the first thing that I take care of - as well as the most recent updates from relevant manufacturers, I try to keep everything up to date.
Thanks again for the availability.

koolkat77 · 22 Dec 2012

I have asked a friend to take a look at your cbs log.
Lets wait for a reply.

NoelDP · 23 Dec 2012

There are a couple of errors in teh log.....

Code:

2012-12-21 22:24:43, Info                  CSI    00000309 [SR] Repairing 2 components
2012-12-21 22:24:43, Info                  CSI    0000030a [SR] Beginning Verify and Repair transaction
2012-12-21 22:24:43, Info                  CSI    0000030b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2012-12-21 22:24:43, Info                  CSI    0000030c [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-21 22:24:44, Info                  CSI    0000030d Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2012-12-21 22:24:44, Info                  CSI    0000030e [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-21 22:24:44, Info                  CSI    0000030f [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-12-21 22:24:44, Info                  CSI    00000310 Hashes for file member \??\C:\Windows\IME\IMESC5\DICTS\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2012-12-21 22:24:44, Info                  CSI    00000311 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2012-12-21 22:24:44, Info                  CSI    00000312 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted
2012-12-21 22:24:44, Info                  CSI    00000313 [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\System32\wdi\perftrack"\[l:26{13}]"ieframe.ptxml" from store
2012-12-21 22:24:44, Info                  CSI    00000314 Repair results created:

I would suggest running CheckSUR as well, in case it finds any more, before we start trying to repair this one.

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and attach it to your reply.