Thanks for the informative reply Broni.
There was no need to download MemTest, as it comes with Ubuntu via the grub boot menu and I have used it several times in the past. I only let it go one pass which you can see here:
However, my machine is less than 6months old and my local manufacturer which did the custom build already ran tests to make sure memory was fine. I'm pretty positive that's not the issue, also that would have of effected Ubuntu and it has not done so thus far.
I'd also like to bring up there is a pattern in the event logs I have been posting.
1. Always online when it happens, even when I spend hours doing stuff in Blender and other applications offline with no problems.
2. I always get a WMI error on the first boot after a crash:
Log Name: Application
Source: Microsoft-Windows-WMI
Date: 14/10/2009 8:35:28 AM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Vista-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
<EventID Qualifiers="49152">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-14T12:35:28.000Z" />
<EventRecordID>17381</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Vista-PC</Computer>
<Security />
</System>
<EventData>
<Data>//./root/CIMV2</Data>
<Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99</Data>
<Data>0x80041003</Data>
</EventData>
</Event>3. All BSOD errors point to one file -- "Wdf01000.sys".
==================================================
Dump File : Mini101409-01.dmp
Crash Time : 14/10/2009 8:35:08 AM
Bug Check String :
Bug Check Code : 0x0000010d
Parameter 1 : 00000000`00000007
Parameter 2 : 0000057f`f752ef18
Parameter 3 : fffffa80`08ad10e0
Parameter 4 : fffffa80`08a88900
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+5d03a
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================
==================================================
Dump File : Mini101009-01.dmp
Crash Time : 10/10/2009 9:41:53 PM
Bug Check String :
Bug Check Code : 0x0000010d
Parameter 1 : 00000000`00000007
Parameter 2 : 0000057f`f617e878
Parameter 3 : fffffa80`09e81780
Parameter 4 : fffffa80`08acd9e0
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+5d03a
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================
==================================================
Dump File : Mini100809-01.dmp
Crash Time : 08/10/2009 3:54:22 PM
Bug Check String :
Bug Check Code : 0x0000010d
Parameter 1 : 00000000`00000007
Parameter 2 : 0000057f`f92b0208
Parameter 3 : fffffa80`06d4fdf0
Parameter 4 : fffffa80`0877cc00
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+5d03a
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================
4. Not a single problem on Linux, and fsck and checkdsk reveal no hard drive issues. I also went through a lot to make sure I didn't have a bad HDD this time around, I nuked 4 of them in one year but they were all cheapies and on an old comp. I got my manufacturer to test the drive and also chose the one with the highest non-failure rate according to some online reports.
Basically, I'm pretty sure the hardware is rock solid. Which only leaves one other option the file system corruption which was more than likely done remotely, perhaps due to a currently unknown buffer overflow exploit on that file? That would certainly cause a BSOD. My only question then is, what can one do to stop it.
Thanks for your time and let me know where I can go from here.
Edited by Gaming4JC, 14 October 2009 - 10:26 AM.
Sign In
Create Account
