BSOD

[cloud167]

Hello,

Reticently I have started to get a lot of random BSODs

Here are the requested files from the instructions

View attachment 155055
View attachment 155056

This usually happens when I'm playing World of Warcraft but has happened randomly some other times, watching a movie, playing other games.

I'm at a loss as to what is causing this. Any help with this issue would be greatly appreciated.

I have ran mem diag and it comes back clean

I have updated my system specs in my profile.

 

[Jonathan_King]

Hello,

Try flashing the latest BIOS from here: http://download.gigabyte.ru/bios/motherboard_bios_ga-ex58-ud3r-sli_f9.exe

Run all three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

If the BSODs persist, please upload a new jcgriff2 report; apparently the app didn't finish running the first time.

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 17 20:30:27.800 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:59.813
Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObject+15d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiSignalSynchronizationObject+15d
BiosReleaseDate = 05/11/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 17 19:21:06.450 2011 (UTC - 4:00)
System Uptime: 0 days 0:18:11.463
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ataport.SYS - 
Probably caused by : CLASSPNP.SYS ( CLASSPNP+1bce )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Repair.exe
FAILURE_BUCKET_ID:  X64_0xD1_CLASSPNP+1bce
BiosReleaseDate = 05/11/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 15:58:47.111 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:27.189
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 14:55:20.654 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:25.731
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchFilterHo
FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+0
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 13:51:02.432 2011 (UTC - 4:00)
System Uptime: 0 days 11:21:04.510
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 02:28:37.901 2011 (UTC - 4:00)
System Uptime: 0 days 4:25:46.894
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : dxgmms1.sys ( dxgmms1+31e79 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1+31e79
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  8 22:01:21.772 2011 (UTC - 4:00)
System Uptime: 0 days 5:09:31.849
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for pacer.sys
*** ERROR: Module load completed but symbols could not be loaded for pacer.sys
Probably caused by : pacer.sys ( pacer+111b )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  veohwebplayer.
FAILURE_BUCKET_ID:  X64_0xC5_2_pacer+111b
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  8 16:42:11.032 2011 (UTC - 4:00)
System Uptime: 0 days 15:12:22.109
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+9a05 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xA_atikmpag+9a05
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  8 01:28:31.126 2011 (UTC - 4:00)
System Uptime: 1 days 17:27:21.203
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : dxgmms1.sys ( dxgmms1+1b507 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1+1b507
BiosReleaseDate = 02/26/2009
SystemProductName = UD3R-SLI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[cloud167]

On my lappie now thanks for the quick response, my computer is doing a chkdsk atm but soon as it is finished i'll log on and try to run those tests and get a completed dump file for you.

 

[cloud167]

Ok my computer doesn't like the BIOS link you gave, says its the wrong version, I'm running 64 bit windows.

the Prime95 tests caused my computer to BSOD almost immediately...

Here is the updated file you asked for I have BSOD'ed 4 times since the 1st one...hopefully this one here is a complete one.

Once while playing WoW for about 10 mins...
Running a repair on WoW
Another one happened while I was trying to do make sure my vid card drivers where up to date
Last one happened with your prime 95 test.


View attachment 155061

 

[Jonathan_King]

Try getting the BIOS here: GIGABYTE - Motherboard - Socket 1366 - GA-EX58-UD3R-SLI (rev. 1.0)

I think our biggest clue is that Prime95 causes an instant reboot. Run Memtest86: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If that comes up clean after 7 or 8 passes, take out all RAM except one stick and then run Prime95. Be sure to note the temps Speedfan shows.

 

[cloud167]

Ok, I have left it running the whole time i was at work today,

I got this fail

Tst 7
Pass 5
Failing address 00108f6e048-4239.4 MB
good 46d7bdd1
bad 46d73dd1
err-bits 00008000
count chan 1

So if i'm interpreting this right, my 2nd stick is bad? or the slot is bad?

 

[cloud167]

Ok i think i figured it out, my 3rd slot on my mother board is bad. I tested one at a time and was unable to launch my computer in one slot, but with the other 3 I was able to run the stress test, I repeated this process with my other two sticks. doing it one at a time and launching the stress tester. Now I have all 3 in my system and the stress tester has been running for 5 mins with no BSOD I used to BSOD almost as soon as i started the stress tester. ^,^ would you suggest running any additional tests?

 

[Jonathan_King]

Hello,

Sorry about the delay...I just started a new job which had to take first priority!

I can't think of any other tests for you to run, with the possible exception of testing your RAM in another system. Still, the case is pretty good for a bad motherboard!