BSOD Win7 x64 : Caused By Driver : ntoskrnl.exe

writhziden · 08 Jul 2012

It may also be that the OS is missing updates and that is resulting in problems. Please install all Windows updates. I note that you do not have Service Pack 1 installed.

Install Service Pack 1 (SP1):

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

System Age:

It may also be that your system BIOS version is not new enough to properly support an SSD.

Code:

BIOS Date: 02/05/10 19:13:52 Ver: 08.00.10

You should update your BIOS: ASUS - Motherboards- ASUS P8H67-M LE
Read the manual for steps to update the BIOS.

Did you read my original steps for the SSD?

writhziden said:

SSD Steps:

For the SSD:

Make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Analysis:

Crashes point primarily to your SSD. They could also indicate memory issues. You still have not uploaded the screenshots for your CPU-Z SPD tab for all slots. Please do so in your next post. Screenshots and Files - Upload and Post in Seven Forums

Faeken · 08 Jul 2012

Hello writhziden

It's true the SP1 has not gone because I just re install the PC.
But before this latest installation, the update were all passed

BIOS, it must be a bad transcription because I'm past the 1401 version 2012.05.22

for CPU-Z, now I'm trying with just one RAM
So I can not make you actually a screenshot

If BSOD continue after RAM tests, i'll re install Win 7 on hard drive and disconnect the SSD...

Night Hawk · 08 Jul 2012

If you ran into a bad flash of the bios you would know it! I think your initial impression about the drive might be correct unless you are missing one step of the process needed to see 7 up and running on the SSD. For the present while trying to figure this out you may to toss at least a temp install of 7 on the other OS drive you have to see how that works out in case there's another problem besides any faulty dimm to look into.

As for the "ntoskmi.exe" type error that would an OS related error going back to Windows 2000, XP as well as being seen with Vista and 7 machines. That could be the result of an incomplete install or installation that runs into problem at any time later. That will cause Windows to lock up on you without any BSODs seen however.

Once you have 7 up and running you can check into any SSD diagnostic tool the manufacturer offers to see if the SSD itself has any problem. If any defect is discovered hopefully you would still have time to return for excnange or refund.

writhziden · 09 Jul 2012

Faeken said:

Hello writhziden

It's true the SP1 has not gone because I just re install the PC.
But before this latest installation, the update were all passed

BIOS, it must be a bad transcription because I'm past the 1401 version 2012.05.22

for CPU-Z, now I'm trying with just one RAM
So I can not make you actually a screenshot

If BSOD continue after RAM tests, i'll re install Win 7 on hard drive and disconnect the SSD...

It may help to get an update on the system status.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Faeken · 19 Jul 2012

Hello, It seems to use only one RAM no longer makes BSOD ... I think the problem is solved if everything stays in order. Thank you all for your help

writhziden · 19 Jul 2012

You're welcome. Glad to see it solved!

Night Hawk · 19 Jul 2012

Bad dimm or bad dimm slot? The only way to be 100% sure would be putting the one good dimm in the other slot if the board will run with it there since some boards require certain slots be populated at all times.

Another thing you could try is rubbing the contacts on the dimm you pulled with a pen/pencil firm type eraser going over the contacts lightly to see if the same dimm suddenly runs without any BSODs. Sometimes the contacts on a dimm or expansion card get a little crudded up where that will restore the continuity.