WEBVTT

00:00:00.000 --> 00:00:05.190
thanks for watching Techquickie click the subscribe button and enable

00:00:03.210 --> 00:00:10.110
notifications with the bell icon so you won't miss any future videos of all the

00:00:07.799 --> 00:00:16.570
unpleasant surprises you can encounter while computing few are more jarring

00:00:13.550 --> 00:00:19.570
and the sudden blue screen of death and

00:00:16.570 --> 00:00:21.980
let's not kid ourselves that cute little

00:00:19.570 --> 00:00:26.390
frowny face they added in Windows 8 really doesn't help what's almost as

00:00:24.830 --> 00:00:31.640
frustrating is losing your work though is the fact that you get hardly any

00:00:28.670 --> 00:00:36.800
information about why your computer suddenly decided to stop working like

00:00:34.489 --> 00:00:41.540
Dennis on a Friday afternoon all you get is some mysterious error code thankfully

00:00:39.470 --> 00:00:46.039
Techquickie is here to save the day with a list of some of the most common

00:00:43.880 --> 00:00:52.910
blue screen error codes along with their meanings and some possible fixes

00:00:48.519 --> 00:00:56.210
starting with irq not less or equal as

00:00:52.910 --> 00:00:59.120
it turns out I RQ l stands for interrupt

00:00:56.210 --> 00:01:03.649
request level which usually means that a program tried to access a piece of

00:01:01.550 --> 00:01:09.050
memory that was being protected by the operating system for some sort of

00:01:05.630 --> 00:01:12.170
important task and since device drivers

00:01:09.050 --> 00:01:14.060
usually have to access these parts of

00:01:12.170 --> 00:01:19.640
memory since they interface with your operating system and the actual hardware

00:01:16.670 --> 00:01:25.880
this error typically indicates a driver issue so try updating or reinstalling

00:01:23.330 --> 00:01:31.670
any drivers that might be problematic of course this could also indicate a

00:01:28.760 --> 00:01:37.220
problem with the hardware itself perhaps a graphics card that's aggressively

00:01:33.800 --> 00:01:40.160
overclocked and by the way the related

00:01:37.220 --> 00:01:44.420
page Fault in non paged area can indicate a similar problem but those

00:01:42.590 --> 00:01:49.640
aren't the only messages that indicate a hardware error if you see data bus error

00:01:47.420 --> 00:01:53.750
it doesn't mean you have a broken Volkswagen parked in your driveway

00:01:50.990 --> 00:01:59.180
instead this probably means you have an issue with your memory so run a memory

00:01:56.240 --> 00:02:03.980
check utility like mem test 86 plus or try simply pulling out one of your RAM

00:02:01.850 --> 00:02:08.300
sticks and then swapping for the other one to see if one of them has died I

00:02:06.560 --> 00:02:12.410
mean or you can swap out both if you have extras on hand it's entirely

00:02:10.340 --> 00:02:17.840
possible that we are single-handedly causing the continuation of the global

00:02:14.720 --> 00:02:20.000
DRAM shortage so sorry about that this

00:02:17.840 --> 00:02:24.470
may well solve the problem and if it doesn't well it's likely that you have a

00:02:21.980 --> 00:02:30.500
driver or Hardware issue elsewhere in your system another memory be saw memory

00:02:28.040 --> 00:02:35.270
management can often be resolved by going into your BIOS and making sure

00:02:32.690 --> 00:02:39.800
that your RAM settings are correct this particular error can pop up if you've

00:02:37.220 --> 00:02:44.300
overclocked your RAM or if it's not getting the right amount of voltage on

00:02:41.840 --> 00:02:49.400
the subject of overclocking machine check exception is often caused by a CPU

00:02:47.420 --> 00:02:54.380
that is overclocked to the point of instability so try bumping it back to

00:02:52.340 --> 00:02:58.610
stock speed to see if the error goes away and then if you do choose to

00:02:56.450 --> 00:03:03.050
overclock again be a little bit more conservative please but then suppose

00:03:00.920 --> 00:03:08.330
your memory and your processor are fine and you get an error that says fat file

00:03:05.720 --> 00:03:14.570
system don't get out the exercise bike just yet any file system error whether

00:03:11.150 --> 00:03:16.790
it's fat or NTFS simply means that

00:03:14.570 --> 00:03:22.070
you've got some kind of a problem with your hard drive or SSD

00:03:18.430 --> 00:03:25.460
now this could simply be caused by a

00:03:22.070 --> 00:03:28.100
driver issue but there also might be a

00:03:25.460 --> 00:03:33.890
more serious physical issue with your disk so if you see this error backup

00:03:31.000 --> 00:03:39.440
anything important and run a disk check utility followed by a diagnostic utility

00:03:36.650 --> 00:03:44.990
like CTools from the manufacturer of your drive to ensure that it is safe to

00:03:41.930 --> 00:03:47.270
continue to use other kinds of discs

00:03:44.990 --> 00:03:52.280
problems can produce the inaccessible boot device blue screen that could be

00:03:50.090 --> 00:03:57.380
caused by a corrupt sector which can sometimes be fixed by running Windows

00:03:54.110 --> 00:04:00.590
startup repair or simply by choosing the

00:03:57.380 --> 00:04:04.160
wrong disc mode in your BIOS if it's set

00:04:00.590 --> 00:04:06.410
to IDE try changing it to AHCI and vice

00:04:04.160 --> 00:04:11.600
versa of course there are other errors that don't have super obvious causes

00:04:08.780 --> 00:04:15.709
such as system thread exception not handled if you see this common message

00:04:13.970 --> 00:04:20.450
or another error code that you don't recognize see if your blue screen of

00:04:18.320 --> 00:04:25.910
death gives you a file name that you can jot down before the PC reboots this can

00:04:23.600 --> 00:04:32.650
give you a clue as to what driver or program is misbehaving so that you can

00:04:28.430 --> 00:04:35.600
update reinstall or remove it completely

00:04:32.650 --> 00:04:39.710
so we're out of time for now but let us know in the comments if there's another

00:04:37.160 --> 00:04:45.569
b-side you'd like us to cover that keeps coming back for you like a bad case of

00:04:41.800 --> 00:04:47.919
the shingles my roof has shingles

00:04:45.569 --> 00:04:53.169
you know what isn't like a rash that goes away though private Internet access

00:04:50.259 --> 00:04:57.970
not only does P IA v pn work on up to five devices at once --is by hiding your

00:04:56.110 --> 00:05:01.630
true IP address and allowing you to bypass geo restrictions and censorship

00:04:59.919 --> 00:05:05.889
by making it appear as though you are connecting from somewhere else it also

00:05:03.310 --> 00:05:10.270
blocks unwanted connections to help prevent attacks it Otto blocks all

00:05:07.990 --> 00:05:15.639
traffic if the VPN disconnects and it keeps your data out of the hands of

00:05:11.889 --> 00:05:17.349
snoops and advertisers P ia supports

00:05:15.639 --> 00:05:21.099
multiple VPN protocols and encryption levels allowing you to dial in the exact

00:05:19.360 --> 00:05:24.970
level of protection you need and they've got apps for Windows Mac Android iOS

00:05:22.690 --> 00:05:30.789
Linux and a Chrome extension with support for more platforms coming soon

00:05:26.889 --> 00:05:32.770
so check out bia they've got over 3,000

00:05:30.789 --> 00:05:37.150
servers in 28 countries and they don't log your activity we're gonna have them

00:05:34.509 --> 00:05:39.310
linked in the video description so thanks for watching guys like dislike

00:05:38.319 --> 00:05:48.130
check out our other channels leave a comment if you have a suggestion for a future video and subscribe it's a dream

00:05:44.470 --> 00:05:50.490
to be subscribed to tech wiki I dream of

00:05:48.130 --> 00:05:50.490
it every day