Multiple BSODs with ntoskrnl.exe as the culprit?

[Bcoolbyte]

Looks like I need to buy it for real, since the trial was only good for one run. I don't mind buying the Basic edition, since it's only $7, but I want to make sure that that will have the functions I need?

 

[Jonathan_King]

Courtesy of usasma.

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

 

[Bcoolbyte]

When he says "when the temperature maxes out", what value would this be? I only ask because on the Furmark site, there's a picture of a GFX card which has been burnt out by the program, and given that I might have to take this one back I'd rather not damage it even more.

 

[Jonathan_King]

Use Speedfan to test your GPU temps.

 

[Bcoolbyte]

I ran it for around 5 minutes, and my temperature got 77C. It didn't seem to have any problems rendering the furry doughnut.

I'm not sure if I did the right thing; I can do it again if need be.

 

[Bcoolbyte]

Ok my brother got another BSOD yesterday, this time while browsing on Facebook. I've attached the crash dump file, while this is what WhosCrashed says about it...

------------------
[FONT=Segoe UI, Arial]On Fri 14/05/2010 21:00:15 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DA90F3, 0xFFFFF880077E5A70, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Dump file: C:\Windows\Minidump\051410-18704-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT]------------------

 

[Bcoolbyte]

I've just tried MemTest just to check my RAM.

I got 9 errors after just 3% of testing. I think I've found my problem.

 

[Jonathan_King]

So do I.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.