BSOD when playing games or doing nothing! :D

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Rodakino, Oct 25, 2014.

  1. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Hello everyone, I would like your help in stopping the favorite hobby of my pc, BSOD-ing.

    My pc will probably bsod at least once a day or if I play games more than once, I have searched of ways
    to make it stop and run some tests as well, I've done both mem test and disk check and there have been no problems, I personally think it's a hardware problem but I have no idea where to go from there, of course I might be wrong cause my knowledge in this area is limited.

    There have been times that I get a bsod even when I'm doing nothing, like leaving the PC on desktop and watching TV or something. Most of my bsods happen when I play games, I could be playing for 5 minutes or even 30 minutes or more before the bsod. Really it happens all the time and I would like to find a way to make that stop.

    I know my PC is old but I don't want to throw it away, although if the problem is the motherboard then I'll have to consider that option right?

    Thank you in advance for your time and I hope we find we find a solution. [​IMG]

    (Everything is in the folder.)
     

    Attached Files:

    #1 Rodakino, Oct 25, 2014
    Last edited: Oct 26, 2014
  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {80acdc30, 8, 80acdc30, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    
    Hi,
    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    Another common cause is the installation of a faulty system service.
    Antivirus software can also trigger this error, as can a corrupted NTFS volume.

    You also had quite a few dump files for the NTFS system which may mean there's an issue with a drive.
    Please run a chkdsk/f/r in a admin command prompt (find command prompt in the start menu, right click on it, properties then run as admin). You may need to reboot.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/
    You might also have some system corruption, again in an admin command prompt type:
    sfc /scannow
    Press enter and await results.

    I've checked for a system support page but I'm having trouble finding one.

    aswHwid.sys Thu Jun 26 12:31:24 2014: Avast AV known on occasion to cause issues please remove and install MSE as it's very stable:
    http://windows.microsoft.com/en-GB/windows/security-essentials-download

    fetn62.sys Thu Mar 31 04:20:34 2011: VIA Rhine Family Fast Ethernet Adapter please update:
    http://www.via.com.tw/en/support/drivers.jsp

    MpKsl02ce8b7b.sys Wed Aug 21 23:32:05 2013: This is possible malware. Please download and run Malwarebytes:
    https://www.malwarebytes.org/

    When you say you tested the RAM what did you use?
     
  3. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    I did change my antivirus cause I also noticed that they caused bsod, I had avast and avg I think but now I do have MSE.

    I also have malwarebytes, I've scanned before but I will scan again just in case.

    I know NTFS has been an issue and I've run both things you mentioned in command prompt, having said that I will do it again just in case and tell you of the results.

    I'll update the VIA thing, I did download the driver I hope I did download the right one.

    As for the RAM, I used the mem test on both RAMs individualy for I think 3 runs.
    Before testing them I had another set of RAMs, same capacity, but I read that RAM could be the reason of the bsod so I changed them to the ones I use now (the ones I also tested), I could run another test of course.

    What is the system support page, is it important?

    Thank you for replying :D
     
  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Usually a system or motherboard has a support page but checking at Packard Bell I can find no such page. This could be down to age or I just haven't found it yet.. :)
    Post any new dump files.
    Please run the scans outlined and post the results.
     
  5. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    ok so, I did the chkdsk/f/r and went AFK and when I came back PC was at desktop so I suppose it was ok?
    But, I did sfc /scannow and it says:

    Windows Resource Protection found corrupt files but was unable to fix some of them.
    Details are included in the CBS.log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    Now, I went to that CBS.log file but when I open it it says access denied, I think that can be changed in the security
    properties by enabling read & execute right? But it says it can result in unexpected access problems etc. and If I want to continue.
    How should I proceed from there?

    I haven't done the malware bytes scan or the mem test yet.

    Also I'm going to attach a compressed file with 2 new dump files from today.

    Edit: Did malware bytes scan, all good.
     

    Attached Files:

    #5 Rodakino, Oct 26, 2014
    Last edited: Oct 26, 2014
  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {80c89c30, 8, 80c89c30, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    
    Hi,
    same as before. To access your logs try booting into admin mode.
    http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-windows-vista/
    Just disable the account when your done.

    Can you post the exact make and model of your machine please. I might be able to find out a bit more about it as you might be missing updates.
     
  7. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Ok, I made a copy of that file, I'll upload it with this post.

    Where do I find the exact model? Is it on the pc or motherboard?
     

    Attached Files:

  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Code:
    2014-10-26 17:25:15, Info                  CSI    00000225 [SR] Cannot repair member file [l:24{12}]"malgunmc.ttf" of Microsoft-Windows-ehome-font, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-26 17:25:16, Info                  CSI    00000226 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.1.7600.16385_none_65a9a90d09b41838\SportsNotesBackground_PAL.wmv do not match actual file [l:58{29}]"SportsNotesBackground_PAL.wmv" :
      Found: {l:32 b:UhRiJCHCLSBvXiemcDzyAWL+Fyi3OpAbVG4EpnAijWE=} Expected: {l:32 b:kBA/DhswFo0wOD0Ygp8RPRsg9vmizdlwra/A4zfksz8=}
    2014-10-26 17:25:16, Info                  CSI    00000227 [SR] Cannot repair member file [l:58{29}]"SportsNotesBackground_PAL.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-Sports, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-26 17:25:17, Info                  CSI    00000228 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.1.7600.16385_none_65a9a90d09b41838\SportsNotesBackground_PAL.wmv do not match actual file [l:58{29}]"SportsNotesBackground_PAL.wmv" :
      Found: {l:32 b:UhRiJCHCLSBvXiemcDzyAWL+Fyi3OpAbVG4EpnAijWE=} Expected: {l:32 b:kBA/DhswFo0wOD0Ygp8RPRsg9vmizdlwra/A4zfksz8=}
    2014-10-26 17:25:17, Info                  CSI    00000229 [SR] Cannot repair member file [l:58{29}]"SportsNotesBackground_PAL.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-Sports, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-26 17:25:17, Info                  CSI    0000022a [SR] This component was referenced by [l:192{96}]"Microsoft-Windows-OpticalMediaDisc-Package~31bf3856ad364e35~x86~~6.1.7601.17514.OpticalMediaDisc"
    2014-10-26 17:25:17, Info                  CSI    0000022b Hashes for file member \??\C:\Program Files\DVD Maker\Shared\DvdStyles\Sports\SportsNotesBackground_PAL.wmv do not match actual file [l:58{29}]"SportsNotesBackground_PAL.wmv" :
      Found: {l:32 b:UhRiJCHCLSBvXiemcDzyAWL+Fyi3OpAbVG4EpnAijWE=} Expected: {l:32 b:kBA/DhswFo0wOD0Ygp8RPRsg9vmizdlwra/A4zfksz8=}
    2014-10-26 17:25:17, Info                  CSI    0000022c Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.1.7600.16385_none_65a9a90d09b41838\SportsNotesBackground_PAL.wmv do not match actual file [l:58{29}]"SportsNotesBackground_PAL.wmv" :
      Found: {l:32 b:UhRiJCHCLSBvXiemcDzyAWL+Fyi3OpAbVG4EpnAijWE=} Expected: {l:32 b:kBA/DhswFo0wOD0Ygp8RPRsg9vmizdlwra/A4zfksz8=}
    2014-10-26 17:25:17, Info                  CSI    0000022d [SR] Could not reproject corrupted file [ml:520{260},l:108{54}]"\??\C:\Program Files\DVD Maker\Shared\DvdStyles\Sports"\[l:58{29}]"SportsNotesBackground_PAL.wmv"; source file in store is also corrupted
    2014-10-26 17:25:18, Info                  CSI    0000022e Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_ceb84d8b2ab2884f\malgunmc.ttf do not match actual file [l:24{12}]"malgunmc.ttf" :
      Found: {l:32 b:aHJF8o/ZJuiU8/OLiTMfiD2z+52jd1GsCya2dVYlCh0=} Expected: {l:32 b:PXDNlSBNwbf78N7JGaksI3bI9IGHln2mzFrdmDpeDj8=}
    2014-10-26 17:25:18, Info                  CSI    0000022f [SR] Cannot repair member file [l:24{12}]"malgunmc.ttf" of Microsoft-Windows-ehome-font, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-26 17:25:18, Info                  CSI    00000230 [SR] This component was referenced by [l:172{86}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~x86~~6.1.7601.17514.MediaCenter"
    2014-10-26 17:25:19, Info                  CSI    00000231 Hashes for file member \??\C:\Windows\ehome\malgunmc.ttf do not match actual file [l:24{12}]"malgunmc.ttf" :
      Found: {l:32 b:aHJF8o/ZJuiU8/OLiTMfiD2z+52jd1GsCya2dVYlCh0=} Expected: {l:32 b:PXDNlSBNwbf78N7JGaksI3bI9IGHln2mzFrdmDpeDj8=}
    2014-10-26 17:25:19, Info                  CSI    00000232 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_ceb84d8b2ab2884f\malgunmc.ttf do not match actual file [l:24{12}]"malgunmc.ttf" :
      Found: {l:32 b:aHJF8o/ZJuiU8/OLiTMfiD2z+52jd1GsCya2dVYlCh0=} Expected: {l:32 b:PXDNlSBNwbf78N7JGaksI3bI9IGHln2mzFrdmDpeDj8=}
    2014-10-26 17:25:19, Info                  CSI    00000233 [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:24{12}]"malgunmc.ttf"; source file in store is also corrupted
    2014-10-26 17:25:19, Info                  CSI    00000234 Repair results created:
    POQ 108 starts:
         0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\735bae0c31f1cf01872e00005405100d._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
        1: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\e4cdae0c31f1cf01882e00005405100d.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
        2: Move File: Source = [l:238{119}]"\SystemRoot\WinSxS\Temp\PendingRenames\3636b50c31f1cf01892e00005405100d.program_files_dvd_maker_405775de8763ce75.cdf-ms", Destination = [l:150{75}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_405775de8763ce75.cdf-ms"
        3: Move File: Source = [l:252{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\5362b90c31f1cf018a2e00005405100d.program_files_dvd_maker_shared_a54613779b918be2.cdf-ms", Destination = [l:164{82}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_shared_a54613779b918be2.cdf-ms"
        4: Move File: Source = [l:272{136}]"\SystemRoot\WinSxS\Temp\PendingRenames\daf5bc0c31f1cf018b2e00005405100d.program_files_dvd_maker_shared_dvdstyles_5fb67e37dd207bb6.cdf-ms", Destination = [l:184{92}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_shared_dvdstyles_5fb67e37dd207bb6.cdf-ms"
        5: Move File: Source = [l:286{143}]"\SystemRoot\WinSxS\Temp\PendingRenames\3458bf0c31f1cf018c2e00005405100d.program_files_dvd_maker_shared_dvdstyles_sports_c6567ebf18c8e989.cdf-ms", Destination = [l:198{99}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_shared_dvdstyles_sports_c6567ebf18c8e989.cdf-ms"
    
    POQ 108 ends.
    2014-10-26 17:25:19, Info                  CSI    00000235 [SR] Repair complete
    2014-10-26 17:25:19, Info                  CSI    00000236 [SR] Committing transaction
    2014-10-26 17:25:19, Info                  CSI    00000237 Creating NT transaction (seq 2), objectname [6]"(null)"
    2014-10-26 17:25:19, Info                  CSI    00000238 Created NT transaction (seq 2) result 0x00000000, handle @0x167c
    2014-10-26 17:25:20, Info                  CSI    00000239@2014/10/26:15:25:20.170 CSI perf trace:
    CSIPERF:TXCOMMIT;265764
    2014-10-26 17:25:20, Info                  CSI    0000023a [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    2014-10-26 17:35:22, Info                  CBS    Reboot mark refs incremented to: 1
    2014-10-26 17:35:22, Info                  CBS    Scavenge: Starts
    2014-10-26 17:35:22, Info                  CSI    0000023b@2014/10/26:15:35:22.846 CSI Transaction @0x1c0be70 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"
    
    2014-10-26 17:35:22, Info                  CBS    Scavenge: Begin CSI Store
    2014-10-26 17:35:23, Info                  CSI    0000023c Performing 1 operations; 1 are not lock/unlock and follow:
      Scavenge (8): flags: 00000017
    2014-10-26 17:35:23, Info                  CSI    0000023d Store coherency cookie matches last scavenge cookie, skipping scavenge.
    2014-10-26 17:35:23, Info                  CSI    0000023e ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
    2014-10-26 17:35:23, Info                  CSI    0000023f Creating NT transaction (seq 3), objectname [6]"(null)"
    2014-10-26 17:35:23, Info                  CSI    00000240 Created NT transaction (seq 3) result 0x00000000, handle @0x6f0
    2014-10-26 17:35:23, Info                  CSI    00000241@2014/10/26:15:35:23.824 CSI perf trace:
    CSIPERF:TXCOMMIT;322071
    2014-10-26 17:35:23, Info                  CBS    Scavenge: Completed, disposition: 0X1
    2014-10-26 17:35:23, Info                  CSI    00000242@2014/10/26:15:35:23.825 CSI Transaction @0x1c0be70 destroyed
    2014-10-26 17:35:23, Info                  CBS    Reboot mark refs: 0
    2014-10-26 17:35:23, Info                  CBS    Idle processing thread terminated normally
    2014-10-26 17:35:23, Info                  CBS    Ending the TrustedInstaller main loop.
    2014-10-26 17:35:23, Info                  CBS    Starting TrustedInstaller finalization.
    2014-10-26 17:35:24, Info                  CBS    Ending TrustedInstaller finalization.
    2014-10-26 19:19:24, Info                  CBS    Starting TrustedInstaller initialization.
    2014-10-26 19:19:24, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cbscore.dll
    2014-10-26 19:19:25, Info                  CSI    00000001@2014/10/26:17:19:25.794 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x71a8de79 @0x720d5d7d @0x720b205a @0xd1c99 @0xd1236 @0x75b975a8)
    2014-10-26 19:19:25, Info                  CSI    00000002@2014/10/26:17:19:25.810 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x71a8de79 @0x72117183 @0x72114013 @0xd1c99 @0xd1236 @0x75b975a8)
    2014-10-26 19:19:25, Info                  CSI    00000003@2014/10/26:17:19:25.810 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x71a8de79 @0x73754bc8 @0x737554a6 @0xd1327 @0xd1245 @0x75b975a8)
    2014-10-26 19:19:25, Info                  CBS    Ending TrustedInstaller initialization.
    2014-10-26 19:19:25, Info                  CBS    Starting the TrustedInstaller main loop.
    2014-10-26 19:19:25, Info                  CBS    TrustedInstaller service starts successfully.
    2014-10-26 19:19:25, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2014-10-26 19:19:25, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2014-10-26 19:19:25, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2014-10-26 19:19:25, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:19:25, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:19:25, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2014-10-26 19:19:25, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:19:25, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
    2014-10-26 19:19:25, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
    2014-10-26 19:19:25, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xbcf7f8
    2014-10-26 19:19:25, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
    2014-10-26 19:19:25, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1c0
    2014-10-26 19:19:25, Info                  CSI    00000007@2014/10/26:17:19:25.810 CSI perf trace:
    CSIPERF:TXCOMMIT;1103
    2014-10-26 19:19:25, Info                  CBS    NonStart: Success, startup processing not required as expected.
    2014-10-26 19:19:25, Info                  CBS    Startup processing thread terminated normally
    2014-10-26 19:19:25, Info                  CSI    00000008 CSI Store 4311640 (0x0041ca58) initialized
    2014-10-26 19:19:25, Info                  CBS    Session: 30404928_4261495780 initialized by client WindowsUpdateAgent.
    2014-10-26 19:19:42, Info                  CBS    Trusted Installer signaled for shutdown, going to exit.
    2014-10-26 19:19:42, Info                  CBS    Ending the TrustedInstaller main loop.
    2014-10-26 19:19:42, Info                  CBS    Starting TrustedInstaller finalization.
    2014-10-26 19:19:47, Info                  CBS    Ending TrustedInstaller finalization.
    2014-10-26 19:21:30, Info                  CBS    Starting TrustedInstaller initialization.
    2014-10-26 19:21:31, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cbscore.dll
    2014-10-26 19:21:34, Info                  CSI    00000001@2014/10/26:17:21:33.775 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x65cfde79 @0x661a5d7d @0x6618205a @0xaa1c99 @0xaa1236 @0x771975a8)
    2014-10-26 19:21:35, Info                  CSI    00000002@2014/10/26:17:21:35.056 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x65cfde79 @0x661e7183 @0x661e4013 @0xaa1c99 @0xaa1236 @0x771975a8)
    2014-10-26 19:21:35, Info                  CSI    00000003@2014/10/26:17:21:35.056 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x65cfde79 @0x65644bc8 @0x656454a6 @0xaa1327 @0xaa1245 @0x771975a8)
    2014-10-26 19:21:35, Info                  CBS    Ending TrustedInstaller initialization.
    2014-10-26 19:21:35, Info                  CBS    Starting the TrustedInstaller main loop.
    2014-10-26 19:21:35, Info                  CBS    TrustedInstaller service starts successfully.
    2014-10-26 19:21:35, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2014-10-26 19:21:35, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2014-10-26 19:21:35, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2014-10-26 19:21:35, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:21:35, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:21:35, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6 [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:21:35, Info                  CBS    SQM: Failed to start always sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:21:35, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2014-10-26 19:21:35, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
    2014-10-26 19:21:35, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
    2014-10-26 19:21:36, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x148fd58
    2014-10-26 19:21:36, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
    2014-10-26 19:21:36, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1c0
    2014-10-26 19:21:40, Info                  CSI    00000007@2014/10/26:17:21:40.337 CSI perf trace:
    CSIPERF:TXCOMMIT;3438911
    2014-10-26 19:21:40, Info                  CBS    NonStart: Success, startup processing not required as expected.
    2014-10-26 19:21:40, Info                  CBS    Startup processing thread terminated normally
    2014-10-26 19:21:40, Info                  CSI    00000008 CSI Store 1493592 (0x0016ca58) initialized
    2014-10-26 19:21:40, Info                  CBS    Session: 30404929_1312426922 initialized by client lpksetup.
    2014-10-26 19:21:42, Info                  CBS    Session: 30404929_1312426922 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
    Hmm looking through the logs it doesn't look like anything critical is corrupted but at the end of the day they are still corrupted files and you may want to consider at some point in refreshing your install.

    Doesn't your system have specific name/model or is it something you built yourself? I know it's old probably circa 2007? Thats the kind of dates I was seeing when searching.. How old is the current install?
     
  9. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    I checked the tower and found that if I type UTOW-CUB in google pictures, it show my pc so I hope that helps a bit.
    (I've also found links from e-bay and they got pictures of how it exactly is but I'm not sure if I'm allowed to post that link. :p )

    Current install is about 4 months old. You're saying the windows instalation wasn't done correctly?
    Is it possible that the hardware related to that may be at fault? The hdd, motherboard, cables or anything like that?

    I'll also upload 2 fresh dump files.
     

    Attached Files:

  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 82c83e63, aa0377d4, 0}
    
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::OpenAllocations+390 )
    
    Followup: MachineOwner
    
    Hi,
    No I'n not saying the installation was done incorrectly. I'm saying you have some corrupt files. Those files don't look critical but non-the-less they are still corrupted. At some point in the future you may want to think about refreshing those files by either a repair or re-install.

    Code:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    The above is blaming part of the graphics section/driver as data in the RAM couldn't be read because either the data or the RAM was corrupted.

    nvlddmkm.sys Wed Jul 02 18:42:25 2014: Try updating to the most recent Nvidia 344.48 driver:
    http://www.nvidia.com/Download/index.aspx?lang=en-us

    Also check your drive using SeaTools:
    http://www.seagate.com/gb/en/support/downloads/seatools/seatools-win-master/

    Check your Graphics using Furmark:
    http://www.ozone3d.net/benchmarks/fur/

    If after making the above changes you still get the bsod then you need to test your RAM.
    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    Try running the test for at least 12hrs unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

    Do you have anything connected vis USB other than keyboard and mouse?
     
  11. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    I got a wifi stick (if that is how it's called), that and my keyboard are connected with a multi usb port.

    Is Memtest86+ V5.01, which is the latest version ok? Also last time I read that I should test each RAM individually, should I remove one, do the test and repeat for the other one or just do a 12hr test while both of them are connected?

    Edit: are those nvidia drivers the right ones for my card? The ones I downloaded were GeForce 9 Series cause those had my card on supported products. Also do I uninstall my previous drivers?
     
    #11 Rodakino, Oct 26, 2014
    Last edited: Oct 26, 2014
  12. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    It might be worth testing to see if your USB Hub has something to do with the bsod as one of your dump files originated from the USB port so it might be worth trying to use the machine without the Hub, if thats possible and see how you go.

    Just test the RAM together as long as it's 12hrs.

    Nvidia link above gives you the option to choose your own driver from the drop down menu. If that isn't your card already on there then simply change it.. :)
     
  13. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Oh ok I thought you had that somehow on the one you wanted me to download :p.
    In that case I do have the latest drivers for that.

    I ran the Seatools and there were 2 tests, one for the HDD and one for the Generic USB SD Reader.
    The HDD passed the test but the USB one showed like 200 errors right from the start and then failed.

    I'll be doing the Furmark soon and put the mem test to run overnight.

    Edit: How do I run the Furmark test? It has lots of options and I don't want to do anything wrong.
     
    #13 Rodakino, Oct 26, 2014
    Last edited: Oct 26, 2014
  14. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Hi,
    Did the USB test fail on a stick that's in the machine right now? If that's the case then I'd remove it to test if it's the cause of the bsod.
    Furmark..... Just try the burn in test and watch your temperatures!
     
  15. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Hello,
    So I did mem test for 12 hours and got 7 passes. I also did furmark for like 5 minutes, didn't know how long to leave it, temperature went up to 70 C, it was pretty stabilized around 68-70.

    The USB test didn't really say which stick it was, just "Generic USB SD Reader".
    Although I've noticed, after some of the bsod, not always, the wifi stick wasn't found so I had to replug it to find it, either in the same usb slot or another. The keyboard and mouse always worked though.

    Thanks again for helping out, I appreciate it. :D
     
  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Hmm..Really? That adds to my growing suspicion that its related to the USB device or the USB driver. What are your chipset/USB drivers like?
     
  17. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Where do I find that? :D
    (Sorry, seems like I know very little..)

    Edit: In CPU-Z it says my chipset is VIA P4M890, I don't know about the drivers : /.
     
    #17 Rodakino, Oct 27, 2014
    Last edited: Oct 27, 2014
  18. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    Hi,

    Sorry for the double post, I had 2 more bsod yesterday, I'll upload the dump files but I don't think there is anything new.

    What should I do about the USB drivers that you mentioned? Any suggestions?

    Thank you for your time!
     

    Attached Files:

  19. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,847
    Likes Received:
    1,568
    Damn... Sorry I must have missed your post yesterday.. I'll look at the dump file now. Did you try removing the USB stick to see if the bsod would stop?
     
  20. Rodakino

    Rodakino New Member

    Joined:
    Oct 25, 2014
    Messages:
    28
    Likes Received:
    0
    I removed the usb hub with the wifi stick on it, so I had only the keyboard and mouse, I didn't see a bsod but I don't think I checked it long enough, I'll do it again today for longer period. Should I try removing all USB and just leave it open?

    Is there a possibility I need drivers or update for chipset or USB or something?
     

Share This Page

Loading...