Random BSODs on a brand-new PC (ntoskrnl.exe)

[rslembo]

Hi,

Bought a new computer a month ago, since then I've been having random BSODs from time to time, all related to the following: ntoskrnl.exe
Done fresh windows install twice, those BSODs keep coming after a while.
Recently updated bios, no results.
Already done some hardware tests, such as:

memtest86: running over 9 hours, no errors.
seatool: Seagate's HDD check, passed.
furmark: stressing the GPU, no problems.

I'm running Driver Verifier in the background, got 3 BSODs since that.
Razer DeathAdder mouse driver wouldn't let me go into Windows while being stressed by verifier (blue screen), so that's the only no-Microsoft driver that is not being stressed at the moment.
(Updated that driver too, the same happened)

Tried to analyse the .dmp files, but I guess I wasn't able to understand those.

Hope you guys could help me, as I've had enough trying to solve this by myself.

Thanks in advance!

 

[Arc]

Hello rslembo, disable driver now, 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.

Uninstall BitDefender. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[rslembo]

Hello, Arc.
Thanks for the reply.

I've just done the following steps as you suggested:

- Disabled Driver Verifier
- Uninstalled BitDefender
- Scanned with MSE
- Scanned with MBAM

No problems with those, system is clean.

However, I had another BSOD in the meantime:

MEMORY_MANAGEMENT
0x1a
ntoskrnl.exe+7efc0

About memtest86+, I've already done all those tests, with each memory stick separately in each memory slot.
I guess we can assume they're all OK.
But, just to be sure, I'll be doing all of them again from now on.

Additional information:

- Ran chkdsk c: /f /r with no problems related.
- Ran sfc /scannow as Windows found a problem on "NlsData0045.dll" and could not repair it.
- Did some hardware stress tests S&M and Prime95 with Hiren's Boot Mini XP, all ok

Any other suggestion so we can go further with the problem?
Thanks for the help!

 

[Arc]

Without seeing the data, I cannot say anything

 

[rslembo]

Arc, what else could I provide to you?

Left memtest86+ overnight with one stick at channel A1, no error reports.
I'll keep testing sticks and channels.

I'm attaching the last dump file about the MEMORY_MANAGEMENT yesterday.
Could you take a look at it?
Thanks!

 

[Arc]

Arc, what else could I provide to you?

Nothing but the data as per Blue Screen of Death (BSOD) Posting Instructions .

 

[rslembo]

Sure.
I'm without access to the computer ATM, sending you ASAP.

 

[rslembo]

Hello, Arc.
I'm back with the data.
Got'em attached.
Thanks!

 

[Arc]

Checked it all, but found nothing. According to the parameters of your data, I searched in MSDN library too, but got nothing helpful there, too.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
MEMORY_MANAGEMENT (1a)[/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
[COLOR=Red]Arg1: 0000000000005003, The subtype of the bugcheck.[/COLOR]
Arg2: fffff781c0000000
Arg3: 000000000001bfd1
Arg4: 0001bfcf00037ba2

Bug Check 0x1A: MEMORY_MANAGEMENT (Windows Debuggers) says, An unknown memory management error occurred.

What can I suggest you that, you rum memtest with all the sticks together, for 8 hours. If it comes free from errors, it is definitely being caused by a driver, and verifier is unable to catch it. In this situation, better you go for a clean install.

 

[rslembo]

Driver Verifier was unable to catch or was badly executed somehow? Should give it another try?
I'm still doing those memtest86+, almost finished one stick, no errors since.

Doing fresh Windows install when I backup the HDD data. Maybe today or tomorrow..

 

[Arc]

Driver Verifier was unable to catch or was badly executed somehow? Should give it another try?
I'm still doing those memtest86+, almost finished one stick, no errors since.

Doing fresh Windows install when I backup the HDD data. Maybe today or tomorrow..

Driver verifier is not badly executed, it found those parameters which are unknown, and so it is hard to determine the cause. Something somehow interrupting the memory for sure. If the RAM is not corrupted, it must be a driver. But due to the unknown nature, the driver is not being caught by the verifier.

Before doing the clean install, take a try, scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

If any of them can found anything.

 

[rslembo]

Scanned with both softwares above, just to be sure, system is clean.

Finished memtest86+ with the first RAM stick in every DIMM slot, no errors.
Testing last stick from today on.

No BSOD occurred since the last MEMORY_MANAGEMENT.
If happens again I'll post the dump file.

Intending to fresh install Windows later today.

Thanks, Arc.

 

[Arc]

Good situation, and good plan When doing a clean install, follow it: http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Actually it will give you a perfect reinstall, if you follow all the steps necessary for you.

 

[rslembo]

Arc, thanks for the guide!
I'll be doing it today, ran out of time yesterday.

However, got another BSOD by the morning, idle computer.
One I've never seen happening before, about:
KMODE_EXCEPTION_NOT_HANDLED
tcpip.sys

Do you know anything about this?
I'm attaching the data..
Thanks!

 

[Arc]

tcpip.sys is network related. A deeper search resulted in Atheros NIC driver. Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)

fffff880`031fe698  fffff880`0425d69eUnable to load image \SystemRoot\system32\DRIVERS\L1C62x64.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for L1C62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
 L1C62x64+0x769e[/COLOR]

And that one is somehow old.

fffff880`04256000 fffff880`04271000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Wed Aug 03 11:51:09 2011 (4E38E8D5)
    CheckSum:         0001CA6F
    ImageSize:        0001B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS Network drivers for Windows.

Let us know the results.

 

[rslembo]

My thoughts had gone straight to Atheros drivers.
That's an extreme coincidence as I've just downloaded it yesterday for Windows reinstallation.

Downloaded from Gigabyte. Driver date - 19/07/2012
Driver release from Atheros webpage above is kinda old, October '10

At fresh Windows install today, I'll be sure to install this one from the beginning.

Once again, thanks for all the help provided!

 

[Arc]

At fresh Windows install today, I'll be sure to install this one from the beginning.

Nice plan. A fresh clean install is always good
In this case, follow http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html. It works equally good with retail, too.

 

[rslembo]

Hello, Arc, I'm back.
Unfortunately, with bad results..

Fresh windows install.
New HDD. (Had to change it)

5 days running clean.. Until now.
I just had another BSOD.

Came home, turned PC on, Windows login: BlueScreen

Attaching new data.

Thanks..

 

[Arc]

Your crash dump is not showing any finite probable cause, but a stop 0xC2 is in general a driver failure. 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.

Let us know the results, with the subsequent crash dumps, if any.

 

[rslembo]

Few hours running Driver Verifier, another crash.
Now, MEMORY_MANAGEMENT as later times.

Data attached, hope it works this time..