new htpc getting daily BSOD

[JayHobson]

I finished building this computer about a month ago. All components are new. Intel dh67bl mb & i3 2100t, using built in video & sound. Have ceton quad tuner, antec earthwatts 380w psu, WD caviar 2tb sata hdd, 2x4gb corsair 1333mhz ddr3 running Windows 7 home premium 64 bit SP1.

I'm getting daily BSOD. Generally, the only thing running is WMC and avast. This latest BSOD happened with WMC gadget running along with IE while trying to set up an account for this forum.

I've updated the box with the latest changes to windows 7. Drivers for the mb are downloaded from Intel and running the latest versions. Ceton card has latest firmware & drivers. None of the drivers seem to be helping matters.

The system shows the following information about an unexpected shutdown. Don't know if this will add anything to help:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041201
BCP2: FFFFF6800004B538
BCP3: A08000005AAFC867
BCP4: FFFFFA800AF2F3E0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\031912-12214-01.dmp
C:\Users\Jay\AppData\Local\Temp\WER-34616-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

It is acting better than my previous htpc which was using some older hardware recycled from a Intel quad core 6400 box. That one was using the HDD, Ceton & OS. It locked up each day after only a few hours of being idle.

 

[zigzag3143]

Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

 

[JMH]

These crashes were caused by memory corruption/exception (`c0000005) (probably a driver).
Please run these tw o tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[JayHobson]

Switched out avast with MS Essentials antivirus. BSOD is still happening. It even happened as I tried to uninstall avast. The frequency varies between ~ 6 - 30 hours.

Been running memtest86 on the system for part of the morning so far. It has finished 3 passes with no errors and been running for nearly three hours so far.

The system is not overclocked, never has been. As far as I know, I have all the latest drivers. The mb does support raid. I'll check and see if there is a separate driver for it that didn't get downloaded when I pulled everything down from Intel a couple weeks back.

An interesting issue happened this morning that I haven't seen this machine do so far. When I turned it on, the image from a TV show was frozen on the screen. WMC wouldn't respond to any mouse input. It seemed like the system was locked up. I didn't think to Ctl-Alt-Del and see if I could break it loose that way, I just put the memtest disk in and pushed the reset button.

Thanks for the help. I'll continue with the memory test for awhile, and see about the drivers afterwards. Any additional suggestions would be great.

 

[writhziden]

Let us know the results memtest86+ first. Then we can proceed with further troubleshooting. Due to the hard reset, I would suggest you check for file system corruption on your hard disk:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

 

[JayHobson]

I let memtest86 run through 9 passes and there were no errors. I also found that I had some old drivers for the mb, so I've installed some of them, including the HDD controller, sound driver, and a couple others. The system ran fine for awhile, but sometime overnight crashed again. I've run the BSOD tools again, and have included another dump. Hopefully this one narrows down the issue a bit more, as the only thing that should have been running is WMC. I think that I also mentioned that I switched out avast for windows essentials antivirus.

 

[writhziden]

Problem Devices:

aswSP	ROOT\LEGACY_ASWSP\0000	This device is not present, is not working properly, or does not have all its drivers installed.
avast! Network Shield Support	ROOT\LEGACY_ASWTDI\0000	This device is not present, is not working properly, or does not have all its drivers installed.
aswRdr	ROOT\LEGACY_ASWRDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.

There are still remnants of avast! on your system. Did you use the avast! uninstall utility? If not, uninstall Microsoft Security Essentials through Start Menu -> Control Panel -> Uninstall a program. Re-install avast!. Then remove avast! with its uninstall utility. Then replace with Microsoft Security Essentials.

 

[JayHobson]

ok. I got rid of ms essentials, reloaded avant, uninstalled it, and reinstalled ms essentials anti virus again. Was hoping that it would fix the problem, but got another bsod after only a few more hours. Since I'm not convinced that I got everything cleaned out, I decided to reinstall the OS. Since I barely have anything installed, it seemed easiest to do that to ensure that I had no leftovers from avant.

I also installed the latest drivers that I downloaded from Intel directly from a CD I burned, so I didn't install old versions of them first. I installed MS anti virus, and have let the system do an update of all of the important items. The system ran fine for 20 hours, but just had a bsod. I was having WMC change the channel when it happened. I had changed the channel many times since I completed the build.

Interesting thing in the perfmon output is that the antivirus still does not appear to be activated.

Two things that may be issues. There was one PCI controller that didn't get a driver installed. There didn't appear to be any way to update the driver manually, but I was able to have windows 7 find the driver for it online.

Additonally, I have not tried to update the BIOS on the MB yet. I haven't checked to see what version it is, but don't know if that could be contributing to the problem.

Thanks for all the help so far. I'm hopeful that this latest reinstall of the OS will make things easier to review and debug as there is less stuff installed.

 

[writhziden]

The perfmon report often gives erroneous messages regarding system security. I wouldn't worry about that.
Security Software (this is to check that you do have security software installed and it is working properly; nothing needs to be done with this at this time):

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	1008	8	200	1380	3/25/2012 4:13 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2600	8	200	1380	3/25/2012 4:13 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2356	8	200	1380	3/25/2012 4:13 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Loading Dump File [D:\Kingston\BSODDmpFiles\JayHobson\Windows_NT6_BSOD_jcgriff2\032512-17300-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c650
Debug session time: Sun Mar 25 17:12:10.693 2012 (UTC - 6:00)
System Uptime: 0 days 14:46:21.552
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002caa460}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002caa460, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb6100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02caa460 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88003c12660 -- (.trap 0xfffff88003c12660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000000050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002caa460 rsp=fffff88003c127f0 rbp=fffffa8000ece740
 r8=fffff80002eb9500  r9=fffffa80065fa000 r10=fffffa80065fa980
r11=fffff880009ea180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiReplenishPageSlist+0xc0:
fffff800`02caa460 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:a180:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c842e9 to fffff80002c84d40

STACK_TEXT:  
fffff880`03c12518 fffff800`02c842e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03c12520 fffff800`02c82f60 : fffff880`009ea180 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03c12660 fffff800`02caa460 : 00000000`00000000 00000000`00000001 00000000`13bd0000 fffff800`00040001 : nt!KiPageFault+0x260
fffff880`03c127f0 fffff800`02ca8c1f : fffffa80`065fa960 00000000`0000003c fffffa80`01759740 00000000`0000003c : nt!MiReplenishPageSlist+0xc0
fffff880`03c12860 fffff800`02c92254 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`03c12980 fffff800`02c82e6e : 00000000`00000001 00000000`13cdf000 fffffa80`07185901 00000000`13bd0040 : nt!MmAccessFault+0x1224
fffff880`03c12ae0 000007fe`ffad58e3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`021ee368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ffad58e3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02caa460 f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

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

Points to memory problems...


Recommend running one of your 4 GB modules at a time and doing your normal routine. See if one of your RAM modules is faulty. Memtest86+ does not always catch faulty RAM modules if they are just beginning to fail. Avoid Static Damage to Your PC when swapping modules.

Run each module in each slot. Try to find a good module and a good slot. Once you have a good module, test the other slots to determine whether there are any bad slots. Test all modules in a known good slot to determine whether there is a bad module.