BSOD 0x000000D1 0x8FB3F071 Error On Start Up

[LarryB]

Hi there,

I have an Acer Aspire 5732Z.

Windows 7 SP1 32bit
4GB RAM
Intel Pentium duo core 2.1Ghz


I have posted up to these forums before with another BSOD earlier this year. The response was to remove AVG anti virus software. This was done at that point but the issue came back. I replied to that thread and I received no further replies. So I will explain the issue and what I have done to date

On start up in normal mode, the screen display will be extremely fuzzy, a bit like a bad connection on a VGA monitor and desktop. My only option is to hard boot the laptop. After each restart the display gets further, where half the screen would be normal, and the other half fuzzy or black.

Any time I load in safe mode it works perfectly fine. At this point the issue points to a graphics driver issue.

Further launches in normal mode result in BSOD 0x000000D1 0x8FB3F071 Error with DRIVER_IRQL_NOT_LESS_OR_EQUAL

Display drivers were completely removed and reinstalled. Driver updaters were paid for and it does not resolve the issue. I have installed MS Essentials for Antivirus, and I have also run malwarebytes. Scans show up no viruses

On the hardware side, I have run memory tests. Tested each stick of RAM in each RAM slot, one at a time, and I have also tested the RAM in another laptop, with no issues, yet the problem still continues. I have also tested the HDD in another laptop and it works OK.

I was considering reseating the display to motherboard cable.

However, here´s the catch. After an hour or so working in safe mode, as I am now, the laptop startsup fine in normal mode, no display issues or blue screens.

If you look at the sequence of display issues, one would think that he laptop is simply warming up, and once it does it gets going. Not ideal and frustrating!

I have attached a minidump from today´s BSOD. Does it show up anything and can you advise on the above issues and hopefully help resolve the issue I have with this laptop

Many thanks

Larry

 

[Arc]

A stray crash dump is not enough. Click on the button below ...

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[LarryB]

Please find attached DM Log collector attached

I should have mentioned that this is a Home Premium edition of Windows 7, in Spanish!

I have checked some of the created logs and they are also in Spanish. By the looks of it I cannot change the language to English as the OS version does not allow it.

The log was created in Safe Mode. I will try later to get a log in Normal mode

Cheers

Larry

 

[Arc]

The language barrier is a problem for sure, but we have to work within what we have.

A stop 0xD1 is basically a driver caused BSOD, but the crash dumps are not pointing to any failing driver there.

So better you 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.

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

As you have a lot of startup entries there, DV may fail to boot the computer to desktop. You disable the startup items as said below ....

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 and the touchpad driver SynTPEnh.
5. Apply > OK
6. Accept then restart.

_____________________________________________

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8fb3f071, 0, 8, 8fb3f071}

Probably caused by : win32k.sys ( win32k!SleepInputIdle+4e )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 8fb3f071, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 8fb3f071, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d7184c
Unable to read MiSystemVaType memory at 82d50f00
 8fb3f071 

CURRENT_IRQL:  0

FAULTING_IP: 
+363d3b0
8fb3f071 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  winlogon.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  8265b99c -- (.trap 0xffffffff8265b99c)
ErrCode = 00000000
eax=ffb4d6b8 ebx=00000000 ecx=ffb4d8f0 edx=ffb4d770 esi=ffb4d6b8 edi=00000000
eip=979c8b83 esp=8265ba10 ebp=8265ba10 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
win32k!SleepInputIdle+0x4e:
979c8b83 ff155850af97    call    dword ptr [win32k!_imp__PsGetCurrentProcessWin32Process (97af5058)] ds:0023:97af5058=0022eb54
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8fb3f071 to 82c48b7f

FAILED_INSTRUCTION_ADDRESS: 
+363d3b0
8fb3f071 ??              ???

STACK_TEXT:  
8265b884 8fb3f071 badb0d00 8265b8fc 8739ad48 nt!KiTrap0E+0x1b3
WARNING: Frame IP not in any known module. Following frames may be wrong.
8265b8f4 18af5058 85398260 8265b914 82ca2fd2 0x8fb3f071
8265b900 82ca2fd2 00000000 00000000 00000000 0x18af5058
8265b914 82c96e0d 8265b948 18af5058 ffb4d6b8 nt!MiCheckVirtualAddress+0x3b
8265b984 82c48aa8 00000000 18af5058 00000000 nt!MmAccessFault+0x1696
8265b984 979c8b83 00000000 18af5058 00000000 nt!KiTrap0E+0xdc
8265ba10 979cb8bd ffb4d6b8 15d56a63 00000000 win32k!SleepInputIdle+0x4e
8265ba5c 979cb6bc 00000200 00000000 00000000 win32k!xxxRealSleepThread+0x1e5
8265ba78 9797c5a2 00000200 00000000 00000000 win32k!xxxSleepThread+0x2d
8265baec 979bb5e2 00800618 00000047 00000000 win32k!xxxInterSendMsgEx+0xb1c
8265bb3c 979bb725 fe800618 00000047 00000000 win32k!xxxSendMessageTimeout+0x13b
8265bb64 9798bbde fe800618 00000047 00000000 win32k!xxxSendMessage+0x28
8265bb98 979a04c5 97b257c0 00000000 fe800618 win32k!xxxSendChangedMsgs+0x115
8265bbf0 979a0728 00000000 00000000 00000000 win32k!xxxEndDeferWindowPosEx+0x2cc
8265bc10 9799cfd5 fe800618 00000001 00000000 win32k!xxxSetWindowPos+0xf6
8265bcc0 9791ed0d 86f08f78 000000b0 00000000 win32k!xxxCreateDesktopEx+0x568
8265bd14 82c458c6 0019fca8 00000000 00000000 win32k!NtUserCreateDesktopEx+0x9f
8265bd14 774d70f4 0019fca8 00000000 00000000 nt!KiSystemServicePostCall
0019fcc0 00000000 00000000 00000000 00000000 0x774d70f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SleepInputIdle+4e
979c8b83 ff155850af97    call    dword ptr [win32k!_imp__PsGetCurrentProcessWin32Process (97af5058)]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  win32k!SleepInputIdle+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53f7e37f

IMAGE_VERSION:  6.1.7601.18577

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_win32k!SleepInputIdle+4e

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_win32k!SleepInputIdle+4e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xd1_code_av_bad_ip_win32k!sleepinputidle+4e

FAILURE_ID_HASH:  {1d941276-1867-0743-ee46-fb5c52172d3e}

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

 

[LarryB]

Hi there,

Many thanks for the pointers.

After getting a restore point and enabling verifier, on the first restart I cannot get past the Windows splash screen.

I take it that this is not normal.

I will disable verifier.

Am I looking at a fresh install of Windows OS???

Cheers

Larry

 

[Arc]

You should try verifier at first, because if it is not a driver related issue actually, then the clean reinstall will not be helpful there.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

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 and the touchpad driver.
5. Apply > OK
6. Accept then restart.

Then try verifier again. Hopefully it will work properly now.

 

[LarryB]

Hi Arc!

No joy with that. I had to disable verifier again. Laptop starts up fine with just the startup cleared.

Funnily enough today is the first day in months this laptop started up in normal mode at the first attempt.

It took about an hour to get in via nomal mode on Sunday. I expect it to go again as it did many months back.

When I get in via normal mode the first thing I do is Windows Updates, AV and driver update.

However, I would like to get this Verifier working. As before it hangs on the Windows splash screen. I gave it about 15 minutes today and there is no activity on the HDD display light either. Should I try again and give it more time, basically walk away for the night!?

Many thanks

Larry

 

[LarryB]

Hi all,

Before I reinstall W7, are there any alternatives to the MS Verifier that i can try and put stress on drivers to try identify the culprit driver causing the BSOD's?

Many thanks

Larry