New build Problems

Hi there, New on this bit of the forum, so g'morning.

I recently built a new computer, and the building itself went almost perfectly, so no problems there as far as I know. Here's my rig:

Q6600 (with after m arket AC fan)
8800GT 512MB (from BFG)
500GB HDD
700W Arctic Cooling PSU
MSI P45 Neo-F Mobo
4GB OCZ 800MHz DDR2 RAM
Vista 64bit SP1
CM 690 case

and I think that's all.

The problem is is that it keeps crashing. Not programs crashing, so that I can Ctrl-alt-del out of them, but proper crashing. Even my caps, num, and scroll lock buttons on my keyboard works, nothing.

It usually, afaict, happens either when it's left on screensaver for a while (about 20 mins), or when I' playing a game. At first, I thought it was the game at faul, but it has since occured on my desktop, when only Steam and uTorrent was on.

I really really really would like some help here, because I'm starting to feel as if I've wasted the best part of £600, for something that is barely better than my preious rig.

EDIT: I also occasionally, and inexplicably, disconnect from the net. Not locally, but just from the nternet. Is this a problem my end, or witht the router?

My guess would be that you need to do a good long burn-in cycle on your RAM, 95% of the problems I've had on my last two rigs were directly related to RAM. First, you should check your voltages in BIOS, on my previous computer the RAM required a much higher voltage than the board was giving it at default, my current PC's BIOS also gives my current RAM lower voltage than needed at default. Second, you need to run something like Memtest86+ for at LEAST 72 hours or more. Yes, at least 3 days. I know it's torture because you want to play with your new toy, but you really need to do this. Check it periodically for errors, if it repeatedly crashes try to determine why it's happening. Sometimes RAM sticks just get too hot without adequate cooling and this can be a factor. Sometimes the mobo component voltages are off, like the FSB or mem controller.

Let us know how it goes.

:balloon2:

hmmm, never had to do a 'burn-in' before.

a friend has just bought a near idential rig, i'll ask him if he had any problems.

Quote:

---

Originally Posted by Whacker

My guess would be that you need to do a good long burn-in cycle on your RAM, 95% of the problems I've had on my last two rigs were directly related to RAM. First, you should check your voltages in BIOS, on my previous computer the RAM required a much higher voltage than the board was giving it at default, my current PC's BIOS also gives my current RAM lower voltage than needed at default. Second, you need to run something like Memtest86+ for at LEAST 72 hours or more. Yes, at least 3 days. I know it's torture because you want to play with your new toy, but you really need to do this. Check it periodically for errors, if it repeatedly crashes try to determine why it's happening. Sometimes RAM sticks just get too hot without adequate cooling and this can be a factor. Sometimes the mobo component voltages are off, like the FSB or mem controller.

Let us know how it goes.

:balloon2:

---

Thanks. How do I check what these voltages should be? I will look at the RAM box, but where would the FSB and mem controller voltages be written down?

Also, my internet is slowing to a crawl. On my sidebar network monitor, it says that I'm almsot using all my connection, but I have no idea why or how, as I'm only downloading a few things through bittorrent, and their speeds aren't exactly fast. I've tried pausing everything, but to no avail. what might the problem be?

I sniff some mighty software-sided malice. What Whacker said is more probable though.

Quote:

---

Originally Posted by LeftEyeNine

I sniff some mighty software-sided malice. What Whacker said is more probable though.

---

Doubt it's that: I sarted having these crashes before I connected to the internet.

Quote:

---

Originally Posted by Che Roriniho

Doubt it's that: I sarted having these crashes before I connected to the internet.

---

Pre-loaded programs still bear such doubt.

However, as I said, Whacker is closer to being spot on.

Just a thought: what Operating System are you running? If Windows XP, then try turning off the auto reboot 'feature', so you can actually read the error message (aka Blue Screen of Death) for the crash, giving you more clues to work with.

Look HERE to see how to do that.

If my rig repeatedly crashed AND my 'net connection kept slowing down, I'd suspect some mal-ware infection, and run Antivirus software.

As the fellas above recommended, I'd first look at hardware (memory, voltage, etc) first.

Okay, I've slightly adjusted the voltages (I think), and it crashed while doing the memtest, although this may have been because I turned down the fans, as they were stopping me from sleeping.
I have also noticed it tends to possibly be related to the Vista screensaver,(I'm running Vista Premium 64-bit SP1, btw, and it's an OEM copy, so there are no other softwarez on it.) so I've turned that off. No crashes ince, but I',m still wary.

Thanks guys, you've really helped.

okay, I checked, and apparantly my memory runs at 2.2v, which I didn't believe, as my CMOS appears red when I attempt to set it as this, so I didn't set it that high for fear odf my memory exploding (AND IN THE GAME LOL). Crashes still ocur, but so far only in Rainbow 6 Vegas. still anoying, as I can't get past the first damn building without complete freezeup.

So what do you sugest? should I try at 2.2v, even if the angry red colour tells me not to? It's DDR2, and I thought all DDR2 ran at 1.8v?

You need to run your memory at the manufacturer's recommended value, UNLESS you know exactly what you're doing.

:balloon2:

Quote:

---

Originally Posted by Whacker

You need to run your memory at the manufacturer's recommended value, UNLESS you know exactly what you're doing.

:balloon2:

---

Well I don't know, some places say it's 2.2, others 1.8, and others still 2.1v. I just don't know which one to go for. OCZ say that it's 2.1, but the place I bought it from says 2.2v. Who should I go with?

EDIT: I think the 2.2 was as high as it can go without voiding the warranty. I'll go with 2.1, and report back when I've seen how it goes.

If OCZ says 2.1v, then you go with 2.1v. Using voltages other than what the manuf. specifies is for overclocking and system tweaking. Unless you have a lot of experience and knowledge in that area, then I definitely would NOT advise it, because that's a surefire way to kill hardware.

Quote:

---

Originally Posted by Whacker

If OCZ says 2.1v, then you go with 2.1v. Using voltages other than what the manuf. specifies is for overclocking and system tweaking. Unless you have a lot of experience and knowledge in that area, then I definitely would NOT advise it, because that's a surefire way to kill hardware.

---

Ok, will do. Tommorow, when I have time. Thankyou so much guys, I'm from now on moving all technichal questions from PCGamer's forums (they seem averse to replying :thumbsdown:) to here.

Nope, it's crashing still, even after setting it at 2.1v. This is starting to get on my nadgers.

Have you checked your event log?

Quote:

---

Originally Posted by Xiahou

Have you checked your event log?

---

Where's that?

I'm not as familiar with Vista, but I believe you can just type 'event viewer' in the start/search box thing to get to it. The system log will mostly be where you want to look, but give the others a check too. In particular, note any errors that are logged around the time of a crash.

okay, I'll get the crash again, and see if there's anything there.

Okay, I've crashed again, and lokoed at the 'Errors' event log, and here's what I got:

Spoiler Alert, click show to read: 

Log Name: System
Source: Microsoft-Windows-HttpEvent
Date: 02/09/2008 11:24:43
Event ID: 15016
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-HttpEvent" Guid="{7b6bc78c-898b-4170-bbf8-1a469ea43fc5}" EventSourceName="HTTP" />
<EventID Qualifiers="49152">15016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-02T10:24:43.707Z" />
<EventRecordID>10515</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="64" />
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data Name="DeviceObject">\Device\Http\ReqQueue</Data>
<Data Name="SecurityPackage">Kerberos</Data>
<Binary>000004000200300000000000A83A00C00000000000000000000000000000000000000000000000000E030980</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 02/09/2008 11:24:32
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-02T10:24:32.942Z" />
<EventRecordID>10509</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 02/09/2008 11:24:41
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
The previous system shutdown at 11:22:49 on 02/09/2008 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="2008-09-02T10:24:41.000Z" />
<EventRecordID>10496</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>11:22:49</Data>
<Data>02/09/2008</Data>
<Data>
</Data>
<Data>
</Data>
<Data>9494</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>D8070900020002000B00160031009E03D8070900020002000A00160031009E03600900003C000000010000006009 000000000000B00400000100000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-HttpEvent
Date: 02/09/2008 08:45:01
Event ID: 15016
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-HttpEvent" Guid="{7b6bc78c-898b-4170-bbf8-1a469ea43fc5}" EventSourceName="HTTP" />
<EventID Qualifiers="49152">15016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-02T07:45:01.033Z" />
<EventRecordID>10396</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="72" />
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data Name="DeviceObject">\Device\Http\ReqQueue</Data>
<Data Name="SecurityPackage">Kerberos</Data>
<Binary>000004000200300000000000A83A00C00000000000000000000000000000000000000000000000000E030980</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 02/09/2008 08:44:48
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-02T07:44:48.245Z" />
<EventRecordID>10392</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

I've rechecked, and noticed these at almost all the approximate times of crashing.
Any Help?

My guess is you have a driver and that is not Vista 64bit compatible. Apparently PQNTDrv.SYS is a driver used by PowerQuest but could also be a virus disguised as that so my next guess would be you have a PowerQuest program that is not Vista 64bit compatible.

This Kerberos thing seems to be a bug introduced with SP1 for some people, don't think I ever had it but found a forum where some had it (including freezes) and they say Microsoft advises to ignore it. Since the log entry seems to be on Every Vista SP1 computer(including this notebook here that doesn't freeze) I guess it has nothing to do with the freezes. :shrug:

I think it could be a purely hardware related problem since an incompatible driver should not cause random crashes either way, unless you caught yourself some virus there...

I'm scanning for viruses, but I doubt that's the cause, as I've been having them since pre-internet on my computer.

Also found a load more 1060 errors, not all of them the same as that previous one, whats more, they seem to match approximately up to my crashes:

Spoiler Alert, click show to read: 

Log Name: System
Source: Application Popup
Date: 24/08/2008 20:34:11
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\??\D:\INSTALL\GMSIPCI.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="2008-08-24T19:34:11.296Z" />
<EventRecordID>4789</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\D:\INSTALL\GMSIPCI.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 24/08/2008 20:34:13
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\??\D:\NTGLM7X.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="2008-08-24T19:34:13.137Z" />
<EventRecordID>4793</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\D:\NTGLM7X.sys</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 01/09/2008 12:20:31
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-01T11:20:31.472Z" />
<EventRecordID>10170</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 01/09/2008 12:08:30
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-01T11:08:30.530Z" />
<EventRecordID>10060</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 31/08/2008 16:47:13
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-08-31T15:47:13.316Z" />
<EventRecordID>9714</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 01/09/2008 10:13:50
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-01T09:13:50.039Z" />
<EventRecordID>9940</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 24/08/2008 19:59:46
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\??\D:\INSTALL\GMSIPCI.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="2008-08-24T18:59:46.619Z" />
<EventRecordID>331</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\D:\INSTALL\GMSIPCI.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 02/09/2008 08:44:48
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-02T07:44:48.245Z" />
<EventRecordID>10392</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 02/09/2008 11:24:32
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\SystemRoot\SysWow64\Drivers\PQNTDrv.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="2008-09-02T10:24:32.942Z" />
<EventRecordID>10509</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\SystemRoot\SysWow64\Drivers\PQNTDrv.SYS</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Application Popup
Date: 24/08/2008 19:59:48
Event ID: 1060
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
\??\D:\NTGLM7X.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="2008-08-24T18:59:48.413Z" />
<EventRecordID>334</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\D:\NTGLM7X.sys</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>

The last few times I've had the crashes, instead of it just hanging, it rebots, and then tells be that there was a bluescreen. I know in WinXP Bluescreens dissappeared the second the appeared, is this the same in Vista.

I've also noticed that 3 things happen before a crash (according to the event viewer):
1st, there is an application pop-up. (1060 error)
Then, about 10 seconds later, there is an EventLog error (6008), this says that about 2 minutes ago (from the message) there was a unexpected shutdown. Example:

Spoiler Alert, click show to read: 

Log Name: System
Source: EventLog
Date: 02/09/2008 11:24:41
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Xena
Description:
The previous system shutdown at 11:22:49 on 02/09/2008 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="2008-09-02T10:24:41.000Z" />
<EventRecordID>10496</EventRecordID>
<Channel>System</Channel>
<Computer>Xena</Computer>
<Security />
</System>
<EventData>
<Data>11:22:49</Data>
<Data>02/09/2008</Data>
<Data>
</Data>
<Data>
</Data>
<Data>9494</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>D8070900020002000B00160031009E03D8070900020002000A00160031009E03600900003C000000010000006009 000000000000B00400000100000000000000</Binary>
</EventData>
</Event>

Finnally, there is an HttpEvent (15016). This tells me that Kerberosis anable to initialize for server-side authentication. This doesn't seem to only happen when there is a crash, but it is always in this 3 error part.

Okay, it's happened again, and I've got an error message diolog adter it booted up.

Here it is:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFFA6007384000
BCP2: 0000000000000001
BCP3: FFFFFA600245305B
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini090308-01.dmp
C:\Windows\Temp\WER-31793-0.sysdata.xml
C:\Windows\Temp\WERA9D5.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409


Hope that helps. If you want me to send you the files detailed, just ask, and I'll upload them asap.

Okay, I'm now begging for help.

Another thing I've noticed is that, for example, today, I've had 3 crashes. Each one of them happene earlier than the last crash happened. This is something that, looking back, may be a trend. Guessing through this it could be one of 2 things:

Either somethings overheating, which I doubt, as nothing is overclocked (except my GPU, but I've stresstested that to buggery, so that has no problems.), and all fans are working well. I also have an After-Market cooler, so I doubt it's the CPU. This might be possible, as it resets, as opposed to me turning off, allowing some cool time, then turning on again, so any heat gain would be cluminative.

That, or Memory problems. wouldn't have a clue where to start here, at least in finding a specific fault. It isn't the latency, as I've set that correctly, as per the manufacturers instructions. Likewise the voltage and frequency (2.1v, and 800MHz respectively). The possiblity of one or both of my RAM sticks being a dud seems to be approaching, admittedly it's still in the distance. They'rew OCZ, so I'm not going to start thinking this until I have proof.

Have you tried leaving one of your sticks of RAM out of the system to see if one is bad?

Quote:

---

Originally Posted by Xiahou

Have you tried leaving one of your sticks of RAM out of the system to see if one is bad?

---

Will do at the weekend. I'm determined to rule out all possiblities before it comes to that though.

I ran memest86+ for about 6 hours today, and it didn't pick up any errors, but it still crashes. For the love of all things holy, can somoeone PLEASE tell me what the smeg is wrong with my computer, or at least tell me where I could!

You got WindowBlinds installed ?

Quote:

---

Originally Posted by LeftEyeNine

You got WindowBlinds installed ?

---

No, what would it do?

Look, if no-one here knows what the problem is, could someone please then tell me a website/forum where I might!

I remember WindowBlinds' certain version giving BSOD after installation.

I'd like to suggest one last thing. How about uninstallig every program at once -at least as much as you can before a reboot happens- so that you eventually nothing left on your PC but your OS, nothing else ?

I know that will take some time and you'll consequently get a computer that can only surf the net provided IE comes with the OS itself. After all your PC is not rally functional already and this method would ensure if thre's something related to a software. 'Cause after basic hardware-related inspections, I'd like to know if everything is fine wit softwares as well.

Tomshardware.com forums may be some place to find answers. However, we got pretty geeky techies here as well.

Okay, thanks. This has been happening since I first installed anything: CoD2, so I don't think it's software related, at least, if it is, it's something that comes with OEM Vista Premium SP1.

Let's see how your totally clean system would respond.

Quote:

---

Originally Posted by LeftEyeNine

Let's see how your totally clean system would respond.

---

I'm going to upgrade my BIOS, as someone said on the myriad of forums that I've posted this on that that might help. as I say, I do very much doubt that this is software-related, as it happens universally, and before I even connected to the internet.

I've underclocked my RAM to see if it's a voltage issue, and if it works fine, I'll push up into the ANGRY RED voltages.

It has crashed again. Yes, they're newish games, but my System specs is WAY beyond their reccomended specs. Should I underclock my RAM further (it's on 709MHz, I think), or is that possibilty now eliminated?

Okay, something I've noticed that I'm fairly sure might be the cause of my woes: In ther BIOS, my VDRAM is set to 2.100, and yet is Speedfan,it tells me it' either 1.84 or 1.9, depending on what mood my computer is in.

Could this be anything, and if so, arethere any suggestions as to how I could fix it?

Right, i have now diagnosed that it is probably a mobo problem - if only by process of elimination.
I was tempted to believe it was my RAM, as I haven't had a crash for over a week, but had 2 today. Making up for lost time I guess.
But yes, I think it's now a mobo problem, so what do I do now?

Return it.

A damaged heart always bears the probability of unpredicted failure no matter what kind of treatment it has received.

It's MSI. Who do I call/yell at?

Retailer shop where you got the PC, first. If they fail to co-operate it would be useful to contact MSI with the serial number of your motherboard (serial no. must be printed on the package of the mobo and/or the motherboard itself).

Okay. ebuyer aren't exactly user friendly in that department though >.<

I'll do it at the weekend. Cheers again.