Blue screen error BCCode 1a

Question

Blue screen error BCCode 1a

Anonymous

random error have had others sometimes no boot at all started 10/dec/2014 help please

BCCode: 1a

BCP1: 0000000000041790

BCP2: FFFFFA8005107EF0

BCP3: 000000000000FFFF

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

4 answers

Answer 1

To be able to troubleshoot what might be causing your system to crash, we need the dump files. In an ideal situation, more than one file would be needed to establish a pattern so, if you do have more than one (preferrably, nothing over a month old), please upload them.

Please refer to the link below for steps to retrieve, zip and upload them to the file sharing site like onedrive, google's "dropbox, etc.

When you are done, make the folder public and share the link here.

Blue Screen of Death (BSOD) Created by ZigZag3143 (MS - MVP)

http://answers.microsoft.com/en-us/windows/wiki/windows\_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

Answer 2

Thank you to all for your help

I persevered and continued to search ... and found a way of diagnosing the error file and got it down to two things one was that it was explorer.exe corrupt or a Ram fail ... so remove all ram and cleaned the socket and fingers reinstall one piece at a time till BSOD .... now is working less two ram chips ....

in all it took 6 hours with no idea where to start now i think with the tools i have i can get it down to 2 hours ... lol

So thank you to all that have helped me ...

Answer 3

Hi,

Welcome to Microsoft Community Forum

I appreciate your efforts on getting this issue resolved and thank you for providing all the information’s.

BSOD Also known as the Blue Screen of Death or the Windows Stop Error, this screen image usually appears when a serious error occurred in your operating system. This majorly happens because of third party applications or driver software’s. If windows finds serious issue then it automatically gives you a BSOD just to protect itself from damage.

Please answer the following question for better understanding

What is the make and model of the computer?
Were there any recent changes made to the computer?

I suggest you to follow the below mentioned methods and check if it resolves the issue.

Method 1

Run a virus

This might happens because of malicious software, run virus scan and check if it fixes the issue.

http://www.microsoft.com/security/scanner/en-us/default.aspx

If the issue persists, follow method 2.

Method 2

Resolving stop (blue screen) errors in Windows 7

http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

Important: System Restore will not revert any of the non-system files like documents, email, music, etc. to a previous state. These types files are completely unaffected by System Restore. If your intention with this tool was to recover a deleted non-system file, try using a file recovery program instead of System Restore.

Important: While performing check disk on the hard drive, if any bad sectors are found, then check disk will try to repair that sector. Any data available on that sector might be lost.

Custom Install Disclaimer: If you don't format the hard disk during installation, data files are saved to a Windows.old folder on the partition you installed Windows 7. However, you should still back up the files. If you have data files that are encrypted, you might not be able to access them after installing Windows 7. If you've backed up your data files and then restored them after installing Windows 7, you can delete the Windows.old folder.

Hope this helps. Write to us for further assistance.****

Answer 4

debugging list hope this helps

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64

Loading Dump File [C:\Windows\Minidump\121514-68780-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred srv*DownstreamStore*http://msdl.microsoft.com/download/symbols

Symbol search path is: srv*DownstreamStore*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Machine Name:

Kernel base = 0xfffff80003a60000 PsLoadedModuleList = 0xfffff80003ca3890

Debug session time: Mon Dec 15 10:34:42.069 2014 (UTC + 11:00)

System Uptime: 0 days 0:20:33.896

Loading Kernel Symbols

.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

.......................................................

Loading User Symbols

Loading unloaded module list

........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

Followup: MachineOwner

5: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2

contains the address of the PFN for the corrupted page table page.

On a 32 bit OS, parameter 2 contains a pointer to the number of used

PTEs, and parameter 3 contains the number of used PTEs.

Arg2: fffffa8005d8a6f0

Arg3: 000000000000ffff

Arg4: 0000000000000000

Debugging Details:

BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff80003b46d50 to fffff80003ad5bc0

STACK_TEXT:

fffff8800e36df78 fffff80003b46d50 : 000000000000001a 0000000000041790 fffffa8005d8a6f0 000000000000ffff : nt!KeBugCheckEx

fffff8800e36df80 fffff80003aa6e75 : ffffffff00000000 000000002f99ffff fffffa8000000000 fffffa8018a67060 : nt! ?? ::FNODOBFM::`string'+0x35084

fffff8800e36e140 fffff80003dab05a : fffff8a018ab8060 fffff8800e36e480 0000000000000000 fffffa8018a67060 : nt!MmCleanProcessAddressSpace+0x679

fffff8800e36e190 fffff80003d8fb7d : 00000000c0000420 fffff8800e36ec01 000000007ef32000 fffffa8018c84060 : nt!PspExitThread+0x56a

fffff8800e36e290 fffff80003ac86fa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!PsExitSpecialApc+0x1d

fffff8800e36e2c0 fffff80003ac8a40 : 0000000018c6e0b0 fffff8800e36e340 fffff80003d8faf0 0000000000000001 : nt!KiDeliverApc+0x2ca

fffff8800e36e340 fffff80003ad4ef7 : fffffa8018a67060 000000007ef32000 0000000000000020 0000000000000020 : nt!KiInitiateUserApc+0x70

fffff8800e36e480 0000000076d811d6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x9c

0000000018c6e030 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x76d811d6

STACK_COMMAND: kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+35084

fffff800`03b46d50 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb

IMAGE_VERSION: 6.1.7601.18409

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+35084

FAILURE_ID_HASH: {f6a6ed79-e275-9f8c-d5a4-3a37a32b0b4e}