Win 7 continually crashing

Hi,

I bought a new computer from a local store, I picked out the parts and had them build it for me. Since I got it home I've found that it continually crashes on me, sometimes to a BSoD, other times the screen just freezes and the audio loops. The crashes don't seem reproducible, I play world of warcraft on the computer a lot, so it appears to happen there mostly... But it will freeze just sitting on the desktop as well.

I took it back to them, they ran some tests and reckon it's a software issue. I got them to install a new cpu heatsink 'cos the SB was hitting 70 degrees C, the temp has now dropped back to more manageable levels, but I'm still crashing.

I'm just wondering if there's any tools I can use to try to isolate where the fault is occurring? I've tried using a program called "whocrashed", but it hasn't really helped me. It mostly gives me this description:
This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time

Any assistance would be greatly appreciated. The hardware specs are as follows:

• AMD Phenom II X6 1090T 3.20Ghz / 3.60Ghz Turbo Core, 9MB Cache, Six Core, Black Edition
• Asus CROSSHAIR-IVFORMULA, AM3, 890FX Chipset, HT5200, 4DDR3, 3PCIE, RAID, GBLAN, ATX, SATA3, USB3
• G.Skill 4GB (2x2GB) Kit, PC-12800 (1600Mhz), Ripjaws, 8-8-8-24-2N, Dual Channel Kit
• Western Digital 1TB, Caviar Black, SATA-III, 7200RPM, 64MB Cache
• Samsung 12X Blu-ray/DVD Combo Drive - 5.25" internal SATA, Blu-ray Reader & DVD Burner, Multi-format, Software, Retail Box
• Gigabyte Radeon HD5870 Overclocked (870Mhz), 1GB DDR5 (4800Mhz), PCI-E 2.0, Fan Cooled, D-Sub, DVI, HDMI
• Corsair CMPSU-850HX 850W ATX Power Supply, 140mm fan, Modular Cables, 80Plus Silver certified, Universal AC input 90~264V
• Samsung 23" Widescreen, Rose Black, Full HD 1920x1080p, HD Tuner, HDMI, Full A/V & PC Inputs, Dolby Sound, Speakers
• Logitech G19 keyboard
• CoolerMaster CM 690, ATX, No PSU.2 x USB2.0, Tool-free drive bays, Side Window

The system is running Windows 7 64bit Professional, AVG free anti-virus, Zone-alarm firewall.

DxDiag produces this result:

Thanks all

 

Here are a few things to try:

Go to www.ati.com; download and install the latest Windows 7 64-bit driver for your 5870 video card. Windows Automatic Updates doesn't always catch ATI driver updates; an outdated video card driver can sometimes cause a Blue Screen of Death.

Since you said it's a new custom-built PC, download and run MemTest.

http://majorgeeks.com/MemTest_d350.html

Although I can't find reviews on your specific G-Skill RAM, some of the reviews on their 4GB stick at NewEgg.com seem to indicate it doesn't work well on some AM3 boards. If you get a bad memory report from MemTest it could either be a defect or incompatibility. If this is the case, I'd contact the store that sold/built it and see if you can exchange the G-Skill for a brand/model that's on the approved (tested) memory list provided by ASUS.

Hope this helps.

 

Thanks for your reply gman863.
I updated the video card drivers and ran the memory test. Memtest ran to about 350% without an issue and the system seemed to be running fine for the last week or so... Then it started crashing again. :cry

Appreciate the assistance, any other tricks in your hat?

Thanks

 

How about uploading some of the most recent minidumps? This might enable us to pinpoint what happened immediately before and during the BSODs. Go to Windows > Minidumps and copy say 4 of the most recent dumps to the Desktop, zip and attach them here. How to set Windows to create minidumps.

 

Minidump zip attached. Although it looks like the last one was at the start of this month...

Thanks

 

Uninstall RivaTuner, it has known issues with W7. AVG has been known to cause problems with W7-64bit (this has been fixed, so they say) I'd uninstall it, too - use Avast!, Avira or MSE.

I'll do a debug next, you uninstall those 2 first.

 

Those 4 minidumps were all from January, are there any later ones? Have you checked that Windows is currently set to save minidumps? Note: Windows cannot save dumps unless there's a swapfile on the System partition.

All dumps pinpointed NetIO.sys as being at fault, I think this is very unlikely, if it's the original unadulterated file.

Code:

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002c91b2f

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c86ca9 to fffff80002c87740

STACK_TEXT:  
fffff880`0308dd68 fffff800`02c86ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0308dd70 fffff800`02c85172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0308deb0 fffff800`02c91b2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`06057fc0 fffff800`02c8cda7 : fffff880`06058180 fffff880`060581a0 00000000`00000001 00000000`00000000 : nt!SepMandatoryIntegrityCheck+0x4f
fffff880`06058040 fffff800`02c4ff6a : fffffa80`072eb8f0 00000000`00000001 00000000`00000000 fffffa80`04a057c8 : nt!SeAccessCheckWithHint+0x317
fffff880`06058120 fffff880`01406c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`06058810 fffff880`0140494f : 00000000`c0000022 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`06058880 fffff880`014069b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!MatchValues+0xef
fffff880`060588d0 fffff880`01406845 : fffffa80`05cd2310 fffffa80`06935f30 fffff880`06058af8 fffff880`06059230 : NETIO!FilterMatch+0x95
fffff880`06058920 fffff880`01407ccb : 00000000`00000000 00000000`00000000 fffff880`06059230 fffff880`06058ae0 : NETIO!IndexListClassify+0x69
fffff880`060589a0 fffff880`0163d417 : fffff880`06058e78 fffff880`06058e78 fffff880`06059bb0 fffffa80`06843260 : NETIO!KfdClassify+0xa4e
fffff880`06058d10 fffff880`0163683e : fffff880`01745690 00000000`00000000 fffffa80`066a57a0 00000000`00000000 : tcpip!WfpAleClassify+0x57
fffff880`06058d50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!CompareSecurityContexts+6a
fffff880`01406c5a 448b442470      mov     r8d,dword ptr [rsp+70h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4bbe946f

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

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

5: kd> lmvm NETIO
start             end                 module name
fffff880`01400000 fffff880`01460000   NETIO      (pdb symbols)          c:\symbols\netio.pdb\8422557063CC44C8B9525A086FA98C032\netio.pdb
    Loaded symbol image file: NETIO.SYS
    Mapped memory image file: c:\symbols\NETIO.SYS\4BBE946F60000\NETIO.SYS
    Image path: \SystemRoot\system32\drivers\NETIO.SYS
    Image name: NETIO.SYS
    Timestamp:        Fri Apr 09 03:43:59 2010 (4BBE946F)
    CheckSum:         0005CFA1
    ImageSize:        00060000
    File version:     6.1.7600.16569
    Product version:  6.1.7600.16569
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     netio.sys
    OriginalFilename: netio.sys
    ProductVersion:   6.1.7600.16569
    FileVersion:      6.1.7600.16569 (win7_gdr.100408-1504)
    FileDescription:  Network I/O Subsystem
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

Ah, I just reread the original Post, uninstall ZoneAlarm, that's most likely to be the real trigger for it!

 

Uninstalling AVG now... I can't find RivaTuner in my uninstall list... What is it? Is it part of another program?

That's worrying.
Can you recommend any good free firewalls for me to replace it with? I've always used Zonealarm on all my computers... I think I'd be lost without it.

Thanks

 

Some recommended firewalls here.

The RivaTuner file is also part of EVGA Precision/MSI Afterburner software, uninstall it - it's from 2005 and a known cause of problems in W7.

 

Everything seems to be working fine now.
Looks like the culprit was indeed Zone Alarm.

Thanks for everyone's assistance

 

Thanks for the feedback, good result