SRL Archive - NOTA

Hey guys, just build my first computer, love it.
First time visiting SRL on it :D.

I've had it for about a week now, and I've had a blue screen (the same one) 7 times now.

I've done a bit of research I'm mostly seeing that the problem is most likely improper drivers. I've updated all of my driver many times and that doesn't seem to be the problem.

I've uploaded the dump files for anyone who would like to help me solve the problem.

Here is the output of some dump analyzer program (WhoCrashed)

On Thu 1/20/2011 10:37:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012011-23540-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) 
Bugcheck code: 0xA (0xFFFFFE8005ADA6B8, 0x2, 0x0, 0xFFFFF80002D8AAEF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 

Link to dump files:
http://www.mediafire.com/?bbn76oe21c20va3

Ask for any other information.
Thanks.

Googling for 5 seconds told me that file has something to do with the boot kernal for windows. Maybe something went wrong when installing Windows ? Maybe bad memory? Try running memtest86

Yeah I read that ntoskrnl.exe is some kind of windows kernal thing, and it's a 'generic' reason for a blue screen.
I'm mostly getting information about driver update/drivers conflicting but I've messed/updated with my drivers quite a bit, I may keep trying that though.
Burning memtest86 right now.
Mad memory meaning RAM right?

Yeah, if you have like one incorrectly working sector on your RAM it can fuck up a lot of things.

Otherwise you may just want to try reformating and not doing stupid driver stuff ;). To much hassle especially since it's basically just a new system.

Alright then. So memtest86 will check to see if my RAM is ok. If that all comes out fine I guess I might reformat sometime soon.

Just install Linux! :)

Sorry for the spammy post, but Linux is almost always more informative with their issues. Perhaps loading a Linux live-cd and checking the state of your hardware might be a good plan.

From: Nava2
Just install Linux! :)

Sorry for the spammy post, but Linux is almost always more informative with their issues. Perhaps loading a Linux live-cd and checking the state of your hardware might be a good plan.

Telling that to a gamer does nothing. (I suppose YoHoJo is a gamer? :))

Ran the memtest (and it kept repeating testing by itself) so it run multiple times with no error every time, so I'm pretty sure the memory is just fine.

Well now that I have this computer I am a gamer yes, but I Nava's point is still valid that I can at least use a LiveCD to test the hardware, but like I said after the memtest I'm pretty sure RAM is fine.

This is getting pretty annoying though, I've tried so many things! At least they occur very rarely!

I had some blue screens when i first built my computer, after a memtest and then some prime95, everything worked perfectly. Oh i had to switch my RAM into different slots too that seemed to work :P

From: XcanadamanX
Oh i had to switch my RAM into different slots too that seemed to work :P

This.

In my travels, I remember comming across this several places. Check your MOBO install guide to see which channels should be used first, make sure you have them setup correctly (and in the right priority).

Yeah I know I've moved my RAM around here and there trying to get it to run at the proper Mhz, no luck.

But according to my mobo manual the slots I'm using are fine, but it's worth a try, I'll try different RAM slots next time I get it and see if that helps. Not a bad ieda.

Reseat all peripheral cards & RAM. Check your RAM timings in BIOS. Check for BIOS updates.

Did you get a "firewall" with your mobo or gpu? or anything?

There are a lot of firewalls that give blue screens on w7 that come with your gpu driver or motherboard.. idk why, I've seen a few different ones

From: gratz
Did you get a "firewall" with your mobo or gpu? or anything?

There are a lot of firewalls that give blue screens on w7 that come with your gpu driver or motherboard.. idk why, I've seen a few different ones

What GPU Drivers come with a firewall? Which mobos?

I think I fixed it. My ram (Corsair Dominator DDR3 2X2G) SAY that they clock at 9-9-9-24, but my computer clocked them at 11-11-11-29, so I guess at some point I went into the BIOS and manually changed it to 9-9-9-24, I changed it back about 3 days ago, and so far no problems! Pretty sure that was the problem, woo.

From: YoHoJo
I think I fixed it. My ram (Corsair Dominator DDR3 2X2G) SAY that they clock at 9-9-9-24, but my computer clocked them at 11-11-11-29, so I guess at some point I went into the BIOS and manually changed it to 9-9-9-24, I changed it back about 3 days ago, and so far no problems! Pretty sure that was the problem, woo.

Oh yeah, that slipped my mind. Yeah sometimes RAM won't be at the right settings and things go crazy lol.

From: Capricorn
What GPU Drivers come with a firewall? Which mobos?

http://www.google.com/search?q=mobo+firewall+causing+blue+screen&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a