New
#21
Sadly I spoke too soon. The system just BSODed again, just after I posted that last message.
I have attached the dump file.
And here is another.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Running memtest86+ for only 3 passes is not long enough.
Run memtest86+ for 7 full passes, best to run overnight, if you get any errors you can stop the test.
Have you ran any type of registry cleaner?
Checked that all cables are securely connected?
What anti-virus are you running now?
When was your last scan?
The csrss.exe is Client Server Runtime Subsystem process file which must run all the time on Windows OS.Code:CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. PROCESS_OBJECT: fffffa80058feb30 IMAGE_NAME: csrss.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
Virus's are known to use this file name to hide.
If you haven't ran a full virus scan recently, then do it now.
Also download and run Malwarebytes, be sure to update it before running.
wininit.exe is a Windows system file but should be checked with a virus scan, same as above.Code:CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. PROCESS_OBJECT: fffffa80058149e0 IMAGE_NAME: wininit.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAILURE_BUCKET_ID: X64_0xF4_fffff800c0000005_IMAGE_wininit.exe
If you are getting the same crashes in safe mode that indicates a possible hardware fault.
Let's take a look at the RAM.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important in order to make RAM settings adjustments.
Old drivers.
Update these drivers.
If you can't update these drivers, uninstall the program for testing purposes.
This is a list of drivers not working/loading.Code:CamDrL64.sys Sun Feb 04 02:17:27 2007 - Logitech QuickCam Pro 3000 - http://www.logitech.com/en-gb/support-downloads/downloads?geo=US GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes - http://www.gearsoftware.com Or update iTunes. LMIRfsDriver.sys Tue Jul 15 00:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver - https://secure.logmein.com/US/home.aspx LVUSBS64.sys Sun Feb 04 02:05:16 2007 - Logitech Camera driver - http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en RaInfo.sys Sat Jan 05 02:57:14 2008 - LogMeIn/RemotelyAnywhere Kernel Information Provider - http://www.remotelyanywhere.com/template.asp?page=documentation teamviewervpn.sys Thu Dec 13 17:22:09 2007 - TeamViewerVPN Network Adapter - http://support.teamviewer.com/index.php?group=default&_m=knowledgebase&_a=view&parentcategoryid=13&languageid=1
Unloaded modules:
What USB devices do you have connected?Code:fffff880`087bc000 fffff880`087c7000 tdtcp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 fffff880`087c7000 fffff880`087d6000 tssecsrv.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000F000 fffff880`08600000 fffff880`08639000 RDPWD.SYS Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00039000 fffff880`0b4f4000 fffff880`0b565000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00071000 fffff880`0692b000 fffff880`06939000 MBfilt64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`064a1000 fffff880`0692b000 RTKVHD64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0048A000 fffff880`01630000 fffff880`0163e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`0163e000 fffff880`0164a000 dump_pciidex Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000C000 fffff880`0164a000 fffff880`01655000 dump_msahci. Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 fffff880`01655000 fffff880`01668000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000 fffff880`04945000 fffff880`04952000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 fffff880`04938000 fffff880`04945000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 fffff880`0492b000 fffff880`04938000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 fffff880`0491e000 fffff880`0492b000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 fffff880`048df000 fffff880`048ec000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 fffff880`04074000 fffff880`04076000 USBD.SYS Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00002000 fffff880`04067000 fffff880`04074000 LVUSBS64.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000
Check in Device Manager for any yellow triangles, this indicates driver problems.
Last edited by Dave76; 26 Apr 2012 at 07:13.
In addition to Dave's suggestions you might want to re-install your HdAudio drivers.
Thanks both,
I have tried to answer the questions asked above as succinctly as possible below:
Yes. I have run the most recent version of CCleaner, other than cleaning up some old records for uninstalled programs, there were no other issues identified.Have you ran any type of registry cleaner?
Yes and can confirm that all are fine.Checked that all cables are securely connected?
Microsoft Security Essentials, fully updatedWhat anti-virus are you running now?
A quick scan was performed today with no threats identified. I have not been able to run a full scan as the system BSODs before it can finish.When was your last scan?
I have already updated and run Malwarebytes when this first started occurring, with no threats identified. However again it was only a quick scan and not a full scan as the system will not stay up long enough.Also download and run Malwarebytes, be sure to update it before running.
Im worried the system will BSOD mid-typing, so I will continue in another post.
Below are the requested CPU-Z screen grabs:
Attachment 209168
Attachment 209169
Attachment 209170
Attachment 209171
More to follow:
I have uninstalled or updated these drivers where possible. itunes is already as up to date as possible and I havent got anything installed that I can find for Gearsoft except for perhaps a virtual CD drive, which I have also uninstalled as a precaution.Old drivers.
Update these drivers.
If you can't update these drivers, uninstall the program for testing purposes.
- Logitech Quickcam Pro 3000 - now uninstalledWhat USB devices do you have connected?
- A USB thumb drive is plugged into a port on the back of my monitor. The drive is currently empty but I sometimes use it for transferring files.
There are no yellow triangles in Device ManagerCheck in Device Manager for any yellow triangles, this indicates driver problems.
Real Temp is currently reporting the following. Currently all I am doing is responding to this post so the load is basically idle.Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Attachment 209172
I will try and put some load on and will update you with the temps accordingly.
I will leave it running overnight tonight and update you with the results ASAP.Running memtest86+ for only 3 passes is not long enough.
Run memtest86+ for 7 full passes, best to run overnight, if you get any errors you can stop the test.
I will update with this ASAP once I have figured out where I am looking for them in the BIOS :)Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important in order to make RAM settings adjustments.
I updated the HDAudio drivers just before the last BSOD, is this still showing as an issue? Should I re-install them again?In addition to Dave's suggestions you might want to re-install your HdAudio drivers.
I have now run the Memtest86+ for 20 passes with zero errors.Running memtest86+ for only 3 passes is not long enough.
Run memtest86+ for 7 full passes, best to run overnight, if you get any errors you can stop the test.
I'm not entirely certain if I have all the right items you want, but this is what I could find in the BIOS:Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important in order to make RAM settings adjustments
- CPU Core Voltage set to Auto,- Current voltage: 1.176 V
- CPU I/O voltage set to Auto,Current voltage: 1.176 V
- DRAM Voltage set to Auto,- Current voltage: 1.472 V
- System Agent voltage set to Auto,- Current voltage: 0.920 V
As far as I can see the RAM Voltage is currently 1.64 V
Next will be CPU temps when at load.
Ok I didnt run load tests for these temps, but I was running Battlefield 3, which is about as load intensive as this system would get anyway.
I used Coretemp to show the at load temps, as the screenshots also show what the load was for each CPU.
Attachment 209494
Attachment 209495