BSOD after clean install, new power supply & new motherboard.

[CliveK]

I have had issues with BSODs for a while, now. I have had the hard drives, RAM and graphics cards professionally checked.

I installed a new motherboard, reinstalled Windows 7 (again) and installed a new power supply as the old one was on its last legs. Any help greatly appreciated as it is driving me crazy!

View attachment 262228

Kindest regards,

Clive.

 

[Northernsoul55]

Hi,

Firstly please install Windows Service Pack 1 as it will increase system stability.
Then once installed please run Windows Updates and install the latest updates.

:ar:http://windows.microsoft.com/is-IS/windows7/install-windows-7-service-pack-1
:ar:http://windows.microsoft.com/is-IS/windows/service-packs-download#sptabs=win7

From your crash dumps:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff6800004a950, f020000088fd9867, fffff6800002cc50}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800004a950
Arg3: f020000088fd9867
Arg4: fffff6800002cc50
STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

Driver causing issues:

fffff880`08c9d868 fffff880`0498ac05Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm nvlddmkm.sys Thu May 14 21:48:07 2009

Please update your driver as it is outdated, choose Option 2:
:ar: http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Run SFC to check the integrity of all Windows 7 system files:
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

You dont appear to have an Anti-Virus Installed, please install:

Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.
:ar: http://windows.microsoft.com/en-US/windows/security-essentials-download

If your issue still remains after you have carried out the above:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

Post back any results/observations

Cheers
Dave

 

[CliveK]

I am unable to install any updates either automatically or manually, even after running the System Readiness application.

 

[Northernsoul55]

Hi CliveK,

Please upload your CBS log:

C:\Windows\Logs\CBS\CBS.log

Zip it up and attach it to your next post.

Cheers

Dave

 

[CliveK]

Hi CliveK,

Please upload your CBS log:

C:\Windows\Logs\CBS\CBS.log

Zip it up and attach it to your next post.

Cheers

Dave

It will not let me zip it or open it - "Access denied."

Also, it's good to see someone else from the NE here. I'm over in Durham.

 

[Northernsoul55]

Hi Clive,

Did you run SFC? What was the outcome?
Were you not able to update your Nvidia Drivers?

Then try the following links in order, and see if you are then able to update:

:ar: http://www.sevenforums.com/tutorials/91738-windows-update-reset.html
:ar: http://www.microsoft.com/en-us/download/details.aspx?id=20858
Post back any progress.

Ah Durham

Cheers

Dave

 

[CliveK]

Hi Clive,

Did you run SFC? What was the outcome?
Were you not able to update your Nvidia Drivers?

Then try the following links in order, and see if you are then able to update:

:ar: http://www.sevenforums.com/tutorials/91738-windows-update-reset.html
:ar: http://www.microsoft.com/en-us/download/details.aspx?id=20858
Post back any progress.

Ah Durham

Cheers

Dave

I've updated the graphics driver without any issues. I ran SFC and it said there were some corrupted files but it could not fix all of them. Still no access to the log.

I've run both links but it won't let me install the hotfix. "Installer encountered an error."

 

[Northernsoul55]

Hi,

Run the SFC again, I forgot to mention to run 3 times...sorry :

• Click on Start > Type in search cmd
  Right-click cmd after results are displayed and Run as Administrator
  Type SFC /scannow at the prompt
  (Note: There is a space between SFC and /scannow)

:ar: SFC Tutorial

   Note

Select option two. If any problems are found, run the scan 3 times and immediately
reboot the computer after each scan.

It may possible fix the corrupted files?

cheers

Dave

 

[CliveK]

Thanks, Dave.

I've run the test 3 times and restarted the PC each time. No improvement, unfortunately.

 

[Northernsoul55]

Were there errors reported?

Ive asked another member to look into why you cant get updates or zip the logs,
might be access permissons or something.

cheers

Dave

 

[tom982]

Hi Clive,

Can you copy your CBS log to your Desktop before trying to zip it up please? The permissions on the CBS folder won't allow you to do anything in there.

Tom

 

[CliveK]

Hi Clive,

Can you copy your CBS log to your Desktop before trying to zip it up please? The permissions on the CBS folder won't allow you to do anything in there.

Tom

Tom, thank you! This makes sense.

Please see attached. View attachment 265506

I've had another BSOD today, too. Still unable to install SP1.

 

[tom982]

Hi Clive,

No problem!

Your CBS log is full of juicy information and has shown the 'corrupt' files as well as the cause of your Windows Update problem.

The SFC log shows one file, and it's WinSxS backup, as being corrupt:

2013-04-25 14:13:29, Info                  CSI    000002f8 [SR] Repairing 1 components
2013-04-25 14:13:29, Info                  CSI    000002f9 [SR] Beginning Verify and Repair transaction
2013-04-25 14:13:30, Info                  CSI    000002fa Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16532_none_c8512f0f2b8716fa\apps.inf do not match actual file [l:16{8}]"apps.inf" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:+04rwqCOyh56JaCaKcRhdz3sTVRYR2l/ISbAlLbHNPg=}
2013-04-25 14:13:30, Info                  CSI    000002fb [SR] Cannot repair member file [l:16{8}]"apps.inf" of Microsoft-Windows-shell32, Version = 6.1.7600.16532, 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
2013-04-25 14:13:31, Info                  CSI    000002fc Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16532_none_c8512f0f2b8716fa\apps.inf do not match actual file [l:16{8}]"apps.inf" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:+04rwqCOyh56JaCaKcRhdz3sTVRYR2l/ISbAlLbHNPg=}
2013-04-25 14:13:31, Info                  CSI    000002fd [SR] Cannot repair member file [l:16{8}]"apps.inf" of Microsoft-Windows-shell32, Version = 6.1.7600.16532, 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
2013-04-25 14:13:31, Info                  CSI    000002fe [SR] This component was referenced by [l:150{75}]"Package_2_for_KB980408~31bf3856ad364e35~amd64~~6.1.1.0.980408-6_neutral_GDR"
2013-04-25 14:13:31, Info                  CSI    000002ff Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16532_none_c8512f0f2b8716fa\apps.inf do not match actual file [l:16{8}]"apps.inf" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:+04rwqCOyh56JaCaKcRhdz3sTVRYR2l/ISbAlLbHNPg=}
2013-04-25 14:13:31, Info                  CSI    00000300 [SR] Could not reproject corrupted file [ml:520{260},l:36{18}]"\??\C:\Windows\Inf"\[l:16{8}]"apps.inf"; source file in store is also corrupted
2013-04-25 14:13:31, Info                  CSI    00000301 Repair results created:
POQ 125 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\af9c13afb641ce01c6370000b4057406._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"

POQ 125 ends.
2013-04-25 14:13:31, Info                  CSI    00000302 [SR] Repair complete

Though I suspect this isn't actually a problem. SFC works by calculating a hash of a file then comparing that to what it should be, if it's different then the file is listed as corrupt and SFC will attempt a replacement, which also failed here as the backup file is 'corrupt' as well. In this case, the file that is corrupt is a configuration file (.inf) so if a setting is changed then the file hash will be different and SFC will detect it as corrupt and I suspect this is what's happened here. This is one of the biggest problems with SFC and it happens to a few files, with settings.ini of Windows Sidebar being hte most common. Microsoft actually posted a support page about that one, assuring everyone it's nothing to worry about:

The SFC.exe command reports Settings.ini file errors in the CBS.log file after you add gadgets to the Windows Vista Sidebar by using the Sysprep tool and an Autounattend.xml file

I've never come across apps.inf in a SFC log so at the moment it's only a guess, to confirm this I would like you to zip up and attach the following file to your next post please:

C:\Windows\Inf\apps.inf

Now for your Windows Update problem. Your CBS log shows that the signature of a few Windows Update packages can't be verified (0x800B0100) and this is probably why SP1 is failing:

2013-04-25 14:20:52, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Mark store corruption flag because of package: Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Failed to initialize package: Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2, from path: \\?\C:\Windows\Servicing\Packages\Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Failed to initialize internal package for package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:52, Info                  CBS    Session: 30294455_3053343094 initialized by client WindowsUpdateAgent.
2013-04-25 14:20:53, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Mark store corruption flag because of package: Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Failed to initialize package: Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2, from path: \\?\C:\Windows\Servicing\Packages\Package_for_KB2807986~31bf3856ad364e35~amd64~~6.1.1.2.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Failed to initialize internal package for package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2013-04-25 14:20:53, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]

I suspect more is going on here though as SFC has only scanned ~40 files when it should be scanning around the 100 mark, so rather than fixing the files shown in the CBS log I would like you to download and install the System Update Readiness Tool (SURT) to check the other files as well:

What is the System Update Readiness Tool?

Save this to your Desktop as we will need to use it again. When it finishes installing (can take several hours on badly affected systems so please be patient) copy and paste the contents of the log into your next post:

C:\Windows\Logs\CBS\CheckSUR.persist.log

If it fails to install, upload the CBS.log as well please!

Tom

Edit: On second inspection, your SFC problem might not exist any more, but I would like you to upload the file anyway please.

 

[CliveK]

Many thanks, Tom. Unfortunately there is no apps.inf file. I've double checked, no apps file in C>Windows>inf.

I'm downloading the SUR tool again now and shall report back soon.

 

[tom982]

Hi Clive,

That's odd, it should be there. Try this:

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   type %windir%\inf\apps.inf > %USERPROFILE%\Desktop\tom982.txt
   
   
4. This will create a text file called tom982.txt on your Desktop. Please attach this to your next post.

Tom

 

[CliveK]

C:\Windows\inf\apps.inf is not recognized as an internal or external command, operable program or batch file.

 

[tom982]

Hi Clive,

Sorry for the confusion, the whole command includes the type at the start(it's using Microsoft's type.exe!)

Tom

 

[CliveK]

Hi Clive,

Sorry for the confusion, the whole command includes the type at the start(it's using Microsoft's type.exe!)

Tom

Ah, I tried that first and got "The system cannot find the file specified." That's why I removed the type. I've added the type again and get the same answer.

 

[tom982]

Hi Clive,

Thanks for letting me know. When you couldn't find the file at first I suspected it was hidden so I tried using a command but it looks like the file isn't there at all! We'll come back to that later, the SURT will probably pick it up.

Tom

 

[Layback Bear]

HI folks.
Tom could this be a Activation problem?