Several BSOD messages, graphic drivers?

Dookster · 04 Jul 2010

I attached the 4 latest minidumps.
Problems have been going on for half a year though before I finally went kuku and decided to call for help:

I'm getting pfn list corrupt, page fault in non paged area, irql-not less or equal errors bsods but most of all it's memory management.

I've tried numerous formats and reinstalling everything.
I've done memtest and no errors whatsoever pop up.
I've taken out one memstick, put them in different slots, ...

As far as I recall the problems all started with me installing the Catalyst control center from ati causing me to believe that it's a video card driver problem.
I updated chipset drivers and have the latest ati drivers for my video card so I'm getting quite desperate.
I have been searching several forums and read somewhere that it's bios related?
(Current version is 6.00PG)
One person advised to flash the bios to a newer version but I want to explore other possibilities first before i risk having to throw away my mobo.

System setup:
Intel Core i7-860
Gigabyte GA-P55-UD4
Sapphire Radeon HD 5770 Vapor-X 1GB GDDR5
OCZ Obsidian Ultra-low Voltage 2x2 Gb DDR3-1600 PC3-12800

Jonathan_King · 04 Jul 2010

It could very well be a hardware issue. Do not use any Catalyst features, just the driver itself.

Your Gigabyte power saving drivers are out of date:

Code:

GVTDrv64.sys Tue Sep 05 03:10:02 2006

Please remove the program completely, or update it.

Enable driver verifier: Using Driver Verifier to identify issues with Drivers

Summary of the Dumps:

Code:


Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Sun Jul  4 07:31:40.383 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:19.523
BugCheck 1A, {41790, fffffa8001356540, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Sun Jul  4 07:00:35.683 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:05.823
BugCheck 50, {fffff900cb1869b0, 0, fffff960000bbc5a, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+5bc5a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Sun Jul  4 07:35:58.332 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:37.472
BugCheck 1A, {41201, fffff683ff7fed98, 3160000100557025, fffffa8003a8f4e0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  SearchProtocol
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Sun Jul  4 07:19:00.030 2010 (UTC - 4:00)
System Uptime: 0 days 0:17:44.060
BugCheck 1A, {3452, 50000, fffff70001080838, 876000006853bc66}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 )
BUGCHECK_STR:  0x1a_3452
PROCESS_NAME:  SearchFilterHo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Dookster · 05 Jul 2010

Thx for the reply. I searched for an update of that driver but couldn't find one. Seems to be for Easytune6 from Gigabyte, I installed Smart6 now, don't know if that will help or...? Driveragent gave no results for outdated drivers.

Either way I also flashed my bios since F6 gave enhanced memory compatibility.
After the format (I formatted cause I didn't want to get a BSOD while flashing) - and reinstalling most of my frequently used progs -I still have the BSODs though.

4 latest dumps using driver verifier are included.

Dookster · 05 Jul 2010

Removed everything videocard related, will report back when I hit the BSOD again or...
Any help meanwhile reading the minidumps is greatly appreciated.

Jonathan_King · 10 Jul 2010

Glad to hear the problem seems to have stopped.

As for the dmps:

Summary of the Dumps:

Code:


Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Mon Jul  5 11:49:07.478 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:25.633
BugCheck C1, {fffff98016dc0c10, fffff98016dc001b, 8103e8, 23}
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Mon Jul  5 11:53:34.123 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:56.278
BugCheck 1A, {41790, fffffa8000d04940, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Mon Jul  5 11:56:35.684 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:53.729
BugCheck 4E, {99, cc8d3, 0, ccc53}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Mon Jul  5 12:01:49.532 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:56.687
BugCheck 1A, {41790, fffffa8000d28f40, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  wermgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

I have to suspect hardware from the looks of it, RAM and video card in particular. Let's just wait and see what happens.

Dookster · 11 Jul 2010

I did sfc /scannow and it repaired a load of files, that in combination with clearing Catalyst and just using the driver seems to help. No more BSODs.

My screen tends to go all grey though from time to time now so I have to reboot anyway -> indication that its the videocard? If so how do I prove this

Jonathan_King · 11 Jul 2010

You don't happen to have a spare video card you can test, do you? Could you borrow one from a friend?