Game Says Your Graphics Card Doesn't Meet the Minimum Requirements? Hardware Check, Wrong-GPU Read & VRAM Misread Diagnosis Guide

Key Takeaway
A game that refuses to start over minimum requirements is reporting the result of its own hardware check, not a verdict on your card. The check may be reading the integrated GPU, counting shared memory as VRAM, or misreading the hardware altogether. This guide works through five layers and seven steps to find which one is wrong.
What This Problem Is — and What It Is Not
You press Start, or Play, and before the game has drawn a single frame a message appears: your graphics card does not meet the minimum requirements, or your system does not meet the minimum requirements, and the game closes. Some games offer a Continue or Yes button alongside the warning; others simply exit. Either way, the game never starts.
That scene is the whole problem this guide covers, and its timing is the most important piece of evidence in the diagnosis. The refusal happens at launch, at the moment the game runs its own hardware check, before gameplay begins. It is not a crash partway through a level. It is not a failure to initialise the graphics API. It is not a message saying the driver is too old. The game has looked at the machine, compared what it found against a list of minimum requirements it carries inside itself, and decided the machine does not pass. The question this guide answers is whether that decision is correct — and if it is not, which part of the check went wrong.
Four conditions must all be true before the steps below apply:
- The message appears when the game is launched, at or before the main menu, and names the minimum requirements or the graphics card as the reason it will not start.
- The machine boots into Windows and shows a desktop normally. If there is no display at all, the problem is a display problem, not a minimum-requirements problem, and a different guide applies.
- The message is about hardware meeting a requirement, not about a driver version. A message that says the driver version does not meet the minimum requirement is a driver-version problem, covered by the guide on outdated drivers, and the steps below do not apply to it.
- The reader is looking at a launch-time check, not a failure during play. A game that starts, runs, and then crashes with an out-of-video-memory error is a different problem, covered by the guide on video memory allocation, and the steps below do not apply to it either.
The distinction between a check and a verdict is the idea the whole guide turns on. A hardware check is a small program inside the game. Like any program, it can read the wrong thing, count the wrong number, or be given the wrong information by the system it is reading. Its result is a claim about the hardware, not a measurement of the hardware. When the claim and the hardware disagree, the claim is the thing that needs investigating, not the card. The five suspicion layers below are the five ways that claim can be wrong.
The Exact Words Matter: Copy the Message Before Doing Anything Else
The single most useful habit in this diagnosis is also the simplest: copy down the full text of the message, word for word, before changing anything. Do not paraphrase it from memory. Do not summarise it as "it said my card isn't good enough". Write down exactly what it said, including any numbers it gave and any button it offered.
The reason is that the message itself is the first piece of evidence, and different wordings point at different layers. A message that names the graphics card points at the card. A message that names video memory, with a number in megabytes, points at the memory layer. A message that names system memory points at the RAM, not the card at all. A message that names the processor or the Windows version points at parts of the machine this guide does not cover, and that is itself an answer: the card may be entirely innocent. A message that gives no part name and no number is also evidence, of a different kind — it means the check has not told you what it objected to, and guessing which part it meant is the worst possible next step.
Three details in the message deserve particular attention. First, whether it offers a Continue or Yes button. A check that can be bypassed is a check the game's own authors did not consider a hard barrier, and what happens after pressing Continue — the game runs smoothly, or it stutters, or it crashes — is itself diagnostic information, dealt with in Step 7. Second, whether it gives a number, and what that number is attached to: a memory figure next to the words "video memory" is a different claim from the same figure next to "system memory". Third, when it appears: the moment Start is pressed, or only after reaching the menu. The timing separates a launch-time check from a later failure, and that separation decides which guide applies.
Three wordings that sound alike must never be confused. "Too old" is a statement about age or about a driver version, and it belongs to the driver guide. "Not supported" is a statement about a support list, and it belongs to the capability layer below. "Does not meet the minimum requirements" is a statement about a check, and it is this guide. If the wording is not clear, re-read the message and write it down again. The diagnosis that follows is built on those words, and a diagnosis built on a paraphrase is built on sand.
The Five Suspicion Layers
A minimum-requirements refusal can come from five layers, and they must be kept separate. Mixing them together is how a wrong-GPU problem gets treated with a driver reinstall, or a memory-accounting problem gets treated by buying a new card, and how the real cause survives because the wrong layer was treated. The five layers below are ordered the way the diagnosis should work through them, and each one has its own deciding test.
Layer One: The Message Layer — Which Part Did the Game Name?
The first layer is the message itself. Every publisher writes its own check, and every check looks at different parts: the graphics card model, the dedicated video memory, the system memory, the processor, or the Windows version. The message is the only direct record of what the check objected to. Without it, the rest of the diagnosis is guesswork.
The deciding evidence for this layer is the copied message from the section above. If it names a part, that part is the suspect. If it names a number, that number is the claim to test. If it names nothing, the diagnosis must proceed by elimination, testing each layer in turn rather than assuming the card is the problem. The most common error at this layer is also the simplest: reading a message that says "system does not meet the minimum requirements" as though it said "graphics card does not meet the minimum requirements". The word "system" is doing work in that sentence. It means the check may have objected to the memory or the processor, not the card, and the card may be entirely fine.
Layer Two: The Wrong-GPU Layer — the Game Is Reading the Integrated GPU
The second layer is the most common real cause, and it is the one the diagnosis must test before any hardware number is compared. On a machine with both an integrated GPU and a discrete graphics card, the game may be reading the integrated GPU. If it is, then the check is measuring the integrated GPU against the minimum requirements — and the discrete card, however powerful, is irrelevant, because the game is not looking at it.
This is why the order of the steps matters. Comparing the discrete card's specifications against the store page before confirming which GPU the game is actually reading is wasted work: the numbers may be more than adequate, and the game may still refuse, because the numbers being checked belong to a different chip. The check is not wrong about the integrated GPU. It is wrong about which GPU matters, and that is a different fault with a different fix.
The deciding evidence for this layer is which GPU carries the load while the game runs, checked in Task Manager, and which GPU is selected in the game's own graphics settings. If the integrated GPU is the one working, the game is reading the integrated GPU, and the direction is the GPU-switching procedure — covered by the guide on laptops running games on the integrated GPU — not a driver reinstall and not a new card. If the discrete GPU is the one working, this layer is cleared, and the search moves to the numbers.
Layer Three: The VRAM Layer — the Game Counts Dedicated Video Memory, Not the Total
The third layer is memory accounting, and it is where the most misleading numbers live. The game checks dedicated video memory — the memory built into the graphics card, reserved for the card alone. It does not check the total figure Windows shows, because that total includes shared system memory that the system has set aside for graphics use. Shared memory is not dedicated memory. A machine can show a large total and still have a small dedicated figure, and the game will refuse on the dedicated figure while the total looks more than adequate.
Monitoring software adds a second trap at this layer. The "allocated" or "used" figure a monitoring program shows is a measure of how much memory has been set aside at that moment, and monitoring programs often reserve memory in advance. That figure is not the dedicated memory capacity, and it is not what the game checks. Reading the allocated figure as the capacity is one of the most common errors in this diagnosis, and it produces exactly the confusion this guide exists to clear up: the numbers look sufficient, the game still refuses, and the reader concludes the check must be broken, when in fact the wrong number was being compared.
The deciding evidence for this layer is the dedicated video memory line in Device Manager, in dxdiag, or in GPU-Z — the line that says "dedicated video memory" or "dedicated VRAM", read from one of those three sources and no other. Compare that number, and only that number, against the minimum requirement on the store page. If it meets the requirement, this layer is cleared. If it does not, this layer is the answer, and no driver change will alter it.
Layer Four: The Capability Layer — the Model List and the Feature Level
The fourth layer is capability: some games check not a number but a name, or a capability level. A game may carry an internal list of supported graphics card models, and refuse any card whose name is not on it — including a new card released after the list was written. A newer model is not automatically on an older game's list. Conversely, an older card may support the DirectX version the game asks for in name, while not providing the feature level the game actually requires. Feature level is a capability list, not a version number: dxdiag shows it as a list of levels, such as 11_0, 12_0, and 12_1, and a card either provides a given level or it does not. A card can be DirectX 12 in the broad sense and still lack the specific level a game demands.
The deciding evidence for this layer is the feature level list in dxdiag, on the Display page, read directly — never estimated from the model name. If the level the game requires is not in the list, the capability layer is the answer. If it is in the list, the capability layer is cleared. The model name is not evidence either way. A new model name proves nothing about the support list, and an old model name proves nothing about the feature level. Only the list itself, and the feature level list, count.
Layer Five: The Checker Layer — the Check Itself Can Read Wrong
The fifth layer is the check itself. A hardware check reads information from the system — from the driver, from Windows — and that information can be wrong. A driver can report the wrong hardware version. A particular Windows version can make a game's checker fail to read the hardware correctly, so that a machine which meets the requirements is reported as not meeting them. In that case the refusal is the checker's error, not the hardware's failure, and no change to the card will fix it, because the card was never the problem.
This layer must be stated plainly, because it is the one most often missed: a "does not meet" result is not a hardware verdict. It is the output of a program that can be wrong, and when the hardware has been checked against the store page, the dedicated memory has been read from the right line, the feature level list has been read from dxdiag, and everything meets the requirement, then the remaining explanation is that the checker is misreading the machine. That conclusion can only be earned after the other layers have been tested. Claiming it first, before any check, is guessing. Claiming it last, after the evidence, is diagnosis.
| Layer | What can be wrong | Deciding evidence | What resolves it |
|---|---|---|---|
| 1. Message | The check's own wording is not read, so the wrong part is blamed | The copied message: which part it names, what number it gives, whether it offers Continue | Reading the message before acting |
| 2. Wrong GPU | The game reads the integrated GPU instead of the discrete card | Task Manager load while the game runs; the GPU selected in the game's settings | Getting the game onto the discrete GPU |
| 3. VRAM | The game counts dedicated VRAM; the reader compares the Windows total or a monitoring figure | The dedicated video memory line in Device Manager, dxdiag, or GPU-Z | Comparing the right number; a card change only if the dedicated figure genuinely falls short |
| 4. Capability | The model is not on the game's support list, or the feature level is missing | The dxdiag feature level list; the game's published support list | A supported card, or accepting that the card cannot provide the required level |
| 5. Checker | The checker reads wrong hardware information, because of the driver report or the Windows version | Driver is the current manufacturer version, Windows version is on the game's support page, and the hardware still meets the requirement on every other test | Updating the driver or the Windows version to one the game supports; accepting that the check is at fault |
The Seven Diagnostic Steps
The seven steps below are ordered so that each one tests one layer, and so that no step destroys the evidence a later step needs. Work through them in order, one variable at a time, and write down the result of each step before moving on. Changing two things at once and seeing the game start leaves the reader not knowing which change mattered — and not knowing what to do when the refusal returns.
Step 1: Copy Down the Message, Word for Word
Write down the full message the game showed, exactly as it appeared, including any numbers and whether it offered a Continue or Yes button. Note also when it appeared: the moment Start was pressed, or only after reaching the menu. Note whether the game closed after the message, or stayed open.
This step proves that the problem has been narrowed to a launch-time hardware check, and it records the only direct evidence of what the check objected to. It proves nothing about whether the check is right — that is what the steps below are for. But without the wording, nothing else can be checked against it: the message names the suspect, and the rest of the diagnosis tests that suspect. A note that says "Message: 'Your graphics card does not meet the minimum requirements'; Continue button offered; appears on pressing Play; game exits after OK" is a diagnosis in progress. A note that says "it said my card isn't good enough" is a starting point with no direction.
Step 2: Compare Against the Store Page's Minimum Requirements
Go to the game's official store page or support page and find the "Minimum" system requirements column. Compare it, line by line, against the part the message named. The minimum column is the one that matters. The recommended column is a different bar, for a different experience, and using it as the test will make a machine that passes look as though it fails. Do not compare against the recommended figures.
If the requirement is written unclearly — no part named, no number given — do not guess. Note that the requirement is unclear, and proceed to Steps 3 to 6, which test each layer directly. A vague requirement is a fact about the game's documentation, not a licence to assume the card is the problem. The comparison in this step is only as good as the requirement it compares against, and an unclear requirement means the later steps carry more of the weight.
Step 3: Confirm Which GPU the Game Is Reading
Open Task Manager while the game is running — or while it is attempting to run — and look at which GPU carries the load. Check also the graphics card selection inside the game's own settings, if the game reaches its settings screen. The question is simple: is the game running on the integrated GPU or the discrete card?
If it is running on the integrated GPU, stop here and deal with that first. The game is checking the integrated GPU, and the discrete card's specifications are irrelevant until the game is actually using the discrete card. The switching procedure belongs to the guide on laptops running games on the integrated GPU, and this guide does not repeat it. If the game is running on the discrete card, this layer is cleared, and the search moves to the numbers. Write down which GPU was working, because it is the fact the next person to look at the machine will ask for first.
Step 4: Read the Dedicated Video Memory from the Right Line
Open Device Manager, dxdiag, or GPU-Z, and find the line that reads "dedicated video memory" or "dedicated VRAM". Read that number. Do not read the total figure Windows shows, which includes shared system memory. Do not read the allocated or used figure a monitoring program shows, which reflects what has been set aside at that moment. Compare only the dedicated figure against the minimum requirement from Step 2.
If the dedicated figure meets the requirement, the memory layer is cleared. If it does not, the memory layer is the answer: the card's dedicated memory genuinely falls short of what the game requires, and the direction is a card change, a settings reduction, or cloud streaming — not a driver reinstall, which cannot add dedicated memory to a card. Write the number down, with its source, so that the comparison can be checked later.
Step 5: Read the Feature Level List in dxdiag
Open dxdiag, go to the Display page, and read the feature level list it shows — entries such as 11_0, 12_0, and 12_1. Find the level the game requires, from its store page or support page, and check whether that level appears in the list. Do not estimate the level from the model name. A model name is not a feature level, and two cards with similar names can provide different levels.
If the required level is not in the list, the capability layer is the answer: the card cannot provide what the game demands, whatever its name or its memory figure. If the required level is in the list, the capability layer is cleared, and the search moves to the checker itself. Write the list down, because it is the evidence that separates a capability problem from a checker problem.
Step 6: Check for a Checker Misread
Check three things, in this order. First, whether the driver is the current manufacturer version: compare the four fields in Device Manager — provider, version, date, and the card name — against the version the manufacturer currently lists for this exact card model on its own website. Never write down a version number as a permanent standard; check what the manufacturer lists at the time. Second, whether the Windows version is one the game's support page lists as supported: a Windows version outside the game's supported range can make its checker fail. Third, if another machine that meets the requirements is available, whether the same game starts on it: a game that starts on a comparable machine and refuses on this one points at this machine's checker, not at the game's requirements.
Only when all three have been checked can the checker layer be named. If the driver is current, the Windows version is supported, the hardware meets every requirement on every other test, and the game still refuses, then the refusal is the checker's error. If any of the three is out of line, that is the thing to fix first, and the checker conclusion waits.
Step 7: Decide — and Record What Happened
The decision follows from the steps, and there are only three directions.
If the game offered a Continue button and the game runs acceptably after pressing it, record that result. A check that can be bypassed and a game that then plays smoothly is evidence the check was wrong, not the hardware. Note what "acceptably" meant in practice — the settings used, whether the frame rate held, whether it crashed — because pressing Continue and forgetting the result is not a diagnosis. If the game stutters, crashes, or shows visual corruption after Continue, that is evidence the hardware genuinely falls short, and the Continue button was only a door the game left ajar, not a verdict that the machine is adequate.
If the hardware genuinely falls short — the dedicated memory is below the requirement, or the feature level is missing — the directions are a card change, lower settings, or cloud streaming. Reinstalling the driver will not help: a driver reinstall cannot add memory or add a feature level. Do not spend further time on driver work once the hardware shortfall is established.
If the result is still uncertain after all six steps, bring the machine in with the complete record: the copied message, which GPU the game was reading, the dedicated memory figure and its source, the dxdiag feature level list, and the four driver fields. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
| Step | What to do | What it proves | What it does not prove |
|---|---|---|---|
| 1. Copy the message | Full wording, any numbers, Continue button, timing | The check's claim, recorded exactly | Whether the check is right |
| 2. Compare with the store page | Minimum column only, against the part the message named | Whether the requirement is met on paper | Anything, if the requirement is written unclearly |
| 3. Confirm which GPU the game reads | Task Manager load; the GPU selected in the game's settings | Whether the check is measuring the integrated GPU | Anything about the discrete card's numbers |
| 4. Read dedicated VRAM | Dedicated video memory line in Device Manager, dxdiag, or GPU-Z | Whether the memory the game counts meets the requirement | Anything about the feature level |
| 5. Read the feature level list | dxdiag Display page, feature level list | Whether the card provides the required level | Anything about the checker |
| 6. Check for a checker misread | Current manufacturer driver; supported Windows version; same game on another machine if available | Whether the checker is reading the hardware wrong | Anything, until all three have been checked |
| 7. Decide | Press Continue and test properly, or accept a genuine shortfall, or bring the record in | Which direction follows from the evidence | Anything beyond the test that was actually run |
Six Common Misconceptions
Misconception 1: The message means the card is not good enough
No. "Does not meet" is the result of a check, not a verdict on the hardware. The game may be reading the wrong GPU, counting the wrong memory figure, or running a checker that misreads the machine. The card may be entirely adequate, and the check may still refuse it. The message is a claim to investigate, not a conclusion to accept. Only after the five layers have been tested can the card itself be blamed.
Misconception 2: Windows shows plenty of video memory, so the game must have enough
No. The total Windows shows includes shared system memory set aside for graphics use, and the game checks dedicated video memory only. The two numbers are not the same number, and comparing the total against the requirement is comparing the wrong figure. The dedicated figure is the one that matters, and it lives on the dedicated video memory line in Device Manager, dxdiag, or GPU-Z — nowhere else.
Misconception 3: A newer model always passes
No. A new card may not yet be on the game's internal support list, and the game may refuse it for that reason alone. An older card may support DirectX in the broad sense while not providing the specific feature level the game requires. The model name is not evidence. The support list and the dxdiag feature level list are the evidence, and both must be checked directly.
Misconception 4: Reinstalling the driver will definitely fix it
No. A driver reinstall helps only if the driver is the layer at fault. If the game is reading the integrated GPU, reinstalling the discrete card's driver changes nothing. If the hardware genuinely falls short — dedicated memory below the requirement, or a missing feature level — a reinstall cannot add memory or add a capability. If the checker is misreading the machine, a reinstall is only one branch of the check, and only the current manufacturer version, installed cleanly, counts as testing it. Reinstalling the driver is a step, not a cure.
Misconception 5: A Continue button means the warning can be ignored
No. Continue means only that the check is not a hard barrier in this game. It says nothing about what happens next. The game may run smoothly, which is evidence the check was wrong. It may also stutter, crash, or show corrupted graphics, which is evidence the hardware genuinely falls short. Pressing Continue and then actually playing — and noting the result — is the test. Pressing Continue and assuming the problem is over is not.
Misconception 6: Meeting the minimum requirements guarantees smooth play
No. The minimum requirement is the threshold at which the game is willing to open, not a promise that it will run smoothly. A machine that meets the minimum may still need lower settings, and may still struggle in demanding scenes. The reverse is also true: failing the minimum check does not always mean the game cannot run at all — some checks offer a Continue button precisely because the authors knew the check could be wrong, or the machine could still cope. The minimum is a doorway, not a guarantee in either direction.
Boundaries: Problems That Look Similar but Are Not This One
Not every launch failure is a minimum-requirements check, and the similar problems each belong to their own guide. If the symptom is one of the following, follow that guide, not this one.
A message saying the graphics API could not be initialised — "failed to initialise Direct3D", or a Vulkan or OpenGL initialisation failure — is an initialisation problem, not a hardware check. The game never reaches the check, because it cannot set up the graphics device at all. A message saying the driver is too old is a driver-version problem, and the version comparison is the whole diagnosis. A game that runs on DirectX 11 but crashes on DirectX 12 is a DirectX 12 problem, not a launch check. A game that starts, runs, and then reports an out-of-video-memory error during play is a memory allocation problem during play, not a check at launch. An error code in Device Manager is a device problem, with its own code-specific guide.
Three more boundaries deserve a sentence each. The first is the laptop whose manufacturer supplies its own driver, and whose generic manufacturer driver cannot be installed or is rejected: laptop drivers must be matched against the laptop manufacturer's own support page, and forcing a generic driver onto such a machine is not a step in this guide. The second is the older card whose manufacturer no longer publishes new drivers: the latest driver for that generation may itself be several years old, and a new game requiring more than that generation provides is a support-lifecycle problem, not an installation problem — reinstalling the driver cannot lower the requirement. The third is a game whose requirement is written so vaguely that no part and no number is given: do not guess which part it meant. Work through Steps 2 to 6 and let the evidence name the part.
Finally, there are things this guide will never teach, and a source that teaches them should be closed. Never edit the registry or a configuration file to trick a game into believing the hardware meets its requirements. Never download a single DLL file from the internet to satisfy a check. Never disable anti-cheat software to get a game to start. Never install a beta or experimental driver to pass a version check: only the version the manufacturer currently lists for the exact card model counts, and a beta version is not that. And never disable driver signature enforcement. None of these is a diagnosis, and each one trades a working machine for a less safe one.
When to Stop and Bring the Machine In
Stop when all seven steps have been worked through, one variable at a time, and the result is still uncertain — or when the hardware genuinely falls short and the question becomes which card to change to, rather than whether the check was right. Stop sooner if Device Manager shows an error code for the card, if the card disappears from Device Manager, or if any step involves editing the registry or downloading files from an unknown source.
Bring the machine in with the notes from every step: the copied message, which GPU the game was reading, the dedicated memory figure and its source, the dxdiag feature level list, and the four driver fields — provider, version, date, and card name. In-store inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
A diagnosis that ends at the stop line is not a failed diagnosis. A note that says "Game refuses at launch, message copied, game reads the discrete GPU, dedicated memory meets the requirement, feature level 12_0 present, driver is the current manufacturer version, Windows version is supported, game still refuses" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.
FAQ
Q1: My game says my graphics card does not meet the minimum requirements. Does that mean my card is too weak?
Not necessarily. The message is the result of the game's own hardware check, not a verdict on the card. The game may be reading the integrated GPU instead of the discrete card, counting shared memory instead of dedicated video memory, or running a checker that misreads the hardware. Copy the message word for word first, then work through the steps: confirm which GPU the game reads, read the dedicated memory figure, and check the feature level list. Only after those layers have been tested can the card itself be blamed.
Q2: How do I find out which graphics card the game is actually reading?
Open Task Manager while the game is running and look at which GPU carries the load, and check the graphics card selection inside the game's own settings. On a machine with both an integrated GPU and a discrete card, the game may be using the integrated GPU, in which case the check is measuring the wrong chip and the discrete card's specifications are irrelevant. If the game is running on the discrete card, that layer is cleared and the search moves to the numbers.
Q3: Windows shows I have plenty of video memory, but the game still refuses. Why?
Because the total Windows shows includes shared system memory set aside for graphics use, and the game checks dedicated video memory only. Read the dedicated video memory line in Device Manager, dxdiag, or GPU-Z, and compare only that figure against the minimum requirement on the game's store page. A monitoring program's allocated or used figure is also the wrong number: it reflects what has been set aside at that moment, not the dedicated capacity.
Q4: Can I use the allocated video memory figure in monitoring software to test the minimum requirement?
No. The allocated figure includes memory reserved in advance that may not actually be in use, so it is not the dedicated video memory capacity. Read the dedicated video memory line in Device Manager, dxdiag, or GPU-Z, and compare only that figure against the minimum requirement on the game's store page. Using the allocated figure means comparing the wrong number.
Q5: My card is a recent model. Shouldn't it pass any minimum-requirements check?
No. A new card may not yet be on the game's internal support list, and the game may refuse it for that reason alone. Separately, a card can support DirectX in the broad sense while not providing the specific feature level the game requires. Check the feature level list in dxdiag, on the Display page, and check the game's published support list. The model name is not evidence; the lists are.
Q6: What is a feature level, and how do I check whether my card has the one the game asks for?
A feature level is a capability list — entries such as 11_0, 12_0, and 12_1 — that says which features a graphics card supports. Open dxdiag, go to the Display page, and read the feature level list, then check whether the level the game requires appears in it. If the required level is not in the list, the capability layer is the answer; if it is, that layer is cleared. Never estimate the level from the model name: a new-looking model does not guarantee the required level.
Q7: My hardware meets the requirements, but the game still refuses. Is the checker reading it wrong?
Possibly. A checker can read wrong hardware information: a driver can report the wrong hardware version, or a Windows version can make the checker fail to read the hardware correctly. Judge it by three checks: whether the driver is the current manufacturer version, whether the Windows version is one the game's support page lists, and whether the same game starts on another machine that meets the requirements. Only when all three have been checked can the checker be named as the fault.
Q8: Will reinstalling the driver fix a minimum-requirements refusal?
Only if the driver is the layer at fault. If the game is reading the integrated GPU, reinstalling the discrete card's driver changes nothing. If the hardware genuinely falls short — dedicated memory below the requirement, or a missing feature level — a reinstall cannot add memory or add a capability. If the checker is misreading the machine, a clean install of the current manufacturer version is one branch of the check, and it must be the version the manufacturer currently lists for the exact card model.
Q9: The game offers a Continue button. Can I just press it and ignore the warning?
Continue means only that the check is not a hard barrier in this game. Press it, play properly, and note the result: if the game runs smoothly, that is evidence the check was wrong; if it stutters, crashes, or shows corrupted graphics, that is evidence the hardware genuinely falls short. Pressing Continue and assuming the problem is over is not a test. Record what happened, including the settings used, so the result can be acted on.
Q10: When should I stop trying things myself and bring the machine in for inspection?
Stop when all seven steps have been worked through and the result is still uncertain, or when the hardware genuinely falls short and the question becomes which card to change to. Stop sooner if Device Manager shows an error code for the card or the card disappears from Device Manager. Bring your notes: the copied message, which GPU the game was reading, the dedicated memory figure and its source, the dxdiag feature level list, and the four driver fields. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.