Cheat Engine

Haswell · Posted: Sat Jan 09, 2010 6:17 am Post subject: Random BSOD, 0x0000007f

Recently I've been experiencing BSODs in my Win7 Ultimate x64. They appear randomly and points to ntoskrnl.exe+71f00. With Googling, I've ran memtest86+ for 13 runs without any errors.

kls85 · Posted: Sat Jan 09, 2010 9:09 am Post subject:

Your ntoskrnl.exe is screwed up. Grab the Win7 disc and do a repair or manually replace that bad file.

Haswell · Posted: Sat Jan 09, 2010 7:41 pm Post subject:

I tried repairing using the repair disk I made inside Win7, no luck.

How do I exactly replace the file manually? I can boot off Ubuntu to access and modify system files, so please point me where to start.

Haswell · Posted: Mon Jan 11, 2010 9:27 am Post subject:

Anyone?

hcavolsdsadgadsg · Posted: Mon Jan 11, 2010 12:28 pm Post subject:

sfc /scannow

go go

ShadowHopeful · Posted: Mon Jan 11, 2010 12:34 pm Post subject:

get on the net and download it.

kls85 · Posted: Mon Jan 11, 2010 12:37 pm Post subject:

Go to the sources folder from your Win7 disc and manually copy the file back into C:\Windows\System32.

Before doing that, try doing a auto repair with the Win7 disc itself and see if that works.

Not the repair disc you created in Windows7.

And sfc /scannow is not a internet application, it's command build into the OS.

Dark Byte · Posted: Mon Jan 11, 2010 12:40 pm Post subject:

you're getting a double fault exception

this can happen if the stack of a driver is being corrupted, or if an exception happened that couldn't get handled properly

check for drivers you might have recently installed, or it's caused by faulty hardware that causes a driver to mess up

Haswell · Posted: Mon Jan 11, 2010 5:06 pm Post subject:

The file in the DVD is a .man file. ntoskrnl-dl.man to be exact, inside sources\dlmanifests.

There is nothing called ntoskrnl.exe inside the disk.

Saifallofjmr · Posted: Mon Jan 11, 2010 5:26 pm Post subject:

Here is the vanilla copy of Win7 x64 Ultimate.

http://www.mediafire.com/?lkibt2nwkti

Haswell · Posted: Tue Jan 12, 2010 12:10 pm Post subject:

I replaced ntoskrnl.exe with the one Saifallofjmr provided, more shit happens.

Saifallofjmr · Posted: Tue Jan 12, 2010 3:47 pm Post subject:

I'll give you those too the link is provided below;

http://www.mediafire.com/?nyqy0y4tnw3

Haswell · Posted: Wed Jan 13, 2010 5:24 pm Post subject:

Replacing those files seems to make it even buggier. I'm still getting ntoskrnl.exe errors .same reference code and addresses. Other drivers start popping out on bluescreens.

In BluescreenView, ntoskrnl.exe is always highlighted in every report.

What would cause stuff to fuck up like that?

hcavolsdsadgadsg · Posted: Wed Jan 13, 2010 6:50 pm Post subject:

have you ran an OS integrity check?

all your crashes look like they are coming from microsoft drivers, so it's more than likely a different driver or hardware.

you could try analyzing the saved dump and walking through the stack trace.

Haswell · Posted: Wed Jan 13, 2010 7:01 pm Post subject:

sfc /scannow returned no errors last time (two days ago). Scanning again now.

It's a laptop, no hardware changes since I bought it; no driver updates since I installed Win7.

If anyone would like to review the reports, http://www.mediafire.com/?tmho5m0yozz

Edit: scan complete, no integrity violations.