ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2022 rebuild 3

**Dave-H** · January 10, 2023

6 hours ago, D.Draker said:

I think it has nothing to do with uCyborg and points out to the same ol' spinning disks "feauture".

Why ? Scroll to the most interesting part:

"Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\drivers\dc_fsf.sys

product: DiskCryptor

description: DiskCryptor FS filter"

"This was probably caused by the following module: iastor.sys (iaStor+0x40514)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BE68514, 0xFFFFFFFFAC765720, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\iastor.sys"

https://answers.microsoft.com/en-us/windows/forum/all/iastor-system-error-stop-0x8e/4e9ae6b2-8b77-e011-8dfc-68b599b31bf5

Usually this BSOD indicates conflicts with Intel iastor.sys driver. Rarely (but also possible) - video drivers.

In short, all points out to 360chrome accessing your HDDs.

Well here's my debug output of the BSOD, which is very different.
I hope it isn't being caused by the rebased chrome.dll, I have been using it now for several weeks quite intensively with no problems.
I'll just wait and see how it goes.
I have had occasional BSODs caused by graphics problems, so the fact it happened when I was using 360Chrome could have been just coincidence.
:dubbio:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\WIN-NT\Minidump\Mini011023-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*d:\programf\microsof\windowss.1\debuggin\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*d:\win-nt\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.180912-0606
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 10 00:36:16.963 2023 (UTC + 0:00)
System Uptime: 0 days 0:08:03.966
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf84ad8a, a8300a60, 0}

Probably caused by : win32k.sys ( win32k!PFEOBJ::vFreepfdg+45 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf84ad8a, The address that the exception occurred at
Arg3: a8300a60, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
win32k!PFEOBJ::vFreepfdg+45
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h

TRAP_FRAME:  a8300a60 -- (.trap 0xffffffffa8300a60)
ErrCode = 00000000
eax=e69882b8 ebx=00000000 ecx=00000000 edx=00000000 esi=a8300afc edi=e6ab6c08
eip=bf84ad8a esp=a8300ad4 ebp=a8300ae4 iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
win32k!PFEOBJ::vFreepfdg+0x45:
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h     ds:0023:00000021=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  360chrome.exe

LAST_CONTROL_TRANSFER:  from bf84ae5e to bf84ad8a

STACK_TEXT:  
a8300ae4 bf84ae5e e6b4bb10 00000000 a8300b5c win32k!PFEOBJ::vFreepfdg+0x45
a8300b04 bf8ddbf4 00000000 00000000 00000000 win32k!RFONTOBJ::bDeleteRFONT+0x1d
a8300b28 bf8de157 a8300b5c 00000000 00000014 win32k!PUBLIC_PFTOBJ::bLoadAFont+0x21f
a8300b54 bf870823 e1a9c610 00000000 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x162
a8300c00 bf87050e e57cb2c0 00000000 00000000 win32k!vCleanupPrivateFonts+0xab
a8300c18 bf86ebe3 e57cb2c0 00000000 00000000 win32k!NtGdiCloseProcess+0xb9
a8300c30 bf86bd81 e57cb2c0 00000000 8978d6a0 win32k!GdiProcessCallout+0x102
a8300c4c 805d1e6b 89002020 00000000 8954dfd0 win32k!W32pProcessCallout+0x5c
a8300cf0 805d2153 00000000 a8300d4c 804ff9e1 nt!PspExitThread+0x409
a8300cfc 804ff9e1 8954dfd0 a8300d48 a8300d3c nt!PsExitSpecialApc+0x23
a8300d4c 80541883 00000001 00000000 a8300d64 nt!KiDeliverApc+0x1af
a8300d4c 7eb3e514 00000001 00000000 a8300d64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e1bfde4 00000000 00000000 00000000 00000000 0x7eb3e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!PFEOBJ::vFreepfdg+45
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!PFEOBJ::vFreepfdg+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c93004e

FAILURE_BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+45

BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+45

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

**UCyborg** · January 10, 2023

On 1/9/2023 at 2:16 AM, NotHereToPlayGames said:

There are newer standards, but for the sake of the term "Googlized" that gets thrown around here at MSFN, I'll refer to the 2015 standard.

I do not know what the newer standards bring to the table, but I do know that import, optional chaining, and nullish coalescing has been around since 2015.

2020 - https://262.ecma-international.org/11.0/

6th iteration was in 2015, 11th was in 2020.

On 1/9/2023 at 2:16 AM, NotHereToPlayGames said:

360Chrome v13/13.5 is a 2018 web browser and it complies with import, optional chaining, and nullish coalescing operators.

2020 again.

2 hours ago, Dave-H said:

Well here's my debug output of the BSOD, which is very different.
I hope it isn't being caused by the rebased chrome.dll, I have been using it now for several weeks quite intensively with no problems.

Unlikely, just XP being XP.

**NotHereToPlayGames** · January 10, 2023

29 minutes ago, UCyborg said:

2020 again.

Ah, correct you are. Maybe I was thinking 360Chrome v11.

**D.Draker** · January 10, 2023

7 hours ago, Dave-H said:

Well here's my debug output of the BSOD, which is very different.
I hope it isn't being caused by the rebased chrome.dll, I have been using it now for several weeks quite intensively with no problems.
I'll just wait and see how it goes.
I have had occasional BSODs caused by graphics problems, so the fact it happened when I was using 360Chrome could have been just coincidence.
:dubbio:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\WIN-NT\Minidump\Mini011023-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*d:\programf\microsof\windowss.1\debuggin\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*d:\win-nt\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.180912-0606
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 10 00:36:16.963 2023 (UTC + 0:00)
System Uptime: 0 days 0:08:03.966
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf84ad8a, a8300a60, 0}

Probably caused by : win32k.sys ( win32k!PFEOBJ::vFreepfdg+45 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf84ad8a, The address that the exception occurred at
Arg3: a8300a60, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
win32k!PFEOBJ::vFreepfdg+45
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h

TRAP_FRAME:  a8300a60 -- (.trap 0xffffffffa8300a60)
ErrCode = 00000000
eax=e69882b8 ebx=00000000 ecx=00000000 edx=00000000 esi=a8300afc edi=e6ab6c08
eip=bf84ad8a esp=a8300ad4 ebp=a8300ae4 iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
win32k!PFEOBJ::vFreepfdg+0x45:
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h     ds:0023:00000021=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  360chrome.exe

LAST_CONTROL_TRANSFER:  from bf84ae5e to bf84ad8a

STACK_TEXT:  
a8300ae4 bf84ae5e e6b4bb10 00000000 a8300b5c win32k!PFEOBJ::vFreepfdg+0x45
a8300b04 bf8ddbf4 00000000 00000000 00000000 win32k!RFONTOBJ::bDeleteRFONT+0x1d
a8300b28 bf8de157 a8300b5c 00000000 00000014 win32k!PUBLIC_PFTOBJ::bLoadAFont+0x21f
a8300b54 bf870823 e1a9c610 00000000 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x162
a8300c00 bf87050e e57cb2c0 00000000 00000000 win32k!vCleanupPrivateFonts+0xab
a8300c18 bf86ebe3 e57cb2c0 00000000 00000000 win32k!NtGdiCloseProcess+0xb9
a8300c30 bf86bd81 e57cb2c0 00000000 8978d6a0 win32k!GdiProcessCallout+0x102
a8300c4c 805d1e6b 89002020 00000000 8954dfd0 win32k!W32pProcessCallout+0x5c
a8300cf0 805d2153 00000000 a8300d4c 804ff9e1 nt!PspExitThread+0x409
a8300cfc 804ff9e1 8954dfd0 a8300d48 a8300d3c nt!PsExitSpecialApc+0x23
a8300d4c 80541883 00000001 00000000 a8300d64 nt!KiDeliverApc+0x1af
a8300d4c 7eb3e514 00000001 00000000 a8300d64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e1bfde4 00000000 00000000 00000000 00000000 0x7eb3e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!PFEOBJ::vFreepfdg+45
bf84ad8a f6412180        test    byte ptr [ecx+21h],80h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!PFEOBJ::vFreepfdg+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c93004e

FAILURE_BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+45

BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+45

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

C0000005 is pure Access Violation .

https://learn.microsoft.com/en-us/shows/inside/c0000005

" The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s"."

https://social.technet.microsoft.com/Forums/en-US/07fd6793-e1a1-444c-af23-0a8fada08d99/bsod-0xc0000005-the-instruction-at-0x08lx-referenced-memory-at-0x08lx

I'd start looking at your drivers, try to replace your video driver. You have a quadro card, if I'm not mistaken ?

I wouldn't use anything higher than 347.26 for XP. Also, do you have any home-made drivers ?

I recently solved my BSOD when I deleted the home-brewed Brazilian USB 3.0 drivers, I don't know

if you read that topic, I cleaned them up and no BSOD since then. If you're interested, we can try to nail it down.

And we shall win.

**UCyborg** · January 11, 2023

I remember my XP crashing out-of-the-blue once in win32k.sys when I paused Actual Window Manager. Do I recall correctly that some guys with BSOD problems that use MyPal 68 browser also get crashes in win32k.sys? I wonder if these occurrences are related. I won't make any conclusions since I didn't even dig into details of that one crash that occurred on my end.

Edited January 11, 2023 by UCyborg

**Dave-H** · January 11, 2023

22 minutes ago, D.Draker said:

C0000005 is pure Access Violation .

https://learn.microsoft.com/en-us/shows/inside/c0000005

" The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s"."

https://social.technet.microsoft.com/Forums/en-US/07fd6793-e1a1-444c-af23-0a8fada08d99/bsod-0xc0000005-the-instruction-at-0x08lx-referenced-memory-at-0x08lx

I'd start looking at your drivers, try to replace your video driver. You have a quadro card, if I'm not mistaken ?

I wouldn't use anything higher than 347.26 for XP. Also, do you have any home-made drivers ?

I recently solved my BSOD when I deleted the home-brewed Brazilian USB 3.0 drivers, I don't know

if you read that topic, I cleaned them up and no BSOD since then. If you're interested, we can try to nail it down.

And we shall win.

Thanks but it's only one isolated case so far.
I'm not going to worry about it unless it keeps happening repeatedly.
I don't actually usually use the Quadro card on XP, although I can, I only routinely use it on Windows 10.
I have two cards installed, and there are no Windows 10 drivers for the ATI X600, and (unsurprisingly!) there are no Windows 98 drivers for the Quadro M4000.
There are XP drivers for both, as although there are no official XP Quadro drivers for that card, it actually works with the last XP GeForce driver once it's added to the INF file. The XP and 98 drivers for the X600 card are the last that were issued by ATI/AMD for the card, and have always been pretty stable.
However if I get more BSODs my first action would be to start using the Quadro card on XP to see if it still happens.
Anyway, this is off-topic.

**D.Draker** · January 11, 2023

3 hours ago, UCyborg said:

I remember my XP crashing out-of-the-blue once in win32k.sys when I paused Actual Window Manager. Do I recall correctly that some guys with BSOD problems that use MyPal 68 browser also get crashes in win32k.sys? I wonder if these occurrences are related. I won't make any conclusions since I didn't even dig into details of that one crash that occurred on my end.

Long time ago, my mom had got crashes with XP and Opera, when she could still use PCs (now she's very old) . But then again, Opera is chinese, so maybe the issue is the same with all chinese browsers and XP ?

**NotHereToPlayGames** · January 11, 2023

1 hour ago, UCyborg said:

when I paused Actual Window Manager

<OT>

My systray - recognize anything, @UCyborg?

</OT>

**UCyborg** · January 11, 2023

22 hours ago, Dave-H said:

Thanks but it's only one isolated case so far.
I'm not going to worry about it unless it keeps happening repeatedly.

Aye, hard to be sure anyway if it doesn't occur consistently and you aren't a pro in analyzing these dumps.

22 hours ago, D.Draker said:

Long time ago, my mom had got crashes with XP and Opera, when she could still use PCs (now she's very old) . But then again, Opera is chinese, so maybe the issue is the same with all chinese browsers and XP ?

Blaming it on Chinese is narrow-minded. Any program of such complexity could be exposing bugs in the kernel space.

**Dave-H** · January 11, 2023

Back on topic now please.

**D.Draker** · January 12, 2023

16 hours ago, UCyborg said:

16 hours ago, Dave-H said:

Back on topic now please.

Blaming it on Chinese is narrow-minded. Any program of such complexity could be exposing bugs in the kernel space.

DAVE, Opera and 360 chrome are basically the same - based on chromium and even owned by the same chinese company for ages. But if you say it's off-topic, then be it.

@UCyborg, I for one had actually modded Opera (not just the "translation" thingy), and I can tell you - the similaraties with all chinese made browsers are astonishing, I shall not write about them here, because DAVE doesn't want me to. They usually add more crap upon the clean chrome engine (even new APIs for telemetry), so no , it's not "narrow-minded". More crap - means more chances to crash, esp. on the older OS, like XP. Blaming it on Chinese should kinda be the default option. Check what they added first, and only then - the actual chrome engine.

**Dave-H** · January 12, 2023

2 hours ago, D.Draker said:

DAVE, Opera and 360 chrome are basically the same - based on chromium and even owned by the same chinese company for ages. But if you say it's off-topic, then be it.

It was the general conversation which was developing about BSODs and their causes which was off-topic (and yes, I did contribute to it, but it was in danger of going on for too long.)
Anything directly relating to the browser that this thread is about is fine.

**NotHereToPlayGames** · January 12, 2023

<del>

Edited January 12, 2023 by NotHereToPlayGames

**UCyborg** · January 12, 2023

@D.Draker
Sure, the stuff they put into these browsers in insidious, but I have a hunch the stock normal browser code is pushing it on XP.

BTW, searching "BSOD" keyword on the forum, noticed how often it pop ups on XP sub-forum specifically or other topics where XP is involved?

**D.Draker** · January 12, 2023

3 hours ago, UCyborg said:

@D.Draker
Sure, the stuff they put into these browsers in insidious, but I have a hunch the stock normal browser code is pushing it on XP.

BTW, searching "BSOD" keyword on the forum, noticed how often it pop ups on XP sub-forum specifically or other topics where XP is involved?

@Dave-H said no talking about BSOD here, and DAVE-H knows best.

So sorry, silence from me.

Sign In

ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2022 rebuild 3

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members