Windows 7: Random BSOD Windows 7

Simia · 06 Aug 2010

Hi,
i have problem with random bsod, they usualy appear while playing games or watching tv.

Things i tried:
- reinstalling system on different hard disk
- reinstalling graphics drivers
- updating bios
- increasing cpu voltage ( from 1.2V to 1.3V)
- changing windows power managment options

Memtest after 12hours was clean.

minidumps and everest pc report attached.

I would be gratefull for any help:>

Edit:
added some reports

ttran · 06 Aug 2010

Hi and welcome to SF friend!

Here are several things:
First of all, L1E62x64.sys was blamed in the dmp file. It is your Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20). Please download and install fresh copy of it.

nvlddmkm.sys was blamed. It is your nVidia Video drivers. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

Code:

BugCheck 1A, {41287, 0, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42be5 )
BugCheck D1, {59d67, 2, 1, fffff8800ff3d944}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ef944 )

BugCheck D1, {fffffa80302cd1d0, 2, 1, fffff88003a123bc}

Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )

Followup: MachineOwner
---------
BugCheck 50, {ffffe4801c82f250, 0, fffff880105c1f80, 7}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : hardware ( nvlddmkm+6eaf80 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff80002a9db63, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+163 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002b0e9be, fffff880009a9958, fffff880009a91c0}

Probably caused by : memory_corruption ( nt!MiZeroPageChain+d3 )

Followup: MachineOwner
---------
BugCheck D1, {28, 2, 0, fffff88001471c1e}

Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+76b8 )

Followup: MachineOwner
---------
BugCheck 50, {ffffffffe879cb99, 1, fffff8801000aebf, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+140ebf )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050031, 406f8, fffff88004420e48}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpInterruptReadComplete+348 )

Followup: MachineOwner
---------
BugCheck D1, {ffffef800f4a7144, 2, 1, fffff88003e7bb47}

Probably caused by : hardware ( USBPORT!USBPORT_TxCsqFindIrp+5b )

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

Do you have another graphic card that you can try on your system (borrow?)

Run system file check:

Quote:

Open an elevated command prompt and enter sfc /scannow.

Let us know if you need help

Tuan

Simia · 06 Aug 2010

Thank You for answer!
Both system file check and memtest(after 8 passes) came clean.
I've installed new drivers and now I hope to never see bsod again

I'll keep You informed:>

ttran · 06 Aug 2010

When did you do the memtest? What memtest? You gotta use memtestx86. 8 pass should take at least 8 or 9 hours my friend. Please use memtestx86 and test your Ram whenever you have time. That's critically important.

Regard,

Tuan

Simia · 06 Aug 2010

As i wrote in my first post i did it earlier. It took me 12 hours :P I've used Memtest86+ V4.10

Simia · 06 Aug 2010

ehh new drivers didn't help. New bsod just appeared. This is new one, or at least I don't remember having it earlier.

minidump attached.

ttran · 07 Aug 2010

Sorry the problem hasn't gone away. nvlddmkm.sys, your Nvidia graphic card driver is faulty and cause memory corruption. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

It can be driver or the device faulty. Let's reinstall the driver again.

Run this free video stress test:
Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

Quote:

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.689\080610-20982-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Aug  6 23:36:08.311 2010 (UTC + 7:00)
System Uptime: 0 days 1:57:40.277
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff8800fe0a358}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Regard,

Tuan
Use speedfan

Windows 7: Random BSOD Windows 7

Random BSOD Windows 7 problems?