BSOD from ntoskrnl.exe :S help please.

[forerunner]

Im having some issues with my machine. Ive reinstalled clean installations of windows 7 ultimate 64, 3 times. Changed video cards, CPU's and even tested the RAM and the ram slots.

I get "dxgmms1.sys" blue screens after gaming for a while, somtimes 6 hours in, somtimes right when the game starts after waking my computer up from sleep. Also, almost every time i wake the machine up from sleeping and try to play a game, like crysis 2, the game is all, super speed. like i walk around like i have speed hacks. And, at the same time if i try to start up a game like.... Red Orchestra 2, i am like i am in Slow MO Mode.... or whatever, the opposite where i run slow and see everyone else running slow.

Sometimes i can run this machine for hours and have no problems. and it never happens when the machine isnt under load. All my temps are fine, no overheating no nothing. Sometimes when its acting up, i get window tearing, when i click and drag them around.

Anyways, ive done alot of testing, reinstalled graphics drivers, unistalled them using driver sweeper in safe mode yada yada...

I downloaded Bluescreenview and its saying that; (Ntfs.sys, dxgmms1.sys, atikmdag.sys, and ntsokrnl.exe) are causing problems. or at least they are highlighted as red.

I used driver verifier, selected them all one by one and the only one that causes bsod on boot is NTSOKRNL.EXE. I restart into windows and i get (BAD_POOL_CALL) blue screen and have to use system restore to get back into windows.

as i said, this is a fresh install of windows, so im pretty lost here. any help would be apreciated.

my specs are

AMD phenom II 940
EVGA 730a
Corsair XMX2 ddr2 4 gig
OCZ 600w
500 gig western digital hdd.
XFX 6850

 

[forerunner]

Oh yeah, ive also ran BurninTest and 3dMark11, and cant get the system to crash/overheat with any.

 

[gilpin]

Hi, NTSOKRNL.EXE points towards a hardware error, which can include an unstable overclock.

In terms of your errors:
- dxgmms1.sys is DirectX related
- atikmdag.sys is related to ATI graphics drivers
- Ntfs.sys is hard disk related

So to start with I would suggest updating your motherboard bios and then updating ati graphics drivers, to see how it goes.

Also remove any CPU/GPU/Memory overclocks and see if that helps.

 

[forerunner]

Thanks for the reply,

Ive had this issue with two different graphics cards, both nvidia and Ati. have ran installations of different driver revisions on both.

I may be wrong but by doing what i did with driver verifier, i think i ruled out the other 3 drivers as the causes, themselves. i mean, i know that bluescreens can put out errors as the wrong driver, or whatever. Like bad ram can show as a graphics card error.

The mobo bios is at the lastest update, which is said to involve compatibility updates for x4 cpus. which i just upgraded to. The 940 is "said" to be compatible but EVGA wont officially state such.

Ive had errors before, in the past which called for certain settings in my bios with my ram, which ive gone through already. I wonder if its just possible that the ram i have, (have had) isnt actually bad, or just not completely compatible (ran memtest in the past) and now that im actually asking the machine to do some heavy work like run crysis 2, its saying, no way.

I thought initially that the solution would be to get a new motherboard, but at this point im not totally convinced its just a driver issue.

By running Verifier like that, and geting the machine to BSOD off of that ntsokrnl.exe driver, doesnt that mean that its the cuplrit? I mean, could Re-REinstalling windows again do me any good?

I mean, i had this issue before i switched from the NVIDIA card to the ATI, used driver sweeper too, but i cant remember if i just installed this new graphics card on a fresh, brand new installation of windows and something from then isnt just messing with me... :/

 

[gilpin]

Thanks for the reply,

Ive had this issue with two different graphics cards, both nvidia and Ati. have ran installations of different driver revisions on both.

I may be wrong but by doing what i did with driver verifier, i think i ruled out the other 3 drivers as the causes, themselves. i mean, i know that bluescreens can put out errors as the wrong driver, or whatever. Like bad ram can show as a graphics card error.

The mobo bios is at the lastest update, which is said to involve compatibility updates for x4 cpus. which i just upgraded to. The 940 is "said" to be compatible but EVGA wont officially state such.

Ive had errors before, in the past which called for certain settings in my bios with my ram, which ive gone through already. I wonder if its just possible that the ram i have, (have had) isnt actually bad, or just not completely compatible (ran memtest in the past) and now that im actually asking the machine to do some heavy work like run crysis 2, its saying, no way.

I thought initially that the solution would be to get a new motherboard, but at this point im not totally convinced its just a driver issue.

By running Verifier like that, and geting the machine to BSOD off of that ntsokrnl.exe driver, doesnt that mean that its the cuplrit? I mean, could Re-REinstalling windows again do me any good?

I mean, i had this issue before i switched from the NVIDIA card to the ATI, used driver sweeper too, but i cant remember if i just installed this new graphics card on a fresh, brand new installation of windows and something from then isnt just messing with me... :/

I don't have experience with driver sweeper so cannot comment on that.

The painful yet most thorough way of identifying a hardware error is to take it all out and test 1 by 1. Crysis 2 will as you say push your PC. How old is your PSU, have you discounted that?

 

[forerunner]

The PSU isnt that old, ive checked the voltages on it, everything seems to be up to par. but i mean theres only so much you can test, be hard to be certain that its not undervolting or something or other when its being over stressed, cause you cant just trust something like hwmonitor to tell you the right voltage readings.

Driver sweeper is supposed to delete the left over registry keys/system files from old driver installs, if i am correct. basically just removes whats left over when you go int o control panel and uninstall a driver

 

[chulex67]

Try this:

http://www.tomshardware.com/forum/319017-28-ntoskrnl-locking-core