Current Spec (Unstable) and Upgrade Advice.

[kalniel]

A note from the gigabyte site about using 1866Mhz memory on this board

(Note 2) To reach DDR3 1866 MHz or above, you must install two memory modules and install them in the DDR3_3 and DDR3_4 memory sockets.

See the earlier posts in this thread

edit: for clarity, I mean post #9: http://forums.hexus.net/pc-hardware/...ml#post2636541

[Sputnik]

See the earlier posts in this thread

You mean this one

AFAIK 1866 isn't a supported frequency by the CPU or motherboard,

At least I checked the Gigabyte site first to see if the memory was supported by the motherboard, Which According to Gigabyte - It is!

Ah well, I won't bother in the future - No worries.

[CAT-THE-FIFTH]

Walks into thread again,and sees people talking about the length of their membership and then walks out again.

[scaryjim]

I think what kalniel's trying to says is; It's not the length of your membership that counts, it's what you do with it

Now let's all keep it friendly in here

[peterb]

Guys.. please. These little spats are hardly helpful to the OP are they - and this is the tech section where really nit-picking/point scoring isn't... 'seemly'.

(and it has clearly shocked the HEXUS resident moose!)

I have deleted the less than helpful posts in equal measure, so perhaps we can get on with sorting out the OP's question. All members (sorry moose) are valued here!

[obev0098]

Just to let you know I have corrected my memory speed to 1333, and my system hasn't crashed once. I have also purchased and installed an SSD, my computer is now super fast so thanks for your help. My only issue now is I don't know what game to play lol. Looking forward to XCOM.

I may look into overclocking the system but not sure if I should bother as it seems fast enough.

Thanks.

[obev0098]

Hello Everyone.

Unfortunately my system is still crashing despite the upgrade to the harddrive and the alteration to the clock speed to 1333. Really need help with this as its so frustrating as I cannot see what could possibly cause this issue.

I have got the event viewer open and located the period of the crash but cannot see a stop code anywhere. I have critical alarm and two event alarms, thanks for your help in advance

[Willzzz]

You should see a stop code on the BSOD and afterwards when you get back into windows.

Have you tried changing the memory timings as well as the clock speed?

There is a bit of time between your posts, was there a point where it did seem to be stable?

[obev0098]

Thanks for your reply, I have difficulty locating a "Stop Code". However I have got a crash dump file thats been created.

Yeah the timings has also been changed, the system has not been stable since first reported.

[obev0098]

I used WhoCrashed as previously advised.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 15/10/2012 07:43:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-11200-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6DF8)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000DB5DF8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 15/10/2012 07:43:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgntflt.sys (avgntflt+0x106B9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000DB5DF8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\avgntflt.sys
product: Avira Professional Security
company: Avira Operations GmbH & Co. KG
description: Avira Minifilter Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgntflt.sys (Avira Minifilter Driver, Avira Operations GmbH & Co. KG).
Google query: avgntflt.sys Avira Operations GmbH & Co. KG KMODE_EXCEPTION_NOT_HANDLED

[holy god of nil]

Software (driver) problem by the looks of things, other people reporting same thing after installing avira, try a different AV and see what happens?

[obev0098]

I disabled Avira on startup, it has happened again this evening:

Stop Message was 0x0000001a

On Mon 15/10/2012 17:33:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-11138-01.dmp
uptime: 02:11:06
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005D62700, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 15/10/2012 17:33:45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 02:11:06
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005D62700, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 15/10/2012 07:43:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-11200-01.dmp
uptime: 00:06:58
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6DF8)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000DB5DF8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

[obev0098]

Has anyone got any advice were I could go from here?

Its so frustrating not having a stable system.

[kalniel]

Does look like the memory is still struggling perhaps - beginning to look like faulty modules (hopefully - rather than a faulty memory controller on the CPU/motherboard issue).

Try allowing the motherboard to control memory settings, in case you have accidentally set something wrong (auto or normal setting). You can also use memtest (http://www.memtest.org/) to hopefully find a repeatable test that will provoke a problem rather than having to wait for a crash.

[obev0098]

I'll run memtest, if the system crashes again i'll swap the memory and monitor the results.