BSODS are a joy?~

[Goomba81]

Yo~!I've recently built a system for a mate.
specs are as follows:
Core i7 860
Gigabyte P55-UD4P mobo
4x2Gb DDR3 2000 G.Skill Trident
Atec EW 750W
WD 800 GB Sata HDD
Nvidia GTX 275
running it on my LG full HD screen
logitech dinovo bluetooth set.

It's been crashing non stop. I've ran Windows mem diagnostics and initially a hardware fault was detected. So following their trouble shoot i removed the ram and blew out the slots... reinstalled and reran. 3 x 3passes (at extended test mode) later, all results were clear. I ran the Western digital HDD full diagnostics software... and that passed also.
after the 5th reformat everything seemed fine. It was running smooth for about half a day and then BSODS started occurring... usually after major Mouse lag.
now AVG displays an unknown error everytime i boot up.

I've attached the minidumps... hope that helps.

 

[torrentg]

Hello. There are no attachments but you will save yourself major troubles by uninstalling AVG. If you don't want to, that's your call. I couldn't recommend it any more strongly though.

Attach a dump and we can look at it for you.

 

[Goomba81]

joy.. i fail at failing.. minidumps uploaded.. ta. AVG is gone.

 

[torrentg]

Enjoy your pc then.

"AVGIDSFilter.sys" is your cause.

If you run into more bsod, let us know by posting it and after updating EnergySaver "des2svr.exe" application. Or hang around and tell us how it's going.

 

[Goomba81]

thanks torrentg. u're a champ. love ya work. zero crashes since.

 

[torrentg]

You're welcome. Many users having trouble with that app. I've been calling it the internet's worst.

 

[Goomba81]

just an update on the bsods. everything was fine for a day or so... thought all was good. a few days later my mate tried booting up and BSOD. he noticed a DES error loading up msg briefly b4 the bsod. since then he hasn't been able to start up windows. it keeps resetting... or loads up to login then BSOD. having trouble getting to the minidumps this way. any recommendations?

 

[smarteyeball]

Tried safe mode?

 

[torrentg]

Yeah. Safe mode + networking to upload the minidump(s).

 

[Goomba81]

ok weird... i was on the phone with him.. to get him to bootup in safe mode. apparantly it booted up (in normal mode) fine. but there's nothing in the windows\minidumps folder. ??
there was no msg 'windows has recovered from a system crash ..etcetc.' upon startup.
kinda weird.. cause at the moment everything seems ok.
the system isn't overclocked. AVG has been removed and since the last time i posted, i updated all the drivers etc.
any idea? or anything else i could do to isolate issues?

 

[usasma]

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

 

[Goomba81]

well my mates gone interstate so i get to play with his rig for the next few days. here are the minidumps since my last post.. also the .nfo. hope this all helps
i haven't had any crashes so far.. and i've booted it up 4 times already...
sigh.. only difference in setup at his place is that he's running it via hdmi on a 32" lcd tv.

 

[Goomba81]

update...
been running since yesterday with no crashes..
tried watching some movies and games.. still no crashes.
loaded up a game.. starting movie clip was really laggy.. so i updated the gfx drivers, rebooted and all is fine again.
once again i'm stumped as to the cause of all the crashes.

 

[usasma]

The minidumps show memory management errors with a couple of other things - to include an error with the video card. I would expect a memory error with the Video RAM. The way to test this is to try another video card.

More info on STOP 0x116 errors: BSOD Index

Older drivers that should be updated (particularly the one from 2006):

GVTDrv64.sys Tue Sep 05 03:10:02 2006
AODDriver.sys Mon Oct 13 00:38:55 2008
000.fcl      Fri Sep 26 09:11:22 2008

There was also an error in NTFS.SYS - so I'd suggest the following:

CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

A free, bootable Hard Drive diagnostic test: HD Diagnostic

Here's the summary of the last 11 memory dumps:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 11:07:22.669 2009 (GMT-5)
System Uptime: 0 days 0:09:15.700
BugCheck 1A, {41790, fffffa8000804810, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec  6 14:24:15.562 2009 (GMT-5)
System Uptime: 0 days 0:28:22.482
BugCheck 1A, {41790, fffffa80007f8510, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 15:14:08.310 2009 (GMT-5)
System Uptime: 0 days 0:13:53.341
BugCheck 1A, {41790, fffffa8000805a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 10:57:13.449 2009 (GMT-5)
System Uptime: 0 days 0:25:24.479
BugCheck 1A, {41790, fffffa8000805a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 14:59:22.365 2009 (GMT-5)
System Uptime: 0 days 0:30:32.396
BugCheck 1A, {41790, fffffa8000181ce0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 12:00:02.531 2009 (GMT-5)
System Uptime: 0 days 0:40:07.562
BugCheck 1A, {41790, fffffa8000780210, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 13:00:00.443 2009 (GMT-5)
System Uptime: 0 days 0:58:59.474
BugCheck 1A, {41790, fffffa800018dd10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 10:30:59.360 2009 (GMT-5)
System Uptime: 0 days 0:10:13.390
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {fffffa8003e40010, fffff8800495a220, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 13:31:26.893 2009 (GMT-5)
System Uptime: 0 days 0:30:35.924
BugCheck 50, {ffffba80048512c4, 0, fffff8800121d28f, 7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFileForCcFlush+2b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 14:27:48.977 2009 (GMT-5)
System Uptime: 0 days 0:55:29.008
BugCheck 1A, {41790, fffffa80001f9ce0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvSCPAPISvr.ex
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 15:52:13.988 2009 (GMT-5)
System Uptime: 0 days 0:37:14.019
BugCheck 1A, {41790, fffffa8000799a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe

 

[Goomba81]

The minidumps show memory management errors with a couple of other things - to include an error with the video card. I would expect a memory error with the Video RAM. The way to test this is to try another video card.

does that mean faulty hardware? or still undetermined ? cause the gfx card is about a month old..



here's the update..

accidentally ran chkdsk without /r...
the following is the event log...

Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
99584 file records processed. File verification completed.
137 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
138084 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
99584 file SDs/SIDs processed. Cleaning up 147 unused index entries from index $SII of file 0x9.
Cleaning up 147 unused index entries from index $SDH of file 0x9.
Cleaning up 147 unused security descriptors.
Security descriptor verification completed.
19251 data files processed. CHKDSK is verifying Usn Journal...
36873728 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

157183999 KB total disk space.
46061232 KB in 79937 files.
54972 KB in 19252 indexes.
0 KB in bad sectors.
207411 KB in use by the system.
65536 KB occupied by the log file.
110860384 KB available on disk.

4096 bytes in each allocation unit.
39295999 total allocation units on disk.
27715096 allocation units available on disk.

so... went back and tried chkdsk /r... did the reboot.. sat and stared at the screen for the 20 minutes or so.. and it came back clean.. but i cant find the logs in event viewer...
also i cant seem to get windows search to work... it'll search for anything in the start menu.. but it wont even open another window when i click 'search more results'
got alot of errors in event viewer for 'search'


in regards to the files...
000.fcl is related to cyberlink powerdvd.. so removed.
AODDriver.sys is Amd's overdrive? dont know what that's doing there.. and cant find much else while googling...
GVTDrv64.sys is somehow related to gigabyte... cant find anything on it on the gigabyte website.. but i downloaded and updated all drivers/bios/utilities while i was there.


apart from that.. no crashes since...
while on the googling expedition, i came across some posts about people having issues with resolution settings that caused BSODS.. that's the only difference i can think of.
hope this all helps...

 

[usasma]

Still undetermined. Also, I hesitate to suggest new hardware because of the financial burden it imposes on the user. If I do suggest hardware, I suggest borrowing functional hardware, or purchasing hardware that you can return for a full refund (in case I'm wrong).

Additionally, I suggest that replacing parts should come after ALL software troubleshooting. Software troubleshooting is usually free (except for your time).

Replacing the video card is a limited test that stands a good chance of resolving the problems - if the error is a video error. This is because it's not just the card that's replaced - the connection to the mobo is redone, the drivers need to accommodate the new card, the connection to the monitor is redone also, etc.

Finally, since the card is only a month old - you've got nothing to lose by replacing it under warranty (RMA). Contact the seller of the card and let them know that it's probably defective.

 

[Goomba81]

awesome. thanks for all the help usasma.
will keep y'all updated with all this...
so far there's been no crashes at all.... playing avi's, ogm, mkv and loading up games just fine....
i'll have to wait til he gets back and try it again with his TV...

 

[Goomba81]

nevermind. after some googling away.. fixed the search issue.. now only the crashes left... well lack of crashes so far.

usasma, would u recommend that we get the gfx replaced? or continue to use it and monitor it?

 

[usasma]

If you can get another card for free - should you take it? Absolutely!
Should you pay for another card - not at this point.

 

[Goomba81]

back with BSODS