Hi,

I've recently built a new PC (see specs in signature) which freezes/BSODs once in a while and I can't figure out what the problem is. The PC runs fine for several days and out of nowhere (maybe!) it BSODs or freezes. I can't make any sense out of the minidump files (even after running them thru Windows debugging tools) so I'm hopping that someone can point me to the right direction.

The PC is not overclocked, everything is running at stock rating except for the memory which I bumped the voltage from the rated 2.1v to 2.2v and reduced the rated timing from 5-5-5-15 to 5-7-7-16 because I'm using all 4 mem slots (so I read somewhere). Running the 8Gb at rated settings causes memtest86+ to error every time on test 5.

Anyway, memtest86+ runs without error for 8+ hours, P95 runs for 12+Hours with no error and windows memory also runs fine, all the temps a within range (CPU at 32C idle, 45C in load).

I noticed that the PC freezes when using Skype+video web cam and BSODs when encoding DVDs using ConvertXtoDVD (could be coincidence!). Having said that, I maybe talking on skype for hours while encoding DVD without problem for a few days and the next it would freeze or BSOD within 2 hours. At night I put the PC in sleep mode (I rarely turn it off).

The PC was OC'ed but because of the problems I set everything back to stock rating with the same issues.

Attached are the last 3 minidump for whoever would be so kind to help me out. Unfortunately the dmp files are bigger than 200k so I had to zip them.

Thanks

Attached Files

Minidumps.zip (70.5 KB, 1 views)

One error is 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

Another is 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.


The first cited the driver aswMonFlt.sys and the second aswFsBlk.sys and both belong to Avast.

The third is 0xA and these are strong indications of hardware issues but sometimes it can mean a driver is attemption to access an IRQL it has no right doing so.

This one cited memory corruption. Avast is a very stable software. It could be the way the memory is configured or a bad stick might have passed memtest. As good as this test is, bad memory has been known to pass it.

Thanks Route44 for a quick reply. Here are the 2 errors I get in the system event

\??\C:\Windows\SysWow64\drivers\TVicPort.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number.

I've searched TVicPort.sys but could not come up with anything really meaningful and I don't don't know where it came from. Is it part of Windows?

Thanks

I think I found what TVicPort.sys is. It must have been installed with memset (which is installed on my PC). Since I don't use I'll uninstall it and see what happens.

Memtest would not install this driver. It is a stand-alone test

TVicPort is a generic device driver for Windows 95/98/ME/NT/2000/2003/XP/XP64
Description: TVicPort Driver for Windows NT/2000/XP
Company: EnTech Taiwan