BSOD after bootup, error 0x0000009f

[socsuec]

Asus notebook n56vz s4037v

When I boot the computer after it has been turned of for a while it runs like it should. Both the intel and the nvidia adapters are visible in the device manager and the fan doesn´t make a lot of noise. After say 5-10 mins I always get a BSOD, machine reboots, the fan starts running continuously and there is no signal anymore from the nvidia adapter. The system now, is completely stable though. To get the machine back to its "normal" running state, I have to leave it turned off for about 30 minutes.

The log was created in the unnormal state so there´s probably no info from the nvidia driver in it.

Thanks in advance

/Kristian

 

[Arc]

Welcome aboard.

There is no dump file in the uploaded zip! Configure windows to make dumps at crashes.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Now search in C:\Windows\minidump manually. Upload the crash dumps.

Do some more things
► http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html
►Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results.

 

[socsuec]

new logs

Hi again!

I have not been able to boot my laptop to the "normal" condition for the whole day but it finally worked again and I got a new BSOD.

New logs are attached.

I tried turning off everything at startup but it had no effect so I turned it on again, thinking it might have been the reason why I wasn´t able to boot it.

/Kristian

 

[Arc]

!devobj fffffa80079b5940 f
fffff80002e8a7d0: Unable to get value of ObpRootDirectoryObject
Device object (fffffa80079b5940) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa80079b5910
 \Driver\ACPI DriverObject fffffa800697fb90
Current Irp 00000000 RefCount 0 Type 00000032 Flags 00000000
DevExt fffffa80069b1010 DevObjExt fffffa80079b5a90 
AttachedDevice (Upper) fffffa800a160040 \Driver[COLOR=Red]\nvlddmkm[/COLOR]
Device queue is not busy.

I would suggest you to uninstall nvidia display driver that you recently updated, and reinstall it again.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, follow option two to search for the appropriate driver for your system automatically, and install it.

Let us know how it worked.

 

[socsuec]

I´ll do that but I hope you understood that I´m not able to access the NVIDIA card nor fiddle with its drivers 90% of the times I boot the machine. Strangely it almost always works after I´ve transported it. I suspected some component might be loose but that´s probably not the case? I read somewhere else that this power state failure happens when a component fails to switch power state and that it usually takes around 10 minutes for the BSOD to happen, which it does for me. What´s that you wrote about ACPI? For me it feels like there´s something wrong with it since I always know when I wount be able to access the NVIDIA card because the fan starts running att full speed as soon as I get logged on to windows. As I said, after a BSOD I ususally have to wait several hours before the system lets me access the NVIDIA card again.

 

[Vir Gnarus]

Yes, it takes around 10 minutes when an IRP (a ticket for hardware I/O) has been started for the system to give up and say it's taking too long, as is with this case. Does this problem happen in Safe Mode as well?

I would think the fan should run at full speed at system startup but then gradually reduce once fan control kicks in and finds full speed isn't needed. Check your BIOS settings to confirm fan control isn't going haywire (or off). In addition, you may wanna go and install updates for your motherboard components and BIOS as well as a just-in-case. Odd fan behavior can be cause by bugs in BIOS/mobo drivers.

Personally the odd hardware behavior (like with the fans) this system is causing reeks of hardware failure. I find the that the Nvidia drivers being blamed, despite being most up-to-date, as being rather curious. However, I noticed that in the IRP the Nvidia driver actually appears that it's waiting for something else. There's a possibility another driver is mishandling a resource the Nvidia driver wants, and due to a bug it ain't letting it go. Something like this can only be told by a kernel dump or larger (the MEMORY.DMP file in Windows directory).

I personally think your video card is bad, and usually for a notebook it means the mobo is bad. Neither of which is easily replaceable in an OEM laptop, so unless you have a currently existing warranty, you may be out of luck. If you wish, you can provide us the kernel dump and we'll look at it, but if this is hardware problems we're dealing with, no amount of crashdump scrutiny will reveal that.