BSOD Problem & SFCFix logfile - Windows 8.1 x86

Re: SFCFix

Hello, and welcome to Sysnative!

In regards to your SFC problem, despite saying it couldn't fix the issue, SFCFix did actually fix the (very minor and unrelated) issue. To check, can you please re-run sfc /scannow and see if you now get a "no integrity violations found" message.

In regards to your BSOD, please follow these instructions: https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

and post the requested files here. Someone else will help you with that [I'm a SFC & Windows Update helper, you're best off with someone who knows much more about BSODs than me :) ]

Richard
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

Hi,

I'm posting so I can be subscribed for when the dumps are posted : )

Regards,

Patrick
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

I did all that but I couldn't go farther than perfmon /report because it says the admin didn't accept. And I am the admin. I contacted windows support And they had me do all these things and none of them worked. They said I would have to pay to get it resolved and I can't pay so I quite. Now I'm stuck again :(
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

You need to take things one at a time and relax. Ask questions, we'll answer them.

The collection app is forced to run in an elevated environment, however, try and run yours by right clicking > run as admin. If you still get the perfmon error, screw the perfmon and just attach the dumps for now. You can find them in C:\Windows\Minidump. Zip all of them up and then attach the zip to your next post.

Regards,

Patrick
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

Thanks very much.

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

Code:
BugCheck A, {[COLOR=#ff0000]1c5[/COLOR], ff, 1, 81b24354}

Code:
3: kd> !pte 000001c5
                    VA 000001c5
PDE at C0600000            PTE at C0000000
contains 0000000000000000
[COLOR=#ff0000]not valid[/COLOR]

Completely invalid memory was referenced.

Code:
3: kd> .trap ad6a7c10
ErrCode = 00000002
eax=000001c5 ebx=00000071 ecx=a2cd8140 edx=00000000 esi=0011ef76 edi=831fad80
eip=81b24354 esp=ad6a7c84 ebp=ad6a7d14 iopl=0         nv up di pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010006
[COLOR=#4b0082]nt!KiChainedDispatch+0x44[/COLOR]:
81b24354 0000            [COLOR=#ff0000]add     byte ptr [eax],al[/COLOR]          ds:0023:000001c5=??

We have a misaligned instruction pointer, likely due to a stack buffer overflow or memory corruption (both caused by a 3rd party driver).



1.

Code:
3: kd> lmvm asacpi
start    end        module name
9267c000 9267d420   ASACPI     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp:        Thu Aug 12 22:52:52 [COLOR=#ff0000]2004[/COLOR]

Your Asus ATK0110 ACPI Utility driver is nearly ten years old. All pre-2009 versions of this driver are pretty known to cause problems on 7+, so please update your Asus utilities ASAP - Motherboards - P5QL/EPU - ASUS

Alternatively you can uninstall your Asus software as well, as it's unnecessary bloatware.

2. Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing conflicts:

Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

Regards,

Patrick
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

This looks interesting, there's multiple bugchecks.

0x24 NTFS_FILE_SYSTEM

Code:
eax=899d5d90 ebx=92190bca ecx=00000047 [COLOR="#FF0000"]edx=00000000[/COLOR] esi=91886b78 edi=899d5e94
eip=8269ef0a esp=899d5d50 ebp=899d5d68 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210286
[COLOR="#800080"]Ntfs!NtfsFindNameLink+0x29[/COLOR]:
8269ef0a 0fb702          movzx   eax,word ptr [[COLOR="#FF0000"]edx[/COLOR]]       ds:0023:00000000=????

Looking at the last context record for the error we can see that Ntfs!NtfsFindNameLink tried to use a null dereference which tries to access data stored on it, but it's using a null pointer so there's nothing there.

Code:
[COLOR="#800080"]DEFAULT_BUCKET_ID:  NULL_DEREFERENCE[/COLOR]

0xA IRQL_NOT_LESS_OR_EQUAL

Code:
BugCheck A, {[COLOR="#FF0000"]1c5[/COLOR], [COLOR="#800080"]ff[/COLOR], 1, 81b24354}

This indicates pageable system memory was access at an IRQL above 1 which results in an illegal operation and a bugcheck.
The IRQL is currently at ff which is 30 for x86 systems, IRQL 30 is an interrupt level indicating power fail which is the second highest IRQL, that's not good getting that high.

The memory being referenced was 1c5 which isn't valid, we can confirm that by checking the Page Table Entries associated with it.

Code:
3: kd> [COLOR="#006400"]!pte 1c5[/COLOR]
                    VA 000001c5
PDE at C0600000            PTE at C0000000
contains 0000000000000000
[COLOR="#FF0000"]not valid[/COLOR]

This inturn generated the following error:

Code:
3: kd> [COLOR="#008000"]!error 00000002[/COLOR]
[COLOR="#FF0000"]Error code: (Win32) 0x2 (2) - The system cannot find the file specified.[/COLOR]

It was using a bad Instruction Pointer as it was meant to write to a different address.

Code:
[COLOR="#800080"]unable to read from 81c366f4[/COLOR]

Code:
[COLOR="Red"]FAILURE_BUCKET_ID:  IP_MISALIGNED[/COLOR]


With all this said so far I suggest running Memtest86 for at least 8 passes.

Which one should I download?


You have two options to choose from, you can either download the ISO version then burn it do a CD and boot it from there.
The other option is downloading the auto installer for USB sticks, you then boot from that USB stick.
Be warned though, it will format your USB then install the files needed to make it bootable so any files left over will be wiped off.

Download it here:

Memtest86+ - Advanced Memory Diagnostic Tool

So how does it work?

It works by writing a series of test patterns to most memory addresses over 9 tests, it then reads the data back to compare it for errors.

The default pass does 9 different tests varying in access patterns and test data. A tenth pass is optional from the menu which writes all the memory in zeroes then sleeps for 90 minutes and compares it to see if any address have changed, this takes 3 hours per pass each time.

My memtest86 isn't booting! What should I do?

This can be caused by a number of different reasons, common ones include your BIOS not setting using the correct settings, you might want to change your boot priority order.
Other causes include your motherboard not supporting bootable USB sticks in which case you'll need to use a CD (or floppy drive).

Any other issues you might want to look here:

FAQ : please read before posting
 
Last edited:
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

Aww Patrick beat me to it!

Go with Patrick's suggestions first then give Memtest86 a try.

By the way if you didn't know, you can use a link at the top of the thread in thread tools to subscribe to a thread without posting.
Although I suspect you posted it anyway to let Niemiro know you are watching.

Anyway, sorry for butting in.
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

Thank you guys so much, so i deleted Norton but i cant update my asus motherboard drivers because they don't go up to windows 8.1, only to windows 7. But how do i delete the driver i have? i looked for it and it isn't there. maybe i'm just looking in the wrong place lol.
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

The ACPI driver in some cases is mandatory and not removable. It's okay if it's from Windows 7 (the utility), because it's newer than 2004 and you can install the driver regardless. If it gives you problems, use the compatibility troubleshooter and it should work just fine.

Regards,

Patrick
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

Sorry, I forgot to clarify above.

W7 32-bit > Utilities > ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

Regards,

Patrick
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

I downloaded it and when i go to run the .exe file to install it nothing happens, it very briefly opens a command prompt then closes it.
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

I believe that is solved by running it as Administrator if I recal correctly.

Right click on the .exe file and Run as Administrator.
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

unfortunately same results. Maybe I unpacked it wrong or something, ill redownload it and try again.
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

I ran the Troubleshoot compatibility and it did something then restarted my computer so i think it worked lol
 
re: BSOD Problem & SFCFix logfile - Windows 8.1 x86

If you navigate to C:\Windows\System32\Drivers, what is the ASACPI.sys driver date?

Regards,

Patrick
 
Back
Top