BSOD at seemingly random times

[racie]

A few months ago, I received a computer secondhand, so I wiped it and installed Windows 7. Now it occasionally BSODs at random times. Sometimes it is when I have already been using the computer for some time, and sometimes it is before Windows is able to fully start up. I cannot discern a specific event or action that I am doing to trigger this. It seems to happen when the computer is left alone for a while.

My Google-Fu has told me that it might be the driver "ntoskrnl.exe," but I'm not sure and I don't know how to fix that. The stop codes have been 1A and 1E.

BSOD popup info from latest crash:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002B08F60
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

.dmp files are included in a .zip as well as other diagnostic files retrieved from SF diagnostic tool.

 

[HarriePateman]

The BSOD reports a memory corruption.

BugCheck 1E, {c000001d, fffff88000d7cc00, fffff88009e32bc0, 0}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

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

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

If there is no error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

   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.

 

[racie]

Thanks, HarriePateman. I ran Memtest86+ overnight and it went through 12 passes with 0 errors. I then tried driver verifier. Nothing happened for a long time, but then I got a different BSOD: C1. Apparently the solution to this problem is to "obtain a backtrace of the current thread. This backtrace will usually reveal the source of the error." I have no idea what this means. :/

Here is the dump file. I am still unable to determine the exact cause.

It may be worth noting that I noticed my speakers were unplugged. Right when I plugged them in, the computer gave a BSOD. It kept restarting and would not turn on. I left it off for five minutes and it turned back on. I have NOT been able to replicate the BSOD by plugging in and unplugging the speakers. They work fine now.

 

[Golden]

fffff880`07361230  00000000`00000000
fffff880`07361238  fffff880`03a32a77Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for [B][COLOR="Red"]aswSnx.SYS[/COLOR][/B]
 aswSnx+0x2ca77
fffff880`07361240  00000000`00000000
fffff880`07361248  00000000`00000000

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9801d664ff0, fffff9801d664800, f90010, 32}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff80002cc4000
THREAD fffffa80078ac940  Cid 0574.0758  Teb: 00000000fff6b000 Win32Thread: 0000000000000000 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffff9801ec42c10
Not impersonating
GetUlongFromAddress: unable to read from fffff80002c03ba8
Owning Process            fffffa80076b4b30       Image:         [B][COLOR="red"]AvastSvc.exe[/COLOR][/B]
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data

Uninstall Avast and replace it with MSE. Reboot and use computer as normal.....if you get more BSOD's, upload them here.

 

[racie]

Huh, thanks. An edition of Avast was giving a different computer BSODs until I downloaded the old installer. I wonder why Avast seems to have these issues.

If you don't mind me asking, how were you able to get detailed info on the bluescreen? I was using bluescreenview and it didn't show anything too detailed, like being about Avast or anything.

 

[Golden]

Bluescreenview is inadequate for diagnosing BSOD's....if often highlights what modules were affected by the crash, but not the cause. Proper BSOD diagnosis is done using WinDBG, this is what I used to locate the cause of the BSOD's.

 

[HarriePateman]

That you for following this up Golden, i was sleeping