Every so often my computer Blue Screens (Of death) and I have to restart my system.

My Operating System - Windows 7 Ultimate

My processor - Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz, 3458 Mhz, 4 Core(s), 8 Logical Processor(s) (Overclocked to 4GHz)

My RAM - 24GB

Hard Drive - 250GB SSDrive (111GB Free)

I have my Processor set to run at 90% currently but I have still received the screen at the recommended 60%.

It seems to do it more when certain projects are close done but I am not sure. It sometimes ruins the work on some projects

It happened while I was away each time and I tried using an auto clicker to keep my "activity" up and it didn't crash nearly as quick except just recently while using it.

Not sure what I am looking for or what the problem is.

EDIT: it just blue screened when the project was ready to upload
Application: Help Fight Childhood Cancer 6.11
Name: HFCC_n1_00792310_n1_0001_0

Upload was successful on reboot

My processor - Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz, 3458 Mhz, 4 Core(s), 8 Logical Processor(s) (Overclocked to 4GHz)

First thing to do when you see any BSOD is stop OC'ing your CPU. You probably went too far.

That said, mind telling us what the BSOD says? There are only a couple of thousand possibilities in which Windows can blue screen... So please help diminish the guesses. :-)

---

I didn't personally overclock it.

It was overclocked by Falcon Northwest, the ones who built my computer.

I have my Processor set to run at 90% currently but I have still received the screen at the recommended 60%.

As in

Use at most   90% of CPU time  
Can be used to reduce CPU heat

??? If yes, recommended by whom?

Gruß,
Gundolf

As in I donate 90% of my processor cycles to the tasks.

I read somewhere on the website that they recommend (and the program default is) 60% of the processor cycles.

I get the BSOD either way.

Considering the processor and its overclocked-ness I have it liquid cooled and just for good measure a fan blowing cool air on the whole system its self.

I get the BSOD either way.

There is not just one BSOD. There are thousands of variants of BSODs in Windows. Please tell us what yours says, just as I asked you before. Then we can look for solutions.

Now you're bringing your car to the garage and says it hums. You don't tell where it hums, you don't tell what kind of hum, but you expect the garage to fix it anyway. Same thing here.

Either write down what the BSOD says, or check if it's been logged in Windows Event Viewer (Start->Administrative Tools->Event Viewer->Windows Logs->System).

---

Well I contemplated copying down what the BSOD said but I didn't really know what was pertinent so I didn't (fail)

I'll copy down stuff next time it happens.

As for my event viewer I still dunno what exactly I am looking for and I don't remember the time the crash happened... Unless you wanna sort though my list of errors. XD

>_< I guess that's a clue to pay more attention. Sorry but I am really tired and have been staying up doing R&D on some projects I am interested in.


EDIT:

PFFFFFFFFT! OMG LOL? That much info behind 12 lines in a table of a massive report list from the very first start of my computer ._. Thats a massive amount of info. Id love to be able to understand any good amount of this.... but alas I do not. DX

This might all be nothing important, if so Just tell me and ill remove this Spam... I mean space consumer X_X

Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 8/23/2010 2:49:30 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Dbric102859
Description:
The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0001.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.835209400Z" />
<EventRecordID>28353</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="60" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">18</Data>
<Data Name="DriverName">Root\SIDESHOW\0001</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WUDFRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 8/23/2010 2:49:30 AM
Event ID: 10114
Task Category: Startup of the UMDF reflector
Level: Information
Keywords: (2)
User: SYSTEM
Computer: Dbric102859
Description:
The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10114</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000002</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.835209400Z" />
<EventRecordID>28352</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="60" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UMDFReflectorDependencyMissing xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<Dependency>WUDFPf</Dependency>
</UMDFReflectorDependencyMissing>
</UserData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 8/23/2010 2:49:30 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Dbric102859
Description:
The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0000.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.835209400Z" />
<EventRecordID>28351</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="60" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">18</Data>
<Data Name="DriverName">Root\SIDESHOW\0000</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WUDFRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 8/23/2010 2:49:30 AM
Event ID: 10114
Task Category: Startup of the UMDF reflector
Level: Information
Keywords: (2)
User: SYSTEM
Computer: Dbric102859
Description:
The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10114</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000002</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.835209400Z" />
<EventRecordID>28350</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="60" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UMDFReflectorDependencyMissing xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<Dependency>WUDFPf</Dependency>
</UMDFReflectorDependencyMissing>
</UserData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 8/23/2010 2:49:30 AM
Event ID: 89
Task Category: (86)
Level: Information
Keywords: (32)
User: SYSTEM
Computer: Dbric102859
Description:
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.
_PSV = 323K
_TC1 = 4
_TC2 = 3
_TSP = 6000ms
_AC0 = 323K
_AC1 = 0K
_AC2 = 0K
_AC3 = 0K
_AC4 = 0K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 6553K
_HOT = 0K
_PSL - see event data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>89</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>86</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000020</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.819609300Z" />
<EventRecordID>28349</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="56" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ThermalZoneDeviceInstanceLength">21</Data>
<Data Name="ThermalZoneDeviceInstance">ACPI\ThermalZone\THRM</Data>
<Data Name="AffinityCount">1</Data>
<Data Name="_PSV">323</Data>
<Data Name="_TC1">4</Data>
<Data Name="_TC2">3</Data>
<Data Name="_TSP">6000</Data>
<Data Name="_AC0">323</Data>
<Data Name="_AC1">0</Data>
<Data Name="_AC2">0</Data>
<Data Name="_AC3">0</Data>
<Data Name="_AC4">0</Data>
<Data Name="_AC5">0</Data>
<Data Name="_AC6">0</Data>
<Data Name="_AC7">0</Data>
<Data Name="_AC8">0</Data>
<Data Name="_AC9">0</Data>
<Data Name="_CRT">6553</Data>
<Data Name="_HOT">0</Data>
<ComplexData Name="_PSL">0000000000000000</ComplexData>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 8/23/2010 2:49:30 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Dbric102859
Description:
The driver \Driver\CLBStor failed to load for the device IDE\CdRomHL-DT-ST_BD-RE__WH08LS20________________2.00____\5&357ea08&0&4.0.0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.804009300Z" />
<EventRecordID>28348</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="60" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">75</Data>
<Data Name="DriverName">IDE\CdRomHL-DT-ST_BD-RE__WH08LS20________________2.00____\5&amp;357ea08&amp;0&amp;4.0.0</Data>
<Data Name="Status">3221226348</Data>
<Data Name="FailureNameLength">15</Data>
<Data Name="FailureName">\Driver\CLBStor</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 8/23/2010 2:49:30 AM
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Dbric102859
Description:
\SystemRoot\SysWow64\Drivers\CLBStor.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Popup" />
<EventID Qualifiers="49152">1060</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.804009300Z" />
<EventRecordID>28347</EventRecordID>
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\CLBStor.SYS</Data>
<Binary>000000000200300000000000240400C0000000006C0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 8/23/2010 2:49:30 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Dbric102859
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:30.398408600Z" />
<EventRecordID>28346</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">257</Data>
<Data Name="BugcheckParameter1">0x19</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0xfffff88002f64180</Data>
<Data Name="BugcheckParameter4">0x2</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 8/23/2010 2:49:41 AM
Event ID: 6013
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Dbric102859
Description:
The system uptime is 16 seconds.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6013</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:41.000000000Z" />
<EventRecordID>28345</EventRecordID>
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>16</Data>
<Data>60</Data>
<Data>300 Eastern Standard Time</Data>
<Binary>31002E003100000030000000570069006E0064006F007700730020003700200055006C00740069006D00610074006500000036002E0031002E00370036003000300020004200750069006C006400200037003600300030002000200000004D0075006C0074006900700072006F0063006500730073006F00720020004600720065006500000037003600300030002E00770069006E0037005F006700640072002E003100300030003600310038002D00310036003200310000003400620061003200610038003800310000004E006F007400200041007600610069006C00610062006C00650000004E006F007400200041007600610069006C00610062006C0065000000390000003800000032003400350036003800000034003000390000004400620072006900630031003000320038003500390000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 8/23/2010 2:49:41 AM
Event ID: 6005
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Dbric102859
Description:
The Event log service was started.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6005</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:41.000000000Z" />
<EventRecordID>28344</EventRecordID>
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security />
</System>
<EventData>
<Binary>DA070800010017000600310029009C010000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 8/23/2010 2:49:41 AM
Event ID: 6009
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Dbric102859
Description:
Microsoft (R) Windows (R) 6.01. 7600 Multiprocessor Free.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6009</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:41.000000000Z" />
<EventRecordID>28343</EventRecordID>
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security />
</System>
<EventData>
<Data>6.01.</Data>
<Data>7600</Data>
<Data>
</Data>
<Data>Multiprocessor Free</Data>
<Data>16385</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 8/23/2010 2:49:41 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Dbric102859
Description:
The previous system shutdown at 2:46:32 AM on ‎8/‎23/‎2010 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-23T06:49:41.000000000Z" />
<EventRecordID>28342</EventRecordID>
<Channel>System</Channel>
<Computer>Dbric102859</Computer>
<Security />
</System>
<EventData>
<Data>2:46:32 AM</Data>
<Data>‎8/‎23/‎2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>2225</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA0708000100170002002E0020006002DA0708000100170006002E0020006002600900003C000000010000006009000000000000B00400000100000000000000</Binary>
</EventData>
</Event>

Dillon 19910

This task

Application: Help Fight Childhood Cancer 6.11
Name: HFCC_n1_00792310_n1_0001_0

is WCG, it having completed 51 million times, so not worried about any code issues. Your logs don't mean much to me... never had to deal with persistent BSOD's though once had a tech totally baffled when running the BSOD screensaver ;-).

Overclocking combined with BOINC throttling can cause expand/shrink effects... 60% means running 3 seconds, pausing 2 seconds, just enough for fails to become intermittent... then 50% will work for more thermal stability, 1 second running, 1 second pause. We recommend to use free TThrottle on Windows systems for hot running systems, specially written as add-on to BOINC. Stable/steady lower load crunching. I've got it running on my W7-32 laptop and desktop, so it's tested, hands on.

Of course, unless it's a new system, dust bunny removal IS a must for power crunchers.

Well my Latest BSOD said there was a hardware problem so I guess it could be an overheat.

I guess I can try turning it down to 10% to see if I still get the screen. If I don't then that is obviously the problem but if so then it would probably eliminate that.

And as for dust, I keep an air purifier within 2 feet of my computer at all times. I can look at my glass side panal and see how much dust the fan pulls in and in these 5 months I have had it, there has been little to no visible dust entering the system.

A hardware problem. Uhuh.

Well, reading through the list of errors you edited in at an earlier post, you have more than one problem. Something with drivers and the Cyberlink Storage Helper. Did you install Windows 7 yourself, or did those people that overclocked your system do this as well? For if so, I'd first turn to them and tell them that the system is highly unstable.

- The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0001.
- The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.
- The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0000.
- The driver \Driver\CLBStor failed to load for the device IDE\CdRomHL-DT-ST_BD-RE__WH08LS20________________2.00____\5&357ea08&0&4.0.0.
- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

All those happening at the same time stamp? Not good.
Any drivers failing to load isn't too good, especially not if it results in an apparent crash of the system.

It has nothing to do with BOINC, that I can tell you. Perhaps that BOINC has found the problem, that because it is putting the CPU and harddrive under load that Windows finds certain drivers aren't up-to-spec. But this would happen with the system as well when you'd go stress it with anything else that would put a good load on the CPU and drive(s).

You can set the run percentages for BOINC to anything and everything you want to, but with that you won't remove the problem, only work around it. You will have to go check if your drivers are all 64bit, all digitally signed, all Windows 7 compatible. And for those pieces of hardware that don't have good drivers, you'll have to either remove them, or get better drivers. Which means that since the system is still under warranty, you'll have to turn to the people who built your computer: Falcon Northwest.

I do hope you can give them better information than "I had the BSOD" and "my Latest BSOD said there was a hardware problem". I'm sorry to be so sarcastic about that, but I did ask twice in this thread for the information pertaining the BSODs you saw, to write down what it said and post that here. Since you refuse to do so, there isn't much help we (or anyone) can give you.

Assuming it's this or that on the basis of seeing it saying "it's a hardware problem", isn't very useful. You will have to tell them (or whomever) the exact message, the STOP Error, the Error number and anything else about it, like mention of specific drivers or a specific piece of hardware.

I wish you luck.

---