Ongoing Fun setting up a new client (1 Viewer)

[2BitSculptor]

... no integrity violations ...

I'm beginning to think it is heat related (I also had the video go black, once), I've ordered 2 aftermarket case fans. I've got the one that came with the enclosure, but it may not be enough. I'm going to set one of the new fans to pull air into the case. Being a super small compact case, 197mm x 197mm x 75mm (LxWxH), it's pretty crowded inside. I've a low profile cpu fan that gives a little clearance under the optical drive, but I think enclosure still needs a little "umph" of air flow.

Right now I'm running it with the top cover off so heat doesn't build up inside. Again, we'll see what happens.

 

[HomeY]

Download Open Hardware Monitor and let that run. It's keeps the Max temps, %, Watts, etc.
Keep an eye on the temps and if you get the BSOD, after windows start, check the Max setting in the tool.
That should give you some extra info.

 

[2BitSculptor]

I put the cover on for the first test. Video went black after about 20 minutes and I had to do a hard stop (pulled the DC power connector)

I took the cover off, booted and ran OHM. I started up MP and TV. after about an hour there were no issues, and still now, after 2 hours. Watage went up and CPU load was at nearly 100% when I (forcibly) stopped test 1. Here is a screen cap from a bit over an hour on the second test. ... I think it verifies, even though temps during the test didn't register too high, Heat is the problem. The values in the first column show results after the hour or so of the second test.

 

[2BitSculptor]

nope.... another BSOD ... I don't know how long it took, I just walked into my office.
at the top:
DRIVER_IRQL_NOT_LESS_OR_EQUAL

at the bottom:
*** iaStorA.sys

I've seen this message before.

 

[2BitSculptor]

new logs

 

[2BitSculptor]

Googled the issue and found it is the Intel Rapid Storage driver ... removed for now, we'll see what happens. Testing continues.

 

[HomeY]

Yeah, agree on the RST drivers.
Also (double check maybe?) your chipset drivers

The temperatures don't look disturbing. < 60 you really don't need to worry for the CPU (although the cores registered lower speeds), but it could be the cause. Not sure when it peaked to 100% CPU load though.

 

[2BitSculptor]

had another BSOD from overnight test. I"ve now updated the onboard graphics driver, reinstalled other drivers from the mobo install disk, and made sure all my MS updates are current. It's been running now for 2 hours, with the cover on, but haven't tried running MediaPortal yet. CPU load did at some time reach 50%, but it has been 2.5% or less currently.

I'm wondering if I've got a bad memory module... at least it is fairly inexpensive to replace. Won't be able to do that till after the coming weekend..

Thanks for all the suggestions!!! ... I think it's getting close.

Of the 4 current systems (and about as many previous) I've put together (2 mini-ITX clients, the micro-ATX Stand Alone, and my office computer) this is the first Intel CPU mobo in more than a decade... and the only one I've had grief with.

 

[breese]

I have been looking thru the Event Viewer Logs.
1-Where did the HD come from? I ask because the logs begin from 2010... It almost appears you did an upgrade to whatever OS was on it?? Just guessing seeing this is a new machine.

2- I do not know this driver
"2/24/2014 9:05:08 PM";"ISCTAgent";"ISCT Agent Service";"Warning";"CAgentState:oPeriodicSuspendResume NetDetect is now disabled since this is not a mobile platform";"1000"

3- This is happening after every restart or crash.
"2/24/2014 9:05:35 PM";"ESENT";"Logging/Recovery";"Information";"Windows (2764) Windows: The database engine is initiating recovery steps.";"300"
"2/24/2014 9:05:36 PM";"ESENT";"Logging/Recovery";"Information";"Windows (2764) Windows: The database engine has begun replaying logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.";"301"

4- This reads as if the permissions are all messed up
"2/24/2014 12:02:23 AM";"EventSystem";"(0)";"Information";"The description for Event ID '1073746449' in Source 'EventSystem' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'86400', 'SuppressDuplicateDuration', 'Software\Microsoft\EventSystem\EventLog'";"1073746449"

I would suggest clearing the Application and System Event logs. This will / might make it easier to find the source of the problem.
Also, if the crash screen has a time indicator, it might help to narrow down in the logs what was happening

 

[2BitSculptor]

I don't recall precisely ... The HD may have come from an old XP install on the other mini-ITX client... which I know I upgraded to 500GB when I installed Win7-64.

Even so, I installed this win7-64 as a new install, not an upgrade. This install has been so different than the other 2 installs. I'm thinking strongly about formatting the drive and starting over on it, fresh.