BSOD every few days on wake up. Help translate dmp files.

[Pcfreak123]

So such power transitions causes memory errors and causes ntoskrnl.exe to be the fault alongside another module if any?

ntoskrnl.exe is never failing. Rather it is the kernel on which the crash took place. When the crash dump recording mechanism fails to detect any failing module, it blames the kernel itself; which is not the true situation.

Also since this occurs is the only work around to turn off such start-up items? Does this still allow them (the drivers) to load if they are disabled in start up/services (how I have them now)? I have read some people do not let their computer sleep for this reason, but I definitely would like mine to sleep so its quiet and sleeping when I am.

Some people who dont let their computer to go to sleep are all desktop users. Portable computers like laptops, notebooks and netbooks run on stored battery power. So the conservation of power is very urgent for those computers. But a desktop runs from direct power, so saving (and so sleep/hibernate) is not any must for it.

All the programs are installed in your computer. You will not loss any of them by disabling startup items. Whenever you need them, go to Start> All Programs and call them. But this rule has three limitations.

Touchpad driver for laptops
Antivirus
Any other special program used for customization, like rainmeter.
​

Besides all discussed above, some other driver (either auto or manual) also may cause BSODs during sleep. In that case we may find them out and take the proper actions for them.

Archie,

My good friend, thank you as usual for the explanation and 101 on such information. I am still waiting for another BSOD but hopefully nothing occurs, its been almost a total of 48 hours so we will see. Also I am a desktop user but it is in the same room where we sleep sometimes so that is why we would like it go to sleep instead of constantly having the fans and all other hardware on.

 

[Arc]

Also I am a desktop user but it is in the same room where we sleep sometimes so that is why we would like it go to sleep instead of constantly having the fans and all other hardware on.

As the option is there, you should be able to use it without any problem. If there are issues, there are solutions, too.

I will be happy to see your computer is running as per your need. Keep in touch.

 

[Pcfreak123]

Also I am a desktop user but it is in the same room where we sleep sometimes so that is why we would like it go to sleep instead of constantly having the fans and all other hardware on.

As the option is there, you should be able to use it without any problem. If there are issues, there are solutions, too.

I will be happy to see your computer is running as per your need. Keep in touch.

Arc,

I hate to tell you this but today it happened again . I got APC_INDEX_MISMATCH (1)

PROCESS_NAME: svchost.exe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

If you would like me to attach the dump file I can. Grrrr I thought I was in the clear.

 

[Arc]

OK, let us see the new files? Blue Screen of Death (BSOD) Posting Instructions

 

[Pcfreak123]

OK, let us see the new files? Blue Screen of Death (BSOD) Posting Instructions

Here are they are. Sorry for the delay. Also please note that the 2 last most recent dumps occurred after I turned on driver verifier because of the dump that happened before those 2. When I enabled driver verifier and restarted my computer would not even boot with constant BSODs pointing to gdrv.sys (as so the mini dumps say) and my start up is completely empty. It seems that this is a gigabyte app center that was running in the background. So I went ahead and downloaded autoruns from sysinternals and unchecked it as well as a few other things that I found in the services that do not show up in start up for some reason but they obviously are starting up? Is this right/ok?

 

[Arc]

The APC Index mismatch BSOD is not showing cause precisely. Which antivirus do you use?

The DV enabled dumps are pointing to Gigabyte motherboard power utility, a gigabyte bloatware. I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

___________________________________________________

BugCheck 1, {77c7132a, 0, ffff, fffff8800cf1bb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

BugCheck C1, {fffff98014b0eff0, fffff98014b0effc, 2b000c, 24}

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

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

 

[Pcfreak123]

The APC Index mismatch BSOD is not showing cause precisely. Which antivirus do you use?

The DV enabled dumps are pointing to Gigabyte motherboard power utility, a gigabyte bloatware. I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

___________________________________________________

BugCheck 1, {77c7132a, 0, ffff, fffff8800cf1bb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

BugCheck C1, {fffff98014b0eff0, fffff98014b0effc, 2b000c, 24}

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

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

I disabled everything in services except any Microsoft services...those I left alone. I am going to see if possibly this fixes it before considering a full clean installation.

Remember how we were talking about power transitions and the drivers that start up at wake up...do the thing in services operate the same way? So this could help?

Thanks in advance as usual for your help.

 

[Arc]

I have noticed that some services from nvidia are problematic and disabling them does it good.

Apparently you should have tried to uninstall the gigabyte programs too. Those are not needed for you. You need the drivers (chipset, network, audio, display) but not the other things.

​

Click these button while installing the drivers and get free trouble!

 

[Pcfreak123]

I have noticed that some services from nvidia are problematic and disabling them does it good.

Apparently you should have tried to uninstall the gigabyte programs too. Those are not needed for you. You need the drivers (chipset, network, audio, display) but not the other things.

​

Click these button while installing the drivers and get free trouble!

I actually did uninstall the gigabyte app control center and just left the important stuff. So back to the waiting game again my friend. Will keep you posted. Have a great day

 

[Arc]

Have a great day

You too.

 

[Pcfreak123]

Have a great day

You too.

Ohh Archie, I am trying. Today is just happened again... take a look at the most recent dump. Gosh how could this be possible.

 

[Pcfreak123]

Have a great day

You too.

Whenever you get a chance please take a look at the latest post. Thank you.

 

[Arc]

Can you apply the 347.09 WHQL display driver and see how it goes?

Before installing it, uninstalled the installed driver using DDU.

Let us know how it goes.
________________________________

BugCheck 19, {3, fffff8a00e672f60, 0, 0}

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

Followup: Pool_corruption
---------

 

[Pcfreak123]

Can you apply the 347.09 WHQL display driver and see how it goes?

Before installing it, uninstalled the installed driver using DDU.

Let us know how it goes.
________________________________

BugCheck 19, {3, fffff8a00e672f60, 0, 0}

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

Followup: Pool_corruption
---------

Archie,

Ive had 2 within the last 24 hours check these out i think one is ntfs and the other bad pool header, can you see if you spot anything? ...But I'm not sure if there is something in there pointing us somewhere. We gotta catch this there is no way we are not seeing it. Im anaylizing away.

 

[Arc]

The same bugcheck, but not very informative.

BugCheck 19, {20, fffff8a01a9de000, fffff8a01a9dec00, 5c00100}

GetPointerFromAddress: unable to read from fffff800034c3100
GetUlongFromAddress: unable to read from fffff800034c31c0
Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+60a )

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

The carsh dump itself saus that driver verifier may be helpful there.

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.

Let us trust it?

 

[Pcfreak123]

The same bugcheck, but not very informative.

BugCheck 19, {20, fffff8a01a9de000, fffff8a01a9dec00, 5c00100}

GetPointerFromAddress: unable to read from fffff800034c3100
GetUlongFromAddress: unable to read from fffff800034c31c0
Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+60a )

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

The carsh dump itself saus that driver verifier may be helpful there.

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.

Let us trust it?

So this has to be a driver issue? Run driver verifier again and hope to catch the right one ?

 

[Arc]

Apparently stop 0x19's are driver related issues. But a failing RAM can disguise any sort of issue, and that is why we suggested for memtest86+ too, in the earlier time.

 

[Pcfreak123]

Apparently stop 0x19's are driver related issues. But a failing RAM can disguise any sort of issue, and that is why we suggested for memtest86+ too, in the earlier time.

Well I ran the test and memory was fine and just to be on the safe side I went and got brand new memory of the same kind and ran test again with no problems. So I would think it is safe to rule memory out.

Can all these errors be hdd related? I ask because my raw read error rate went from 314 to 316 i know its small but was jw.

 

[Arc]

If you have any doubt, you may take the Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test. Let us know the results.

If the HDD is free from errors, and if you feel that it is a good call, can you plan a clean reinstall? As we are not getting any specific error but the issue continues, let us see how it goes with a vanilla install? Then adding the drivers and programs one by and and observing at which point the issue recreates?

If the issue continues even in th vanilla stage, we have to be sure that it is some sort of hardware related issue.

 

[Pcfreak123]

If you have any doubt, you may take the Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test. Let us know the results.

If the HDD is free from errors, and if you feel that it is a good call, can you plan a clean reinstall? As we are not getting any specific error but the issue continues, let us see how it goes with a vanilla install? Then adding the drivers and programs one by and and observing at which point the issue recreates?

If the issue continues even in th vanilla stage, we have to be sure that it is some sort of hardware related issue.

Arc, the harddrive is 100% clean. Also I can try to a whole new clean install but let me say that I did install from a OEM windows 7 ultimate disc, which I dont think contained any bloatware..If I am correct? Does this matter?