BSOD randomly happens

[Test67]

I have recently built my own PC and installed Win7 64 bit, but just get lots of BSOD which can happen randomly some a few mins after boot, other after an hour or so.
I have tested my memory using memtest and get no errors (11 passes).

System temperatures seem good, I have tried recently removed my Antivirus (avast) but this did not help.

Gigabyte 870A-UD3 motherboard
AMD Phenom II X4 965
2 x 2GB DDR3 9-9-9-24
MSI N8400GS with 512MB (Basic but all I need)
850W PSU
Various HDD

Any help appreciated.

 

[zigzag3143]

I have recently built my own PC and installed Win7 64 bit, but just get lots of BSOD which can happen randomly some a few mins after boot, other after an hour or so.
I have tested my memory using memtest and get no errors (11 passes).

System temperatures seem good, I have tried recently removed my Antivirus (avast) but this did not help.

Gigabyte 870A-UD3 motherboard
AMD Phenom II X4 965
2 x 2GB DDR3 9-9-9-24
MSI N8400GS with 512MB (Basic but all I need)
850W PSU
Various HDD

Any help appreciated.

AS of your most recent BSOD Avast is still installed and loading, and the cause. Use this to remove

Avast

http://www.microsoft.com/security_essentials/

Ken J

 

[Test67]

I have used the Avast removal tool and now also installed MS security essentials, the PC was running OK for about 30 mins and then BSOD !

Any more clues as to what is causing the BSOD ?

Thanks for the help so far....

 

[Test67]

Still getting BSOD

I have attahced the latest dmp info, as I am still getting various BSOD after removal of Avast.
( I have deleted the previous older dmp files, so you just have the latest)

I have not got a clue what this can be, help !!!!

 

[Jonathan_King]

Start by updating your nVidia display drivers:

nvlddmkm.sys     Tue Jan 12 00:26:35 2010 (4B4C080B)

Here's a download link: NVIDIA DRIVERS 260.99 WHQL

I suspect the problem may be caused by your network adapter drivers.

netr28ux.sys     Mon May 25 00:38:17 2009 (4A1A20B9)

That is the Edimax nLite Wireless USB Adapter. Could you download some newer drivers from here?

::: EDIMAX Technology :::

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 05:41:21.371 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:52.683
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_sMode_PollEndpointSlot+67
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 05:02:36.784 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:15.469
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 04:54:27.128 2010 (UTC - 5:00)
System Uptime: 0 days 0:25:18.439
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 04:28:23.320 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:10.021
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec  2 14:51:46.324 2010 (UTC - 5:00)
System Uptime: 0 days 0:40:00.010
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Test67]

Still more BSOD

I have now updated my Nvidia driver to the latest version.

On my Edimax wifi, the driver I was using was dated 25/5/2009, I updated to one on the Edimax web site, but this was not much better dated 3/7/2009. I then found out that they use Ralink chipsets, so used the latest driver from their website (dated 26/5/2010).

But I still have just got a BSOD, info attahced.

Could this be hardware, as mosty drivers have been updated etc ?

 

[Test67]

Lots more BSOD

It's still happening, any thing else I can try ?
Latest DMPs attahced.

Thanks.

 

[Jonathan_King]

I see nothing out of place as far as software goes; let's make sure software is not the cause, and then test hardware.

To try to flush out any drivers causing the problem, enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Could you also run Prime95? Read this guide: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 10:33:50.209 2010 (UTC - 5:00)
System Uptime: 0 days 0:27:33.520
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Test67]

Thanks for the help so far...

I have run Prime95 for around 3 hours and did not get any errors (and no BSOD).
Temperature and voltages seem OK
CPU temp at idle was 30C, at full load was 58C
DDR volatge was the same at idle and full load (1.504V)
The 3.3V rail was 3.344 at idle and 3.328 at full load.
The 12V rial was 12.048 at idel and 11.858 at full load.

I then ran the driver verifier, I assume the results for this appear in the DMP file, as I saw no results on screen. I have had a few BSOD since the verifier has been on and have attahced my files.

Thanks,
Mark.

 

[Jonathan_King]

Try running Furmark: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Do you have access to another video card? I'm wondering if that could possibly be the problem.

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec  4 10:26:13.994 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:14.710
*** 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+fc28a )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nvlddmkm+fc28a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec  4 08:41:46.301 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:10.002
Probably caused by : cng.sys ( cng!GatherRandomKey+294 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_cng!GatherRandomKey+294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec  4 08:25:12.761 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:13.478
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Test67]

Bad DDR3 !!!

Thanks to all the help I have got from this forum, I hopfully have now solved the BSOD problem (well it's been stable for a few days now !)

It turns out the DDR3 was bad.

I did run memtest86 for 11 passes and got no errors at all.
I ran Prime95, the test recomended here which is small FFTs for about 3hrs and still no errors.
I then had a play with Prime95 and ran the blended test, so a range of FFTs that ment the ram is used a lot more, within a few mins each of my 4 cores came up with a rounding error !

I then did the same test with only one DDR3 stick at a time and found one to be at fault.
So, I got some new DDR3 (same speed/latency) and all is stable now.

I am a little concerned that Memtest86 did not pick this up, very strange, but at least I have a stable system now !!

Cheers.

 

[Jonathan_King]

Good diagnostic work! I'm glad you found the problem, and thanks for reporting back.