NEW asus system COMPLETE random bsod

ok i just ran drive verifier again and have a video running about 10 minutes in the video is running SUPER slow still hasnt frozen but to answser the instantaneous question it looks like its a little less than instant

now the video has slowed to a crawl 1fpm id guess but the system is still responding

Ok, and just to make sure I'm completely understanding things here, this does NOT occur when Driver Verifier is off, correct? You can check if DV is on or not by either going into command prompt and typing verifier /query or opening DV up as normal and clicking "Display existing settings" then Next. If it shows a list of drivers and it shows checks are enabled, then it's obviously on.

The freezing thing when DV is on kinda puts a big damper on our endeavor to find cause for this, as it's rather crucial in making sure the system BSODs when the culprit is causing the problem and not afterwards. Without those crashdumps we're kind of at a loss.

The only other option I have for gettin more info on this besides DV is to have it crash one more time and then send us the MEMORY.DMP file located in your Windows directory. It'll compress heavily in a zip, rar or other archive variant, but it'll still be too big here. Upload to a 3rd-party filesharing site and I'll have a look at it to see what I can come up with, but I can't guarantee I'll find something conclusive (better than nothing, though). Make sure to explain when the crash occurred and what the PC was doing at the time.

While we're working on figuring it out through this route, you can run some more hardware tests. Have Prime95 going on Torture Test on Blend settings overnight. Then follow that up with another overnighter but on Large FFT settings instead. If your system crashes during any of the runs, send us the crashdumps (minidumps might just be fine here, no kernel dump from MEMORY.DMP). If a test fails in Blend but not Large FFTs, you have most likely a motherboard/RAM issue. If test fails on Large FFTs but not Blend, most likely an internal CPU failure. If it fails on both, it can be anything but most likely bad CPU.

As for it being a GPU problem here, can you try a beta version of the driver, or perhaps a rollback? Also, if you have onboard graphics controller on your mobo, you can try switching to that to see if things stabilize. If they do, it's a driver bug or a graphics card problem. Or if you have a different video card you can swap that in and try that a bit to see how things go.

It may very well be the graphics card, which isn't a rare issue as it's always possible to get a dud piece of hardware for a new system. Nevertheless, unless you're willing to go the caveman route and start swapping hardware, it's cheaper to try and get more info on this and analyze it further than to go off buying more stuff.

Hmm, strange, NDIS driver shouldn't be on that list. However, I do notice USBFilter, which is also a driver I saw in one of your crashdumps. That's an outdated (pre-Windows 7) driver that's a gimmick driver, designed to "enhance" USB performance. All I see the potential from it is a cause for instability. Probably will want to remove it or rename it to like usbfilter.sysbak) and test how your system works out afterwards.

Vir Gnarus said:

Hmm, strange, NDIS driver shouldn't be on that list. However, I do notice USBFilter, which is also a driver I saw in one of your crashdumps. That's an outdated (pre-Windows 7) driver that's a gimmick driver, designed to "enhance" USB performance. All I see the potential from it is a cause for instability. Probably will want to remove it or rename it to like usbfilter.sysbak) and test how your system works out afterwards.

i only selected non windows drivers... i will double check the ndis driver. and try removing the usbfilter driver once i complete the prime95 big FFT test

I just noticed your post about DV causing extreme video output slowdown. Was everything else on Windows responsive?

Part of me really wants to do a manual crash here. If you can get it to manually crash using this method while you're experiencing that extreme video sluggishness, and send us a MEMORY.DMP of that, perhaps we might have the information we seek.

As for video playing, have you used various video players: VLC, Media Player Classic, Windows Media Player, etc.? Ensure that the video playback problem isn't something specific to one player but occurs with multiple.

Vir Gnarus said:

I just noticed your post about DV causing extreme video output slowdown. Was everything else on Windows responsive?

Part of me really wants to do a manual crash here. If you can get it to manually crash using this method while you're experiencing that extreme video sluggishness, and send us a MEMORY.DMP of that, perhaps we might have the information we seek.

As for video playing, have you used various video players: VLC, Media Player Classic, Windows Media Player, etc.? Ensure that the video playback problem isn't something specific to one player but occurs with multiple.

so should i stop the prime95 testing and try for the manual crash? and if so i will want to do this while the dv is on correct?

as far as video playback i have only played through windows media player. but i can add vlc and classic to try them as well

It's probably best to run Prime95 when the system is idle overnight. But yes, I'd prefer the manual crash at the moment.

ok ill get on it

Vir Gnarus said:

I just noticed your post about DV causing extreme video output slowdown. Was everything else on Windows responsive?

yes everything else seemed fairly responsive