BSOD problems (again)

OldEvil1 · Sep 10, 2012

Hi,

I already came twice to this forum for help in the past and both times you guys were able to solve the BSOD.

http://www.vistax64.com/crashes-debugging/286267-bsod-after-upgrade-system-2.html

http://www.vistax64.com/crashes-debugging/293918-bsod-came-back.html

Since recently however my problem has re-occured. The BSOD occurs a few times a week. I haven't changed anything to the specs of the PC.

System specs:
I bought these Items to upgrade my PC:
2X Corsair XMS CMX4GX3M2A1600C9 (so 8GB in total)
AMD Phenom II X6 1055T 2.8Ghz Boxed | HDT55TFBGRBOX
Asrock 870 Extreme3 | 870 EXTREME3
Samsung EcoGreen F4EG. 2TB | HD204UI (add on to my other 2HD's I already have)
Sapphire HD 6850 1GB GDDR5 PCIE | 11180-00-20R

I added the most recent dumb files and I'm hoping you guys can again find a clue as to the reason of this...

Already a lot of thanks in advance...

EDIT: Just read the sticky, I'll add the 'SF diagnostic Tool'-info when I come back from work this evening. (sorry for not reading it first)

richc46 · Sep 10, 2012

Welcome Back
Sorry you find it necessary to return on an annual basis because of computer problems. In any event, your problem may very well be hardware related. Before testing that lets just try to update a driver that is potentially the cause..
Update driver or uninstall the related hardware
Hcw71364.sys file descriptionProductname: Hauppauge WinTV-HVR-1100 Description: WinTV-HVR-1100 Driver Company: Hauppauge Computer Works, Inc

OldEvil1 · Sep 10, 2012

Tnx for the warm welcome.

I tried to run the SF diagnostic tool but halvway through the process I get a .NET framework error.
I installed .NET 4.5 but it didn't fix this problem.
(details pasted below)

Also in attachment the SF diagnostic data that was obtained.

I got a new BSOD today and I decided to uninstall the hauppauge software and removed the TV-card from the PC.

Code:

ie het einde van dit bericht voor meer informatie over het aanroepen 
van JIT-foutopsporing (Just In Time) in plaats van dit dialoogvenster.

************** Tekst van uitzondering **************
System.IO.IOException: Het systeemaanroepniveau is onjuist
   bij Microsoft.VisualBasic.FileIO.FileSystem.ThrowWinIOError(Int32 errorCode)
   bij Microsoft.VisualBasic.FileIO.FileSystem.ShellFileOperation(SHFileOperationType OperationType, ShFileOperationFlags OperationFlags, String FullSource, String FullTarget, UICancelOption OnUserCancel, FileOrDirectory FileOrDirectory)
   bij Microsoft.VisualBasic.FileIO.FileSystem.ShellCopyOrMove(CopyOrMove Operation, FileOrDirectory TargetType, String FullSourcePath, String FullTargetPath, UIOptionInternal ShowUI, UICancelOption OnUserCancel)
   bij Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
   bij Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   bij Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   bij WindowsApplication2.Form1.Button1_Click(Object sender, EventArgs e)
   bij System.Windows.Forms.Control.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bij System.Windows.Forms.Control.WndProc(Message& m)
   bij System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bij System.Windows.Forms.Button.WndProc(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladen assembly's **************
mscorlib
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4223 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
    Assembly-versie: 1.0.0.0
    Win32-versie: 5.0.0.3
    CodeBase: file:///C:/Users/OldEvil1/Desktop/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly-versie: 8.0.0.0
    Win32-versie: 8.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4223 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4228 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4230 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Windows.Forms.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
mscorlib.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4223 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------

************** JIT-foutopsporing **************
Als u JIT-foutopsporing wilt inschakelen, moet in het configuratiebestand voor deze
toepassing of computer (machine.config) de waarde
jitDebugging in het gedeelte system.windows.forms zijn ingesteld.
De toepassing moet ook zijn gecompileerd terwijl foutopsporing
was ingeschakeld.

Bijvoorbeeld:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wanneer JIT-foutopsporing is ingeschakeld, worden onverwerkte uitzonderingen
naar het JIT-foutopsporingsprogramma gestuurd dat op de computer is geregistreerd
en worden niet door dit dialoogvenster verwerkt.

Oh... maybe relevant ... but probably not:
Since a few weeks my PC freezes for a minute of 2 whenever I open Internet Explorer for the first time after I booted the PC. Don't have this problem with Chrome...

richc46 · Sep 10, 2012

The latest reports give no information that can help, it Inconlusive

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_SF_OldEvil1_10-09-2012.zip\SF_10-09-2012\Mini091012-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02bdbdd0
Debug session time: Mon Sep 10 01:30:44.618 2012 (GMT-4)
System Uptime: 0 days 1:13:24.657
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {21, 0, fffffa60019d8180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------

This most likely points to harware. It may be a drawn out process, but we can get this solved just as we did in the past.
Lets start with memory test.
Guide to using Memtest86+ - Geeks to Go Forums

OldEvil1 · Sep 10, 2012

I have complete confidence in you

I just created a memtest bootable USB and I'm now going to start it up for the night.

If nothing shows up I'll test it stick-per-stick starting tomorrow.
I'll keep you posted.

OldEvil1 · Sep 11, 2012

Good news (I think):
The memtest showed the screen in attachment:

How sure are we with this information that memory is the cause?

I suppose the next test will be to remove 2 memory sticks and test those 2 tonight.
And repeat this tomorrow for the other 2 sticks?

(I also saw I have 2 months of waranty left on the memory - so I might be able to trade them)

richc46 · Sep 11, 2012

The next step would be to try to return the memory under warranty.

OldEvil1 · Sep 12, 2012

Just got confirmation that I can send the memory sticks back to them.

richc46 · Sep 12, 2012

Thats actually good news. You get your computer fixed for free. Glad that I could help solve your problem.

OldEvil1 · Sep 12, 2012

tnx again (that's the third time you helped me)

This topic may be closed.
I'll open a new one if I get new problems

richc46 · Sep 12, 2012

I will mark this thread as solved. Again, Im glad that I could help solve your problem.

OldEvil1 · Sep 23, 2012

Today, after two weeks, I got a new BSOD.

I send 2 memory sticks back for RMA and they informed me that they could find anything wrong with them.

And now, after two weeks (working only with 2 instead of 4 memory sticks) I got a new BSOD.
minidump in attachment.

I guess I can report them that the BSOD issue isn't solved.

richc46 · Sep 23, 2012

OldEvil1 said:
Good news (I think):
The memtest showed the screen in attachment:

How sure are we with this information that memory is the cause?

I suppose the next test will be to remove 2 memory sticks and test those 2 tonight.
And repeat this tomorrow for the other 2 sticks?

(I also saw I have 2 months of waranty left on the memory - so I might be able to trade them)

Regardless of what they said there are many errors. It could be the mother board and not the sticks.
Test again. Follow directions for test carefully.

OldEvil1 · Sep 23, 2012

and another BSOD
In both cases I was playing a game (Company of Heroes) and watching an livestream on my second screen.

dump in attachment.

I'll do another memtest tonight.

richc46 · Sep 23, 2012

They are all the same, they hint at hardware and you DID fail the memory test. It could be the MB (slots) that are bad.

OldEvil1 · Sep 24, 2012

After a night of memtest (didn't change anything to the configuration - so 2 memory sticks in the first 2 banks):

I'm thinking there might have been 2 issues?
1. the memory sticks I have send for RMA did give errors during memtest (both in position 3 and 4 and in positions 1 and 2).
2. the will be/might be another issue with motherboard or graphics card?

richc46 · Sep 24, 2012

OK you tested all the sticks. Now test each stick alone for 6 passes. If that passes we will look for other causes. Not trying to give you a hard time, but we have to be sure. If its memory and we pass it as good, we never find the cause.

OldEvil1 · Sep 25, 2012

Stick 1 in position 1: pass

Tonight I'll test stick 2 in position 1

richc46 · Sep 25, 2012

If you are doning those test for between 6-8 passes we may have to look into causes other than memory as the source of the problem. I would not understand, however, why it failed the first time.

OldEvil1 · Sep 25, 2012

I agree, with the other two sticks (that I sent for RMA - but they informed me they couldn't find anything wrong with it) I got twice an error during this test.

first time with 4 sticks in te PC
position A - stick 1
position B - stick 2
position C - stick 3
position D - stick 4

Second time with only those 2 sticks in the PC
position A - stick 3
position B - stick 4

But we'll take it one step at a time...
I'm also starting to think that I almost always was watching TV on my PC at the moment of the BSOD. Either via the hauppage card (which I removed and unistalled), or yelo or just a justinTV-like site...

BSOD problems (again)

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer