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

rslembo said:

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.

Good situation, and good plan :) When doing a clean install, follow it: Clean Reinstall - Factory OEM Windows 7

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

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

Code:

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

And that one is somehow old.

Code:

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 said:

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 Clean Reinstall - Factory OEM Windows 7. It works equally good with retail, too.

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.