BSOD only in Sim City - ntoskrnl.exe

[philmo]

I just knew I was tempting fate, over a week later after no BSOD - 2 tonight.

Am not aware of doing anything different to machine....so frustrating - was hoping all was now ok.

Any further help greatly appreciated.

 

[philmo]

Any further help would be appreciated - ARC what would you suggest next...

Thanks

 

[Arc]

Both the dumps are resulting the same old D1, with another driver as the probable cause.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff80000b88c2c, 6, 0, fffff880048cbeed}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+b7eed )

Followup: MachineOwner
---------

This time it is the display driver. And I have checked that the display driver is the latest version.

So before altering the display driver, let us do some more checks.

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Then enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

It it crash a couple of times.
Let us know the results, with the subsequent crash dumps, if any.

 

[philmo]

Both the dumps are resulting the same old D1, with another driver as the probable cause.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {fffff80000b88c2c, 6, 0, fffff880048cbeed}
 
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+b7eed )
 
Followup: MachineOwner
---------

This time it is the display driver. And I have checked that the display driver is the latest version.

So before altering the display driver, let us do some more checks.

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Then enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

It it crash a couple of times.
Let us know the results, with the subsequent crash dumps, if any.

Ok, will try all tonight. I note the links to Driver Verifier - is this dangerous in any way? / tricky to use for medium level user?.


Thanks Arc.

 

[Arc]

Not dangerous at all, and no tricks are needed, too. Just take the cautions, that's all
And, at a max, keep the system repair disc beside you.

 

[philmo]

Not dangerous at all, and no tricks are needed, too. Just take the cautions, that's all
And, at a max, keep the system repair disc beside you.

Ok, will give it a go.

Ref "system repair disc " - what do you mean, system recovery point ? or Windows 7 disc for repair?.

Thanks again.

 

[Arc]

I mean this one: http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

 

[philmo]

I mean this one: http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

Ahh ok.

Can I use my Windows 7 disk in a similar way? or just do as you advise.

tks

 

[Arc]

If you have the windows installation disc, that's even better

 

[philmo]

If you have the windows installation disc, that's even better

I do indeed, so I guess I can just use that to boot if all goes badly ?.

Sorry for all the stupid questions, I am a severe pecimist - so want to be ready for the worst.

Would I just insert it, and follow simple instructions to repair ?.

 

[Arc]

I hope nothing will go bad.

If it goes bad, do it.

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

It never happens that a user cannot boot into safe mode too. The repair cd is just for a mental support. In need we can restore the system back using it, to the point created manually before enabling verifier