Solved BSOD instantly after a fresh recovery, bug check code 0x0000001a

[tamoor]

Hello,

This is my first post on this forum.

After spending hours online on these BSODs, I finally decided to spit the error out somewhere since BSOD can occur out of nowhere and situation is different for everybody.

My friend and I bought Asus N55 and N56VM on 27th Feb 2013 respectively. Unfortunately, after a few updates, I got BSOD on the very first day. I've had Vaio F113fx/b before and never experienced this kind of situation before.

After days of trials on figuring out problem and experiencing BSODs 3-4 times a day on average, I planned to recover the Windows from the DVD backup I'd made. Yesterday, after a fresh recovery (factory default settings) a Asus critical update prompted and I gave it permission for so. Right after the update installed, boom, had a first BSOD on 'Memory Management 0x0000001a".

After a restart at around 10:53PM, situation seemed normal so I left my laptop ON for a night. Today, I found my laptop shut down. On restart, found that it had BSOD of "KMODE_EXCEPTION_NOT_HANDLED 0x0000001e".

I installed BlueScreen Viewer to find out what was causing these BSODs and same as before, it's ntoskrnl.exe.

I've attached minidump files in an attachment. Please help me! I'm worried, does that really happen with new laptops?

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[URL="http://www.carrona.org/bsodindx.html#0x0000001E"]BugCheck 1E,[/URL] {ffffffffc0000005, fffff800038ccf94, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[URL="http://www.carrona.org/bsodindx.html#0x0000001A"]BugCheck 1A[/URL], {41790, fffffa8000882900, ffff, 0}

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

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

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[tamoor]

Sorry for the late reply. I tried upgrading to Windows 8 to avoid any software related issues. Situations is much smoother now in a way that BSODs now occur after every 4-5 hours instead of occurrence at every hour.
However, I ran memtest86+ 4.2 ver last night and found thousands of errors at test#2.

I can't really check RAMs from the slots because I bought this laptop 3 weeks ago and opening its casing would void the warranty (i think).
P.S: N56VM has a single case structure on its bottom unlike slots for hardware components.

 

[VistaKing]

Hi Tamoor

To get the memory fixed you would have to open up an RMA with Asus letting them know you have a bad Ram . You might loose warranty if you do open the bottom to get to the RAM due to opening up the entire bottom to get to the memory .

   Tip

Before you send your laptop to Asus backup your files . Knowing OEM companies they like to reimage laptops when they work with them

 

[Arc]

Sorry for the late reply. I tried upgrading to Windows 8 to avoid any software related issues. Situations is much smoother now in a way that BSODs now occur after every 4-5 hours instead of occurrence at every hour.
However, I ran memtest86+ 4.2 ver last night and found thousands of errors at test#2.

I can't really check RAMs from the slots because I bought this laptop 3 weeks ago and opening its casing would void the warranty (i think).
P.S: N56VM has a single case structure on its bottom unlike slots for hardware components.

Dont take a risk.

As you are getting errors in memtest, the RAM is corrupted for sure. For a new computer, for new RAMs, slot by slot testing is not necessary, as you will get the replacement.

Let us know the results with the replacement RAMs.

 

[tamoor]

Problem Presisting!

Hey,

I had sent my laptop for a repair from ASUS and there was indeed a problem with RAMS. They even replaced the Mainboard.
However, the same day after receiving the laptop, it started turning off without giving any BSODs. I reckoned it had loose connection or something so sent it back again.
This time, they changed the mainboard again and here I am after almost a month from the same laptop.
I received laptop yesterday and it has been working flawless until today when it gave me BSOD for "DRIVER POWER STATE FAILURE". I have attached the dump file in an attachment.

Please help. This is getting seriously annoying now. It has been sent for repair two times now.

 

[Arc]

The problem is your network dongle related, apparently. But for the most precise suggestions, we need to have a look at your msinfo32 file. upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[tamoor]

Hey arc,

I haven't experienced any BSOD after last night. I forgot to mention that just before the BSOD, I noticed that my icon that shows availability of internet stopped working. It didn't respond even if I clicked it.
It all seems to work fine now.

However, I've attached the .info file in an attachment.

Thanks.

 

[Arc]

Very good to know.

Make it sure that the following drivers are up to date:

1. Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20): ATHEROS drivers for Microsoft Windows (Atheros?????)
2. Atheros AR9485WB-EG Wireless Network Adapter: Drivers for Atheros AR9485WB and Windows 7

And, if Bluetooth is not necessary, disable it. Probably the unaccessable network icon in the notification area is caused by bluetooth.

Let us know the updated news

 

[tamoor]

Solved!

Thanks guys!

Laptop seems to work flawlessly now. Been three days and its running without any sign of BSODs. I couldn't find updated driver for Ethernet. However, I updated Wireless Adapter.

I would try to keep my laptop up to date to avoid any crashes.

Thanks again.

 

[Arc]

Good to know

For any further issue, Please us know here: BSOD Help and Support - Windows 7 Help Forums