Win7-64bit BSODs

SirWilhelm · 20 Feb 2011

Hi,

My BSODs continue. Starting to wonder if it could be a motherboard issue. Have been running many memory tests and none reports issues with the memory.

All components are less than 5 months old. I have re-installed Windows from scratch several times and I dont have a antivirus software installed. I have replaced the OS disk with a completely new one, since I thought at some point it was related to the hard drive.

Please, any help would be really appreciated!

Regards
Wilhelm

Jonathan_King · 20 Feb 2011

Hello,

Please run driver verifier: Driver Verifier - Enable and Disable

Run Prime95 as well; all three tests: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 07:02:04.652 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:29.603
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  LogonUI.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

SirWilhelm · 20 Feb 2011

rgr, driver verifier is enabled and I have run all 3 tests in Prime95. Although I did not run it so long.

Jonathan_King · 20 Feb 2011

Try running Prime95 for about an hour or two per test, when you get a chance. Do any of the workers stop?

SirWilhelm · 23 Feb 2011

I haven't completed the 3*2 hour Prime95 tests yet...but i will do that I promise and share the result.

However, meanwhile I would like to update the thread a little.

I just disabled the Driver verifier again today...it have been turned on now for 3 days.

Uploaded new dump files.

I also now have noticed that these BSOD's seem to appear most of the times when I have just started up the PC but don't login...just leaving it at the login screen. When Windows goes down in sort of the half-hibernate mode when leaving it there not touching the keyboard or the mouse...I'm getting the BSOD.

Does this share some more light on this?

Jonathan_King · 23 Feb 2011

Might it be your Creative headset causing the problems? Try disconnecting the device and uninstalling the drivers for it; see if that doesn't do the trick for you.

...Summary of the dumps:

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 23 12:28:06.664 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.615
*** WARNING: Unable to verify timestamp for skfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for skfiltv.sys
Probably caused by : skfiltv.sys ( skfiltv+1807 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_skfiltv+1807
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 23 12:26:20.696 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.757
*** WARNING: Unable to verify timestamp for skfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for skfiltv.sys
Probably caused by : skfiltv.sys ( skfiltv+1807 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_skfiltv+1807
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 23 12:24:33.696 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.646
*** WARNING: Unable to verify timestamp for skfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for skfiltv.sys
Probably caused by : skfiltv.sys ( skfiltv+1807 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_skfiltv+1807
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 03:46:43.274 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.336
*** WARNING: Unable to verify timestamp for skfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for skfiltv.sys
Probably caused by : skfiltv.sys ( skfiltv+1807 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_skfiltv+1807
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 03:45:32.321 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.383
*** WARNING: Unable to verify timestamp for skfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for skfiltv.sys
Probably caused by : skfiltv.sys ( skfiltv+1807 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_skfiltv+1807
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 03:44:19.727 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.788
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+7e6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkPageFromLockedList+7e6
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

SirWilhelm · 20 Mar 2011

BSOD's continue.

I've now completed the 3*2 hour CPU tests. No worker stopped.

I also done a 4 hour memory test with Memtest 86+ 4.20. Did not report any issues.

I did remove the Creative headset and removed the drivers with driver sweeper.

On a bluescreen 2-3 days ago I choose the option to repair windows since it suggested this during startup. After that the setting to create a small dump file was removed so I don't have a new dump to attach

. I have reset this again now so it should create the dump.

Any suggestions?

Jonathan_King · 21 Mar 2011

Try flashing the latest BIOS found here: GIGABYTE - Motherboard - Socket 1366 - GA-X58A-UD3R (rev. 2.0)

If that doesn't work, you may try RMAing the board. You can upload one more jcgriff2 report if you get more BSODs, and we'll try to rule out software completely, but I suspect we are down to a hardware problem.

SirWilhelm · 21 Mar 2011

Thanks, I have already updated to latest Bios using the suggested @BIOS software from Gigabyte.

I do have waranty left on all components so maybe returning the motherboard and get a new one?

RMAing? Whats that? Sorry for noob question.

mgorman87 · 21 Mar 2011

Update your video card drivers
atikmpag.sys Thu Nov 25 21:16:47 2010