Blue screen error in GW2

Associate
Joined
10 Jan 2011
Posts
189
Location
Scotland
As above, don't know if its related to the game or not :S
Just been playing GW2 fine and them, blue screen, buzzing from speakers, crashed. never happened in any games before, its actually never happened to me at all before.
I've linked to a pic I took of the error on screen. Is this just a typical "blue screen error" or something more specific to what I was doing?
heres the link
x56t5i.jpg


Cheers all
 
Copied from Mircosoft Answers Page:

Welcome to Microsoft Answers.

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.
Use check disk command for any errors on hard disk -
Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.
Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.
NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.
You may refer to the below mentioned link for more details -
http://msdn.microsoft.com/en-us/library/ms793989.aspx
Hope this helps.
 
whats your operating system?

for a wild guess it's vista Home Premium 64-bit?

yes?

also guessing again,

CHKDSK /P and sfc /f will return a hard drive error or corrupt file error and replace, or ask for dik etc, maybe a bad sector or corrupt file after power lost or bad save etc etc, and will mark it bad if it finds it faulty, but saying that, windows has already used or can't find the file etc it, that's why you get the error.

only option is if bad sectors, either back up and reinstall o/s then add back up doc's etc, short term fix, as i wouldn't use that drive again either, but many do for months and year with no more errors, once reinstalled, windows won't use the bad sector as it will mark it bad before it installs.

if corrupt files, sfc should repair, if not you may not be able to yourself if it's a system file, but sfc/f should do it, fingers crossed it's this tbh....

for me i'd just replace it with another hard drive, after data has been taken off if it's that, or reinstall if sfc/ system file checker doesn't repair

i maybe wrong, won't be the first or last time tbh

but guessing i'm right :)
 
Last edited:
whats your operating system?

for a wild guess it's vista Home Premium 64-bit?

yes?

also guessing again,

CHKDSK /P will return a hard drive error, maybe a bad sector etc, and will mark it bad, but saying that, windows has already used it, that's why you get the error.

only option is, either back up and reinstall o/s then add back up doc's etc, short term fix, as i wouldn't use that drive again either, but many do for months and year with no more errors, once reinstalled, windows won't use the bad sector as it will mark it bad before it installs.

for me i'd just replace it with another hard drive, after data has been taken off

i maybe wrong, won't be the first or last time tbh

but guessing i'm right :)

My OS is Windows 7 64 Bit, the hard drive is only 1 month old aswell?
 
then run both above, date doesn't matter, one power loss with no ups or protection can kill or damage any drive, but if it's not that, sfc /f or sfc scannow will fix or should fix faulty system files

you will need to run it twice as well and re boot between uses, making sure you have the o/s disk handy if needed

Open Command Prompt as an administrator, often referred to as an "elevated" Command Prompt.

Important: For the sfc /scannow command to work properly, it must be executed from an elevated Command Prompt window in Windows 8, Windows 7 and Windows Vista. This is not required in previous versions of Windows.

Once Command Prompt is open, type the following command and then press Enter.

sfc /scannow
Note: There's a space between sfc and /scannow.
 
Last edited:
"did not find any integrity violations"
what exactly does this mean, I've now tried CHKDSK and /scannow and both are telling me nothings wrong yes?
something must be wrong otherwise it wouldn't crash
 
Back
Top Bottom