Random BSOD multiple times, most recent 0x00000038

[80Clubman]

I have had multiple BSOD, there is nothing that seems connected as they will even happen when the computer is idle. I have tried lots of things, driver updates, a windows hot fix, and a few other things. Looking for some help. I even broke down and took it to the local computer store and they couldn't figure out what was wrong. Although I don't think they put in too much effort. I have attached the dump files as i deleted none of them.

 

[essenbe]

Hello, 80Clubman. I'll try to help, if I can. If you have any more information that may help us, I would appreciate having it. I have looked at the last 5 or 6 dump files and they all blame your graphics driver which is out of date.

fffff880`08d05308  fffff880`04965011Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xad011

igdkmd64
start             end                 module name
fffff880`048b8000 fffff880`04dcf060   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        [COLOR=red]Wed Nov 07 22:01:47 2012[/COLOR] (509B2EAB)
    CheckSum:         0052691E
    ImageSize:        00517060
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update the driver. Your Motherboard's web site for your board is the best place. If you can't find one there, you can try http://downloadcenter.intel.com/Default.aspx

Try that and see if you have better results.

 

[80Clubman]

I deleted the driver and did an got the latest version from the ASUS website for the motherboard. It went two days without issue, then today I got a BSOD again. Attached are the new files. I deleted the drive again and did a reboot today and checked to make sure the file in question was gone before I reloaded the new driver.

 

[80Clubman]

Well this might be good, it crashed again this time with a different issue. Please see attached files.

 

[essenbe]

80Clubman, you had 2 today. Are you sure all of your Windows updates are installed? You may want to check update history and see how many failed updates you have, and also see if you can find an updated Network driver from your Motherboard's web site for your particular board.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff28007c2be1a, 2, 0, fffff880043db788}
*** WARNING: Unable to verify timestamp for NisDrvWFP.sys
*** ERROR: [COLOR=red]Module load completed but symbols could not be loaded for NisDrvWFP.sys[/COLOR]
Probably caused by : NisDrvWFP.sys ( NisDrvWFP+3788 )

That is the Microsoft Network Inspection System Driver

You also had another

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff87f8e68db94, 0, fffff88004ab3ecb, 5}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Could not read faulting driver name
[COLOR=red]Probably caused by : igdkmd64.sys[/COLOR] ( igdkmd64+28aecb )
Followup: MachineOwner

 

[80Clubman]

I have attached screen shots of windows up date for failed and most recent. All the failed ones I am finding on the installed list. View attachment 348683View attachment 348684

 

[essenbe]

OK, as long as the failed ones, later installed. please run 'check for updates' and install any important and recommended updates.
. Keep checking until there are no more. Then open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Please hold down the windows key and press R. You will get a run box, type msconfig in the run box and click run. In the Window that appears, please check the 'Startup' Tab. Please post a screenshot. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Please make sure your SSD Firmware is up to date.

 

[80Clubman]

SFC said no integrity violations. Below is a screen shot of the msconfig startup tab. I am almost to the point of doing a fresh install. Although I don't want to I am wondering if that is my best course of action. View attachment 348952

 

[80Clubman]

The "Onboard" Item is part of Western Digital's Smartware application.

 

[essenbe]

The only thing needed in the startup tab is your anti virus. All of the other programs there will still be available when needed but I know of no reason to run programs unless they are needed at startup. It also helps avoid some driver conflicts.

 

[80Clubman]

Another crash today. Everything but antivirus is turned off in start-up section of msconfig except for Microsoft security essentials. Here is the error code and dump files. 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F16F98, 0xFFFFF880031D2888, 0xFFFFF880031D20E0)

Are we to the point of doing a new windows install?

 

[essenbe]

How about run Seatools for Dos first. Run the short and the long tests. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

If you haven't done it already, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Let me know how that goes and I would like to try one other thing, before a clean install. Also, keep track of your CPU temps.

 

[80Clubman]

What does sea tools look for in the drive? Will it be able to detect anything from a SSD? Just curious I am working on downloading and creating a bootable USB now. Currently the CPU temp is at 27C the motherboard is running the same.

 

[80Clubman]

Also I ran sfc /scannow two days ago with no errors. I will run again.

 

[essenbe]

Probably not necessary for the sfc if you ran it 2 days ago. Seatools checks the drive for defects. I don't think it's necessary on an SSD. They write data different anyway. Just make sure you have the latest firmware for it.

 

[80Clubman]

Firmware is up to date. What is our one last thing to try?

 

[essenbe]

Lets run Driver Verifier. Sort the drivers by provider, then select all drivers not provided by Microsoft. Your computer will seem a little slow and sluggish. That is normal, Run it for 24 hours of actual use, nit just idling. We are hoping it will BSOD and we can catch the bad driver in the dump file. This will tell you how. But, be sure to create a restore point first before doing anything.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

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

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. 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, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.