BSOD 1a 00041790 C0802604 0000FFFF

Hi genxcoders.

The issue there is font related. Specifically, the Adobe Type Manager is failing.

Browse to C:\Windows\Fonts, and delete the fonts those you have lately installed before the BSODs started to occur.

If you cannot access to the fonts folder in normal mode, try in safe mode.

Then rebuild the font cache. Go to C:\Windows\System32\ and delete the "Fntcache.dat" file there. Then restart the computer. On restart, a fresh font cache will be built.

Let us know the results.
_______________________________

Code:

9040b278 82c71446 ATMFD+0x14008
9040b2d4 82c742ea ATMFD+0x11446
9040b304 82c743c3 ATMFD+0x142ea
9040b338 82c74d40 ATMFD+0x143c3
9040b34c 82c628ae ATMFD+0x14d40
9040b35c 82c7a2fe ATMFD+0x28ae
9040b3d4 82c7a71f ATMFD+0x1a2fe
9040b444 82c62f97 ATMFD+0x1a71f
9040b804 82c65aae ATMFD+0x2f97
9040b83c 82c67884 ATMFD+0x5aae
9040b948 82c63fbf ATMFD+0x7884
9040b98c 82dfdaa2 ATMFD+0x3fbf
9040b9d4 82dfe265 win32k!PDEVOBJ::QueryFontData+0x3e
9040ba08 82dfb36d win32k!RFONTOBJ::bGetDEVICEMETRICS+0x49
9040bac4 82e776ea win32k!RFONTOBJ::bRealizeFont+0x21b
9040bb70 82e77925 win32k!RFONTOBJ::bInit+0x2e3
9040bb88 82e13177 win32k!RFONTOBJ::vInit+0x16

Code:

BugCheck 1A, {41790, c080206a, ffff, 0}

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

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

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Uninstall McAfee Security Scan Plus. And never let it to be installed.

Attachment 314798

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

This installation is almost a vanilla. It is installed, updated to SP1, chipset, network and graphics driver is installed.

And then the BSOD occurred .....

Code:

BugCheck , {99, 12747, 0, 12947}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

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

Stop 0x4E is either the physical memory is failing or any driver is passing bad information to the memory. And, no driver is found as failing.

Same for the other BSOD ....

Code:

BugCheck 1A, {41790, c080204a, ffff, 0}

Probably caused by : CI.dll ( CI!I_MapCatalog+1e2 )

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

It is also either RAM or a driver. CI.dll is not the actual cause, but it failed to perform some tasks ....

Code:

8e58b240 8c11277e CI!I_MapCatalog+0x1e2
8e58b31c 8c1128c8 CI!I_ReloadCatalogs+0x22e
8e58b368 8c112ba2 CI!I_FindFileOrHeaderHashInCatalogs+0xcd
8e58b3a0 8c10eebd CI!MinCrypK_VerifyHashInCatalog+0x51
8e58b408 8c10fab0 CI!CipFindFileHash+0xab
8e58b4e4 8c10fecf CI!CipValidateFileHash+0x1d4
8e58b55c 82feec66 CI!CiValidateImageHeader+0x171

And as usual, no driver is traced as failing.

Still, update the display driver to NVIDIA DRIVERS GeForce 314.22 Driver WHQL and network driver to Win7 and WinServer 2008 R2 Driver, 4th one in the list.

And test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

One more ...... what made you think that I will understand it?

Bhai help karo please...

I did!