Installed Control Centre from PCS website now BSOD.

[jaredjeya]

I later installed the chipset driver direct from Intel, so if theirs is well out of date I don't know what to do.

It's not possible that there are historic dump files on the system, as it was on a brand new SSD:

I had to reinstall Windows on a new SSD after my old one failed.

This is how I made the installation medium:

I made the bootable USB using Windows Media Creation Tool

That was from a colleague's computer, as far as I'm aware that just creates the standard Windows installer for whatever version you pick. I picked the newest Windows 10 version when creating it.

Then I plugged it in and followed the instructions. Drivers were whatever Windows found while installing itself, I don't know exactly how that process works but my computer was functioning fine so I had no concerns. This was on Saturday night and I used my computer a lot on Sunday, rebooting several times, so I'd expect any issues would've shown themselves then.

After Control Centre crashed my PC today, I installed chipset drivers first from PCS. After uploading the logs, I installed chipset drivers from Intel themselves also installed all optional driver updates via Windows Update as per Scott's advice. And then I installed the newest Nvidia drivers from Nvidia themselves. But I haven't tried reinstalling Control Centre yet because it looks like it has a heavy risk of corrupting my system, and I don't just have a spare hard drive to hand to make a system image for a full restore.

PS: Is this OS_Version from the dump files, because it doesn't appear in the logs as far as I can see? Maybe that's the driver Control Centre tried to install and the reason for the crash.

 

[SpyderTracks]

That was from a colleague's computer, as far as I'm aware that just creates the standard Windows installer for whatever version you pick. I picked the newest Windows 10 version when creating it.

Perplexing because it doesn't give you any option as to which version of windows 10 it installs other than pro / home etc. I'm not saying it's not the process you went through, just raises flags on weather it was the official tool. Unless you created the installer using an ISO file?

Drivers were whatever Windows found while installing itself, I don't know exactly how that process works but my computer was functioning fine so I had no concerns. This was on Saturday night and I used my computer a lot on Sunday, rebooting several times, so I'd expect any issues would've shown themselves then.

So you never actually installed the optional updates (which are system drivers)?

I would personally just bite the bullet and do a clean install making sure you've applied all optional updates (except preview OS updates). Only once those are installed and all components are showing successfully configured in device manager do you then install GPU drivers from Nvidia and lastly control center.

It doesn't sound like the drivers were properly configured, plus I'm still confused on the dump file OS signature.

PS: Is this OS_Version from the dump files, because it doesn't appear in the logs as far as I can see?

You'd have to ask @ubuysa

Maybe that's the driver Control Centre tried to install and the reason for the crash.

Control center has nothing to do with a windows version. The number is a windows version number, it's not related to control center in any way.

 

[jaredjeya]

[

Perplexing because it doesn't give you any option as to which version of windows it installs

You're right, it just gives you the newest version of Windows unless you ask otherwise. I was confused with earlier when I downloaded the 22H2 ISO and tried to apply it to the USB using Rufus (which didn't work, as I didn't have admin rights...once I got a computer with admin access, I thought it best to go the more official route).

So you never actually installed the optional updates (which are system drivers)?

I didn't at the time, since it said I should only install those if I had a specific problem, otherwise automatic updates would keep my computer up to date. I have now installed them.

If I can be sure that the version of Control Centre available on PCS's website is the latest version, now that all my drivers seem to be in place, then I can try reinstalling it. But at the moment I don't even know it's Control Centre being out of date itself that's the issue.

 

[SpyderTracks]

[
You're right, it just gives you the newest version of Windows unless you ask otherwise. I was confused with earlier when I downloaded the 22H2 ISO and tried to apply it to the USB using Rufus.


I didn't at the time, since it said I should only install those if I had a specific problem, otherwise automatic updates would keep my computer up to date. I have now installed them.

If I can be sure that the version of Control Centre available on PCS's website is the latest version, now that all my drivers seem to be in place, then I can try reinstalling it. But at the moment I don't even know it's Control Centre being out of date itself that's the issue.

I'm afraid that's not how it works.

For windows, you really have to have the platform properly configured before you go installing anything, especially mishmashing drivers, uninstalling them, overlaying different ones, installing different platforms like .NET or Java when the OS isn't configured.

It all just borks the platform.

You have to have a proper clean platform before you install things, otherwise you tend to get system instability.

I'll bow out from here.

Another question is why it's taking you so long to install your programs, a complete clean install should only take about an hour if you have really complex suites. All the configs should be stored on your data drive, you just install the app and point to the config file. Same with games, just install the launcher and point to your games library.

If it's taking you hours and hours, there's something wrong with the way you're doing it.

 

[jaredjeya]

Another question is why it's taking you so long to install your programs
If it's taking you hours and hours, there's something wrong with the way you're doing it.

There's really no need to be rude. I'm not an experienced sysadmin, I'm just a guy trying to get his laptop working.

 

[SpyderTracks]

There's really no need to be rude. I'm not an experienced sysadmin, I'm just a guy trying to get his laptop working.

Interesting, genuinely don't know what's rude about it, but fine.

If you've got any kind of custom build, you're going to have to level up pretty quickly I'm afraid, this is just basic stuff you'll need to know, you'll have to do this annually at least with major version updates, and you'll need to know how to do basic software and hardware troubleshooting very regularly.

 

[jaredjeya]

Interesting, genuinely don't know what's rude about it, but fine.

If you've got any kind of custom build, you're going to have to level up pretty quickly I'm afraid, this is just basic stuff you'll need to know, you'll have to do this annually at least with major version updates, and you'll need to know how to do basic software and hardware troubleshooting very regularly.

Really? You can't tell what's rude about this? You're making a lot of assumptions about me.

 

[SpyderTracks]

I'm not an experienced sysadmin, I'm just a guy trying to get his laptop working.

I'm going by this thread, you don't know how to configure windows or manage software installs and think that doing so is a sysadmin type role.

No assumptions, all based on this thread and the fact you came on immediately in the red as though it was PCS fault. 9 times out of 10, those are people who don't know what they're doing.

I'll sign off, it's been grand.

 

[Scott]

All just need to step back and relax a bit. I think the wrong foot was set off on initially and it's just not helped the situation at all.

@jaredjeya it's going to be difficult to help from our side without fundamental knowledge unfortunately. Looking through the past few posts it was highlighted that the build install was wrong along with a few other things, to be met with an argument to the case. Unfortunately you are best placed to see and know what is in front of you with the laptop, we have to rely on the relay of that information and I don't think we can really have confidence in that info as a lot of it is contradicting.

I would keep in touch with PCS and go through the install again. There's not a lot else we can advise as there's been back and forth on the system. It genuinely shouldn't take days to install software, so perhaps if you can let us know your process we can help streamline your build.

 

[ubuysa]

FWIW the Windows version that I posted came from the dumps, and the dumps don't lie.

 

[jaredjeya]

I don't know what I can say, I installed Windows 22H2, my computer says it's Windows 22H2. So I've no idea why this version number is popping up, unless the Control Centre installation or something else somehow overwrote the drivers with ones for the wrong version of Windows. The laptop *only* crashed when I tried to install Control Centre - I've had no issue rebooting it multiple times. And I've now installed the latest Intel chipset drivers, from 2023.

This version number also appears multiple places in Device Manager (screenshot). Again, no clue why, because Windows is reporting that its 22H2 Build 19045.4046 in Settings -> System -> About. So I do accept there is something funky going on, but I don't know why or what it is. I certainly didn't install Windows 10 v2004.

The problem is I have no idea how on earth to install the most up to date drivers, all I have access to are the ones on PCS (which are definitely out of date), the ones Windows installs, and what Intel has on their website, and nothing changes this version number. Nowhere do I seem to be able to update the various ACPI drivers.

I could reinstall from scratch. It probably won't take me *that* long, I was including time spent sourcing the SSD, installing it etc., and this time I've written a list of software I need so I can go from that. But I don't want to lose half a day of work doing that if I don't know that it will fix the problem, as I'm already behind, and all the indications I have are that the Control Centre version downloadable from PCS is very out of date anyway. I've no clue if this problem results from that or not following perfect procedure during original windows installation. I also don't know what I would do particularly differently the second time around.

I'm waiting to hear back from PCS tech support at the moment so maybe they'll have something concrete for me.

 

[Scott]

If starting again, this is how I would do it.

Installed Control Centre from PCS website now BSOD.

So, I had to reinstall Windows on a new SSD after my old one failed. I have one of the Tongfang models, specifically Elimina Pro Series: 15.6" Matte QHD 165Hz sRGB 100% LED Widescreen (2560x1440). It was all working fine and I’d spent HOURS reinstalling all my programs. At that point I noticed...

www.pcspecialist.co.uk

 

[ubuysa]

I don't know what to tell you about the WIndows version. Here is the triage analysis of one of the dumps (they're all the same). The WIndows version is near the end of this...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff58cc46b6000, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff807c9c33355, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify timestamp for ACPIDriver.sys

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 4171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6598

    Key  : Analysis.Init.CPU.mSec
    Value: 843

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2504

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 120

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  022624-13781-01.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: fffff58cc46b6000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff807c9c33355

BUGCHECK_P4: 2

READ_ADDRESS: fffff8074fefb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff58cc46b6000 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  GCUService.exe

TRAP_FRAME:  fffff58cc46b5070 -- (.trap 0xfffff58cc46b5070)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff58cc46b5260 rbx=0000000000000000 rcx=fffff58cc46b5ff0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807c9c33355 rsp=fffff58cc46b5208 rbp=fffff58cc46b5310
 r8=00000000000077e8  r9=00000000000000d4 r10=fffff807c9c37130
r11=fffff58cc46b5208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ACPIDriver+0x3355:
fffff807`c9c33355 0f294110        movaps  xmmword ptr [rcx+10h],xmm0 ds:fffff58c`c46b6000=????????????????????????????????
Resetting default scope

STACK_TEXT:  
fffff58c`c46b4dc8 fffff807`4f63ba7d     : 00000000`00000050 fffff58c`c46b6000 00000000`00000002 fffff58c`c46b5070 : nt!KeBugCheckEx
fffff58c`c46b4dd0 fffff807`4f424660     : ffffbb80`000005df 00000000`00000002 fffff58c`c46b50f0 00000000`00000000 : nt!MiSystemFault+0x1d851d
fffff58c`c46b4ed0 fffff807`4f60d358     : fffff58c`c46b52f8 00000000`0000051c ffffd888`78393030 0010019f`00000000 : nt!MmAccessFault+0x400
fffff58c`c46b5070 fffff807`c9c33355     : fffff807`c9c31b1b fffff807`c9c33a10 ffffd888`78736010 fffff58c`c46b56f0 : nt!KiPageFault+0x358
fffff58c`c46b5208 fffff807`c9c31b1b     : fffff807`c9c33a10 ffffd888`78736010 fffff58c`c46b56f0 00000000`00000001 : ACPIDriver+0x3355
fffff58c`c46b5210 fffff807`c9c33a10     : ffffd888`78736010 fffff58c`c46b56f0 00000000`00000001 00000000`00000002 : ACPIDriver+0x1b1b
fffff58c`c46b5218 ffffd888`78736010     : fffff58c`c46b56f0 00000000`00000001 00000000`00000002 00000000`00000070 : ACPIDriver+0x3a10
fffff58c`c46b5220 fffff58c`c46b56f0     : 00000000`00000001 00000000`00000002 00000000`00000070 00000000`656c6946 : 0xffffd888`78736010
fffff58c`c46b5228 00000000`00000001     : 00000000`00000002 00000000`00000070 00000000`656c6946 00000000`00000003 : 0xfffff58c`c46b56f0
fffff58c`c46b5230 00000000`00000002     : 00000000`00000070 00000000`656c6946 00000000`00000003 ffffd888`00000000 : 0x1
fffff58c`c46b5238 00000000`00000070     : 00000000`656c6946 00000000`00000003 ffffd888`00000000 00000000`00000000 : 0x2
fffff58c`c46b5240 00000000`656c6946     : 00000000`00000003 ffffd888`00000000 00000000`00000000 00000000`00000000 : 0x70
fffff58c`c46b5248 00000000`00000003     : ffffd888`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x656c6946
fffff58c`c46b5250 ffffd888`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3
fffff58c`c46b5258 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffd888`00000000


SYMBOL_NAME:  ACPIDriver+3355

MODULE_NAME: ACPIDriver

IMAGE_NAME:  ACPIDriver.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  3355

FAILURE_BUCKET_ID:  AV_W_(null)_ACPIDriver!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {18cee22b-087d-cfc2-2693-5d5468a42838}

Followup:     MachineOwner

 

[jaredjeya]

I don't know what to tell you about the WIndows version. Here is the triage analysis of one of the dumps (they're all the same). The WIndows version is near the end of this...

Sure, but it’s not like I’ve photoshopped the screenshot…so something very odd has happened that I don’t understand, then, where some of the drivers and/or kernel files come from an earlier version of windows. I just wish I understood what happened, so I can avoid repeating that mistake the second time round (which I’m now in the process of doing - I’ll avoid installing control centre itself until I hear back from PCS).

 

[jaredjeya]

Sorry, what I mean is it’s not like I’m lying about what the windows settings page is reporting. (The screenshot was something else). You can also see 22H2 in one of the logs I shared - not the dump file but one of the text files.

 

[jaredjeya]

So, the first thing I did after re-installing windows from the USB stick (wiping clean the entire SSD beforehand) was check the version of ACPI PC in device manager.

Still reporting that same version number. And I do not believe that Windows Media Creation Tool from the official Microsoft website somehow loaded me up with a Frankenstein of Windows 10 2004 and 22H2, so this is what you get in a clean install of Windows.

So there is something else going on here. Perhaps it’s a red herring? I don’t know tbh.

 

[SpyderTracks]

So, the first thing I did after re-installing windows from the USB stick (wiping clean the entire SSD beforehand) was check the version of ACPI PC in device manager.

Still reporting that same version number. And I do not believe that Windows Media Creation Tool from the official Microsoft website somehow loaded me up with a Frankenstein of Windows 10 2004 and 22H2, so this is what you get in a clean install of Windows.

So there is something else going on here. Perhaps it’s a red herring? I don’t know tbh.

I’m afraid your rather reading into things without understanding what you’re seeing. That’s simply a default ACPI driver.

Drivers have no relation to windows. The driver layer sits on top of windows.

The windows OS version has absolutely no connection to what drivers are installed.

 

[ubuysa]

In the Run command box enter the command winver. A small window will open. Post a screenshot of that window.

 

[jaredjeya]

Here you go, Windows 22H2.

 

[ubuysa]

Yep, that's 22H2 and it looks as though the version number that Windows reports in dumps has been 'standardised' to allow for Windows 11 support. Windows 11 reports itself as Windows 10 build 22621 so that apps that look for the windows version (and expect Windows 10) will still run on Windows 11. As part of that it seems they have fixed all Windows 10 versions to show the build number 19041. That's certainly what I'm now seeing across a large range of dumps I have here, many on 22H2 systems. I'd not noticed that before....

Thank you for persevering on this, I've learned something useful today! 👍

Back to the original problem then, can you please download and run the SysnativeBSODCollectionApp. This will collect all the necessary troubleshooting data and write it out to a zip file (SysnativeFileCollectionApp.zip). Please upload that zip file to a cloud service with a link to it here.

The SysnativeBSODCollectionApp does not collect any personally identifying information. It's used by many well-respected Windows help forums, and is known to be safe. If you want to see what data the app collects there are full details here.