Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Another BSOD to analyse...

17 Sep 2010   #11

Windows 7 Professional x64
 
 

Do you have another graphics card you can test out? I almost suspect bad video RAM.

If not, I suggest returning the card back to the place you bought it, and get a new one.

It may also pay to do a RAM test. See this tutorial: RAM - Test with Memtest86+

...Summary of the Dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 10:56:00.863 2010 (UTC - 4:00)
System Uptime: 0 days 6:23:20.314
BugCheck 50, {fffffa8045cb1350, 1, fffff88004178ad9, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCaptureProcessName+69 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии


My System SpecsSystem Spec
.

17 Sep 2010   #12

Windows 7 Ultimate 64 bit
 
 

I've already run Memtest86+ - see my OP for the results.

The only other PCI-e video card I've got is an ATI Radeon HD5770 - it needs its own power connection, the PSU in the new machine hasn't got one/it's all zip tied tidily away somewhere.
The 9500GT I've got in here is the only non-new component - it's about a year old and was previously in my other desktop. I upgraded to the aforementioned HD5770 and decide to use the then spare 9500GT in this otherwise new build.
Meh. I'm tempted to not do anything and see if the problem happens again. Is there any way of doing the equivalent of a Memtest86 on video RAM?
My System SpecsSystem Spec
17 Sep 2010   #13

Windows 7 Professional x64
 
 

Sure, you can try Furmark: Video Card - Stress Test with Furmark

Another thing you can try is reseating the video card, and blowing out the PCIe slot with a can of air.
My System SpecsSystem Spec
.


19 Sep 2010   #14

Windows 7 Ultimate 64 bit
 
 

Unfortunately I return.

The machine bluescreened again just now. I was just browsing the Internet. Is this the same issue as before or something else? Memory dumps attached.

The Furmark test ran fine; I quit it when the temperature levelled out.
My System SpecsSystem Spec
19 Sep 2010   #15

Windows 7 Professional x64
 
 

I'd really like to see that other video card tested out. Any chance you could crack open that bunch of power cables?

...Summary of the Dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 06:31:56.461 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:28.912
BugCheck 3B, {c0000005, fffff96000092a4c, fffff88005bd6850, 0}
Probably caused by : win32k.sys ( win32k!bDetermineAlphaBlendFunction+2b4 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
My System SpecsSystem Spec
10 Jan 2011   #16

Windows 7 Ultimate 64 bit
 
 

Hi again.
Having now had some more time, I'm now continuing the troubleshooting.
The previous graphics card died, so has been replaced with a brand new one, no improvements. The PSU has also been swapped out for a slightly more powerful one, with no effect.
I'm going to run Memtest86+ again overnight, but in the meantime I've attached memory dumps going all the way back to my OP.
My System SpecsSystem Spec
10 Jan 2011   #17

Windows 7 Professional x64
 
 

Hello again,

I see several possible causes, just from the dumps dated November and later.

First, your original theory of a network issue is not eliminated from this batch of dumps. Rt64win7.sys and NETIO.SYS are blamed by two dumps, which are your Realtek Ethernet and Windows networking drivers, respectively. Chrome.exe was the top process in another dump. Try installing these updated drivers:
Realtek

The next cause is your Hauppauge TV card drivers. Try installing newer ones from here: Hauppauge Computer Works : Support
Code:
HCW71364.sys    Fri Jan 15 15:20:45 2010 (4B50CE1D)
If you can't find newer ones, remove the device.

Do run the memory test again. One thing I missed the last time around was that error that was detected; any errors are unacceptable, and should be dealt with.

Beside the Memtest86 test, run Prime95. Run both the Blend and Small FFTs tests: http://www.sevenforums.com/tutorials...t-prime95.html

Also test your hard drive, with SeaTools.

Finally, let me ask, when did you replace the graphics card? Was it before or after November 5?

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 16:15:10.548 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:06.000
Probably caused by : usbehci.sys ( usbehci!EHCI_NotifyTransferQueueState+6d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_usbehci!EHCI_NotifyTransferQueueState+6d
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:59:02.447 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:41.524
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:12:20.994 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:48.446
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:06:58.836 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.913
Probably caused by : usbehci.sys ( usbehci!EHCI_RefAsyncIdle+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_usbehci!EHCI_RefAsyncIdle+56
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan  8 06:30:33.597 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:26.674
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : hardware ( spsys+37345 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  sppsvc.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_spsys.sys
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan  5 05:32:27.535 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:03.002
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+a7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeliverApc+a7
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan  3 15:09:18.341 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:50.824
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngCopyBits+12e4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!EngCopyBits+12e4
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan  3 14:57:19.085 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:26.178
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+122 )
BUGCHECK_STR:  0xc2_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_99_Ntfs!NtfsFullDeleteLcb+122
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 09:00:45.551 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:49.034
*** WARNING: Unable to verify timestamp for HCW71364.sys
*** ERROR: Module load completed but symbols could not be loaded for HCW71364.sys
Probably caused by : HCW71364.sys ( HCW71364+2bdf0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_HCW71364+2bdf0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 07:42:08.907 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:38.000
Probably caused by : hardware ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 07:37:46.539 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:20.022
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSelectContextFromThisPriority+80 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiSelectContextFromThisPriority+80
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 06:19:17.517 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:50.000
Probably caused by : hardware ( usbehci!EHCI_DecPendingTransfer+3b )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_usbehci.sys
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 20 11:28:16.786 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:12.253
*** 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+119cf8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 14:22:11.548 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:43.000
Probably caused by : hardware ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+443 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 15:55:43.523 2010 (UTC - 5:00)
System Uptime: 0 days 0:21:13.600
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 20 15:35:26.908 2010 (UTC - 5:00)
System Uptime: 1 days 0:11:48.359
*** WARNING: Unable to verify timestamp for HCW71364.sys
*** ERROR: Module load completed but symbols could not be loaded for HCW71364.sys
Probably caused by : HCW71364.sys ( HCW71364+2c4fd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_HCW71364+2c4fd
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 15:22:58.303 2010 (UTC - 5:00)
System Uptime: 2 days 23:54:51.755
Probably caused by : ntkrnlmp.exe ( nt!PopFindPowerSettingConfiguration+37 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!PopFindPowerSettingConfiguration+37
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 15:24:14.194 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:31.646
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
BUGCHECK_STR:  0xc0000102
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xc0000102_nt!ExpSystemErrorHandler2+5e1
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 15:20:03.903 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:37.355
Probably caused by : hardware ( win32k!GreOffsetRgn+9 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 16:32:42.311 2010 (UTC - 5:00)
System Uptime: 0 days 0:11:32.762
*** 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+3e2303 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+3e2303
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 16:20:31.898 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:49.349
Probably caused by : win32k.sys ( win32k!EvaluateSpline+25a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_win32k!EvaluateSpline+25a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 10 15:05:27.552 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:44.004
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 10 13:39:07.583 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:09.035
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : hardware ( Rt64win7+14786 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Rt64win7.sys
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 15:29:58.100 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:08.552
Probably caused by : nvlddmkm.sys ( nvlddmkm+58e7c3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+58e7c3
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 16:16:50.027 2010 (UTC - 5:00)
System Uptime: 0 days 1:14:14.478
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
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
11 Jan 2011   #18

Windows 7 Ultimate 64 bit
 
 

Hi,
Memtest reported 66 errors over 20 passes of the whole lot of RAM, so I'm now trying each stick in each channel in order to (hopefully) pinpoint the problem.

I've already tested the hard drive with SeaTools - it's fine.

The graphics card was replaced with a temporary one on 30/12/10, and replaced again with a permanent replacement on 8/1/11.

I'll let you know when I've pinpointed the RAM problem.
My System SpecsSystem Spec
11 Jan 2011   #19

Windows 7 Professional x64
 
 

That sounds good.

Remember, modern boards usually run in dual or even triple channel configurations. If you need to RMA one stick, RMA the whole kit, to make sure you don't have problems down the road from now.
My System SpecsSystem Spec
11 Jan 2011   #20

Windows 7 Ultimate 64 bit
 
 

After a day of Memtest'ing, I've pinpointed the fault to one memory module. I've raised an RMA request with OCZ and am awaiting developments.
My System SpecsSystem Spec
Reply

 Another BSOD to analyse...





Thread Tools



Similar help and support threads for2: Another BSOD to analyse...
Thread Forum
Solved BSOD 0x0124, help to analyse the dump file BSOD Help and Support
BSOD, need help to analyse dmp file BSOD Help and Support
How to analyse the CBS.log BSOD Help and Support
BSOD when computer starts, need help to analyse .dmp files BSOD Help and Support
Plz help analyse BSOD BSOD Help and Support
Please analyse this .dmp file for me! BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 03:14 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33