Keeps saying ntoskrnl

[Docthomas]

OK

10 month old system been very stable until last few weeks.
I am running Norton Internet security and I did isolate it as a culprit a few months ago after a forced update by NIS. this is different. before I go and abandon Norton again I wanted to post this.

frequent BSOD lately. Blue Screen viewer always includes ntoskrnl but it not always the only culprit. I have read that it is not always accurate and I can't find a way to repair it anyway.

I did run verifier but did it incorrectly and chose ONLY the ntoskrnl and it did a BSOD about 2 mins after I did a restart until I was able to quickly diable the verifier.

Current nvidia driver set did not work, so I DL'd the 266.77 set from a driver site. used driver sweeper to reinstall the newest drivers and no better.

current BIOS 1.F current on all drivers from MSI.
no overclocking. only adjustments to BIOS is recommended mods to have memory run at 1600.

I have not run memtest but again working system for 10mos. BSOD usually happens when clicking but will occasionally occur at random/idle.


I'd appreciate any help you guys can give me.
haven't removed NIS again yet but since I only have 30 days left in my year I will
be willing to look elsewhere but I'm not convinced that is the issue this time.

• CPU:

Manufacturer: AuthenticAMD
Description: AMD64 Family 16 Model 4 Stepping 2
Name: AMD Phenom(tm) II X4 955 Processor
Speed: 3200
_____________________________________________

• Installed RAM: 8190 MB

OCZ Obsidian 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model OCZ3OB1600LV4GK

_____________________________________________

• PC Info.:
MSI 790FX-GD70 AM3 AMD 790FX ATX AMD Motherboard

PC or motherboard model: MS-7577
System name: OFFICE-PC
System Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD
_____________________________________________

• Graphics:

Description:XFX NVIDIA GeForce GTS 250
Name: NVIDIA GeForce GTS 250
RAM: MB
Driver Date: 20110120000000.000000-000
Driver Version: 8.17.12.6677

_____________________________________________

• CD/DVD drives:

Description: CD-ROM Drive
Caption: TSSTcorp CDDVDW SH-S223Q ATA Device
Manufacturer: (Standard CD-ROM drives)

Description: CD-ROM Drive
Caption: HL-DT-ST DVDRAM GH22NS50 ATA Device
Manufacturer: (Standard CD-ROM drives)

 

[Maguscreed]

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000a0, Handle value being referenced.
Arg3: fffff9802c16ab30, Address of the current process.
Arg4: fffff800033a82e5, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  RivaTuner.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000355e3dc to fffff800030d3740

STACK_TEXT:  
fffff880`08dd73c8 fffff800`0355e3dc : 00000000`000000c4 00000000`000000f6 00000000`000000a0 fffff980`2c16ab30 : nt!KeBugCheckEx
fffff880`08dd73d0 fffff800`03573ae4 : 00000000`000000a0 fffff980`2c16ab30 00000000`00000000 fffff880`08dd74f0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08dd7410 fffff800`0332e030 : 00000000`00000000 fffff880`08dd7698 00000000`00000000 00000000`00000010 : nt!VfCheckUserHandle+0x1b4
fffff880`08dd74f0 fffff800`033a82e5 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`030cef00 : nt! ?? ::NNGAKEGL::`string'+0x20b4e
fffff880`08dd75c0 fffff880`0ae68fc1 : 00000000`00000000 fffff800`03073967 fffffa80`0729ce18 fffff880`00000011 : nt!ObReferenceObjectByHandle+0x25
fffff880`08dd7610 00000000`00000000 : fffff800`03073967 fffffa80`0729ce18 fffff880`00000011 fffff880`08dd7698 : RivaTuner64+0x1fc1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RivaTuner64+1fc1
fffff880`0ae68fc1 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  RivaTuner64+1fc1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RivaTuner64

IMAGE_NAME:  RivaTuner64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  469d14e6

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRFK_RivaTuner64+1fc1

BUCKET_ID:  X64_0xc4_f6_VRFK_RivaTuner64+1fc1

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

Seems to be blaming rivatuner to me.

 

[Docthomas]

Not sure how far back the BSOD util goes back but I have many in the last few days (dump files) this particlar incident you listed was during the BSOD fest after I ran verifier.

Riva was installed in the last 2 days based on a tip someone had given on another thread about slightly underclocking the GTS250. other than that it has not existed before 2 days prior. I can provide old dumps if needed.

 

[Docthomas]

I currently have verifier running and am awaiting another BSOD but we'll see. not sure how far back that utility goes into the old dump files.

 

[Maguscreed]

Every crash you had on 3/1 seems to be related to rivatuner.
until it's out of the way I don't think I can troubleshoot beyond it.

 

[Docthomas]

OK. I will uninstall and wait until the next BSOD? post then back to this thread?

thanks

 

[Maguscreed]

Yeah, go ahead and delete all the ones you have currently. They're already uploaded here anyhow.

 

[Docthomas]

OK,

running verifier. it will not start BSOD at usbfilter.sys

ideas? i can boot into safe mode and I'll post once I disable verifier again.
could this be the realtek drivers? or logitech keyboard?

currently verifier is off and computer is running. we'll see. nothing has changed except no RIVA. but it had issues before that.

 

[Docthomas]

OK ran great all night. came in this morning and another Blue Screen greeting me.

 

[Docthomas]

Still running when I left. I guess I'll pull all 4 reseat them and try again
Also they are rated at 1600 but run native @ 1066. Ran recommended bios changes from ocz. Could the tweaked bios settings be causing it. Been that way for 10mos?

 

[Maguscreed]

Memory does go bad, it happens. It can last a week or 15 years it's just the nature of the beast. My OCZ required me upping the voltage a bit higher than default, but this was just so it would run at the voltage it was designed to run at. I haven't experienced any problems because of it.

 

[Docthomas]

thanks. multiple errors when I returned home.

reset all BIOS to default no upped voltages. so far 2 of 4 sticks tested OK. About to pull those and test the next two 1 then the other.

 

[Docthomas]

bitter sweet. last chip I checked lit up like fourth of july.
I put the remaining 3 modules in and running memtest386+ again but I feel confident.

whew! now for an RMA to OCZ

 

[Maguscreed]

Yeah, definite failure there.
Is it still under warranty?
OCZ's rma process wasn't too bad if I remember it doesn't sound like you abused it at all, I just don't know the warranty on your RAM.

 

[Docthomas]

website says lifetime

OCZ Technology | Warranty

 

[Maguscreed]

yeah, just click the start a rma ticket. the only downside is if it was a matched set they may want you to return the set instead of just the one bad chip. for the rma, they'll just replace it with a new matched set though.