Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



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

30 Jan 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by rslembo View Post
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.
If any of them can found anything.

My System SpecsSystem Spec
.

31 Jan 2013   #12

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
31 Jan 2013   #13
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
.


01 Feb 2013   #14

Windows 7 Ultimate x64
 
 

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!
My System SpecsSystem Spec
01 Feb 2013   #15
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
01 Feb 2013   #16

Windows 7 Ultimate x64
 
 

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!
My System SpecsSystem Spec
01 Feb 2013   #17
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by rslembo View Post

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.
My System SpecsSystem Spec
06 Feb 2013   #18

Windows 7 Ultimate x64
 
 

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..
My System SpecsSystem Spec
06 Feb 2013   #19
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
06 Feb 2013   #20

Windows 7 Ultimate x64
 
 

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

Data attached, hope it works this time..
My System SpecsSystem Spec
Reply

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





Thread Tools



Similar help and support threads for2: Random BSODs on a brand-new PC (ntoskrnl.exe)
Thread Forum
Random different BSODs, ntoskrnl.exe BSOD Help and Support
Random BSODs in brand new build BSOD Help and Support
Solved Random BSODs. Seems to be ntoskrnl.exe+7e569. BSOD Help and Support
Solved Random BSODs about once a day or so with ntoskrnl.exe and tcpip.sys. BSOD Help and Support
Random BSODs ntoskrnl.exe+26ee0 & ntoskrnl.exe+5063dc BSOD Help and Support
Random BSODs by ntoskrnl.exe BSOD Help and Support
Random BSODs ntoskrnl.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:41 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33