📎 AI Summary:
The thread discusses a user's recurring blue screen errors on Windows, suspected to be caused by disk issues, viruses, or faulty hardware. The user has followed troubleshooting steps like reinstalling Windows and running system scans but encounters persistent problems with corrupt system files and the DISM command. The overall sentiment indicates ongoing frustration but helpful assistance from others, guiding the user through diagnostics, system file repairs, and hardware checks to resolve the issue.
T

TAHIR MEHMOOD

New Member
Member details
Joined
Sep 2, 2014
Messages
10
Thread Author #1
hi
please I need some help here,i am getting these blue screen, I think I had a virus because i installed a fresh copy of windows not a week long. I am doing nothing when i got this blue screen.
please help

Tahir Mehmood
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa80048e5078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c830 )

Followup: MachineOwner
Hi,
the above bugcheck along with this error code:
Code: 
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

Means...
Sort by date Sort by votes
T

TAHIR MEHMOOD

New Member
Member details
Joined
Sep 2, 2014
Messages
10
Thread Author #2
hi
please I need some help here,i am getting these blue screen, I think I had a virus because i installed a fresh copy of windows not a week long. I am doing nothing when i got this blue screen.
please help

Tahir Mehmood
 

Attachments

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#3
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa80048e5078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c830 )

Followup: MachineOwner
Hi,
the above bugcheck along with this error code:
Code: 
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

Means there was a problem with the disk being accessed. This could be down to faulty or loose cables so please check all connections.

Other possible causes for this Bugcheck can be viruses or faulty RAM.

As specified above please check cables and connections. If the bsod persists run a chkdsk. This link describes how to run chkdsk:
Link Removed

Your also missing a Service pack. Please download SP1 here:
Link Removed

Any issues installing the Service pack could mean you need the update readiness tool:
Link Removed

Install MSE and check for viruses:
http://windows.microsoft.com/en-GB/windows/security-essentials-download
Check for malware with Malwarebytes:
https://www.malwarebytes.org/

e1c62x64.sys Tue Dec 21 09:30:56 2010: Intel(R) 82579V Gigabit Network Connection driver. 2014 update on motherboard support page. Please apply any updates that relate to your machine (pretty much all of them. 🙂 )
Link Removed

RTKVHD64.sys Tue Jan 25 10:38:43 2011: Realtek HD audio driver. See above:

xusb21.sys Sat Feb 17 02:43:15 2007: XBox USB wireless controller please update:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Post any new dump files.
 
Upvote 1 Downvote
Solution
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#4
Didn't you get me message about your original post? I moved it to it's own thread.. See above.
 
Upvote 0 Downvote
T

TAHIR MEHMOOD

New Member
Member details
Joined
Sep 2, 2014
Messages
10
Thread Author #5
thanks for the reply
i did all except Memtest86, no blue screen up till now but i have a problem in sfc scan. It always said that unable to fix corrupt file, what should i do?
 

Attachments

  • CBS.zip
    CBS.zip
    205 KB · Views: 216
    Microsoft Defender: No threats detected Scan details
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#6
Code: 
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-09-05 09:12:44, Info                  CSI    000002f0 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-09-05 09:12:44, Info                  CSI    000002f1 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-09-05 09:12:44, Info                  CSI    000002f2 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-09-05 09:12:44, Info                  CSI    000002f3 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-09-05 09:12:44, Info                  CSI    000002f4 Hashes for file member \??\C:\Windows\SysWOW64\en-US\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-09-05 09:12:44, Info                  CSI    000002f5 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-09-05 09:12:44, Info                  CSI    000002f6 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted

Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Opn the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#8
You must follow how I've written the above command exactly. Easiest way is to open an admin command prompt (has to be admin otherwise won't run) and then copy and paste the command from above.
 
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#11
Hmm... could you run the SFC again please and perform a chkdsk:
Link Removed
 

Last edited:
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#13
Hi Tahir,
did you install the latest service pack?
The file that is corrupted is quite important and has to do with system stability. How is the machine running currently?
 
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#16
Well... see how you go and if issues return post back. I would also consider re-installing Windows at some point in the future (don't for get the service pack).
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#18
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0000001, {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+26c6e )

Followup: MachineOwner
Hi again,
the above Bugcheck is specifically for AMD drivers only and can mean either the device isn't getting enough power from the PSU or the driver is corrupt. If your overclocking the card then return to default values.

atikmdag.sys Sat Jun 21 03:36:23 2014: Please update to the latest 14.9 AMD driver:
Link Removed

If your still getting issues just check the card with this test:
Link Removed

Post any new dump files.
 
Upvote 0 Downvote
You must log in or register to reply here.