Project Reality Forums

Hello guys i have install everything good.... all 64bitt drivers

But now i get bluescreen of death, i downloaded bluescreenvieuw and its says it got caused
by driver dxgkrnl.sys and i also got a athor one Caused by driver ntoskrnl.exe

it happens around the 4 our or more, i google it everything but didnt find anything

Pc specs?

Is it new install, did you buy new hardware for it, installed new softwares, did you modify your PC anyway before this lot?

Please post your full PC specs including the make and model of video cards etc.

Also what fans or other cooling do you have?

do you have X-FI sound card? they sometimes cause this. revert its driver

Yes its a new install before this i had a 32bitt windows 7 but the pc can handel 64bitt so i install 64bitt

Cpu : ADM Athlon II X4 640
Motherboard : N68S3 NVIDIA
Memory : GEIL 4GB DDR3
Graphics : Radeon HD 5670
Disk : 300 GB and 500 GB

I also got 3 fans ... 1 on the cpu and 1 on my graphics card en 1 on the front of my pc.
The max tempature is 42 C soo its always cool

Giving a bit of a search on the net:
This website should help you:
NTOSKRNL.EXE is missing or corrupt.

I believe from what you've said your boot.ini was not installed properly in the reinstall of win 7.
So this link may help more:
Additional information and help with the boot.ini.

Edit: But your best bet, if your not 100% computer savvy with the stuff above, is to put the win 7 disk back in and repair the install. It should leave all the files alone, other than the windows system files.

Ensure that All your drivers are up to date. I have recent experience of dxgkrnl BSOD, it turned out my ATI card drivers were the problem.

'[R-DEV wrote:strima;1711915']Ensure that All your drivers are up to date. I have recent experience of dxgkrnl BSOD, it turned out my ATI card drivers were the problem.

Yes, good point, my mouse drivers used to cause BSODS when I first got my PC, the latest ones fixed that, but as you have gone from 32bit to 64bit, its more vital that all of them are up to date. Including motherboard especially, and possibly BIOS, just to name a few that are normally forgotten. They should all be on the manufacturers websites.

i think i found it i had the rong motherboard driver or somthing butt lets hope its fix xD ! im now 10 ours without bluescreen !!! And made a back up LOL xD ! Why you guys so help full !!!!!?

soldier106343 wrote:Why you guys so help full !!!!!?

cuz were nice community and like to help eachother out

Doc.Pock wrote:cuz were nice community and like to help eachother out

1 LOVE !!!! Sick off war Sick off working like a dogg !!!!! FOR NOTING !! ONLY FOR DEATH ! If you feel me (L) !

mkaaaaay...

WEll the bluescreen is back !! I got 3 errors
Caused by driver : ntoskrnl.exe
ndis.sys
dxgkrnl.sys

The dxkrnl.sys whas 2 days ago, so i think thats fix!
Pleace help i wont reset my pc ! I done it like 10 times ! And this problem whas not on the 32bitt.
And yes my pc is 64bitt ! I double check that before i install the 64bitt

Your system is broken unfortunately. Id advise you to take it to someone more experienced to take a look and inspect it, and maybe reinstall the system. Fixing BSODs is pain in the butt, and I know if this would happen to me Id strip it to parts and test everything to make sure its not a hardware problem, and then reinstall system completely. I know its much to do sometimes but it is only way to fix it in most cases if no hardware error is there.

Before you do that you might try this first. Make sure you follow all the steps. Check your CPU and Graphic card for overheating, also check ram and hdd for errors. If not sure how notify me Ill help.

Oke i did a CMD scan and it says : Windows resource Protection found corrupt files but was unable to fix some of them. Details are included in the BBS.log windir\logs\CBS\CBS.log.

So must i try to repair it ?

Instruction on how to read the CBS.log are on the link provided above.

OPTION THREE
How to See and Read Only the "SFC" Scan Results from the CBS.LOG

NOTE: When SFC runs, it logs it's actions into the C:\Windows\Logs\CBS\CBS.log. The steps in this option will show you how to see only the specific SFC entries with the [SR] tags in this CBS.log. This can be helpful to show you what files SFC could not fix automatically if you wanted to try and manually replace them.1. Open a elevated command prompt (right click -> Run as administrator).

2. In the elevated command prompt, copy and paste the command below and press Enter. (See screenshot below)
NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it.

Code: Select all

 findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

3. Close the elevated command prompt.

4. Open the sfcdetails.txt file on your desktop to see the SFC scan details in the CBS.LOG.

5. You can safely delete the sfcdetails.txt file afterwards if you like.

Possibly better option would be to run sfc/scannow at system boot. To do this you will need system repair disk or Windows 7 installation media. See this link for more info.

MaSSive wrote:Instruction on how to read the CBS.log are on the link provided above.

Yes i did it and it found some corupt file ... Yeah i will think about bringing my pc to some guy..

As I understood you have WIn7 64bit Ultimate? Is this correct?

If so, you must have installation disk. If you dont have it, use downloaded ISO image and burn it to DVD and use bootfix method of sfc/scannow. Either way you will need Win7 64bit install disk.

You cant repair it without this.

EDIT: You might try to fix it by doing system restore but make sure to backup your data first just in case.