0x0E* · PAGE FAULT
About
I have worked in IT for over 25 years, across software development, training, database management and IT infrastructure design for internal and client environments.
Why this site
The name comes from a simple concept: a page fault is not an error — it is the mechanism by which a system recognises something is missing and goes to fetch it. I think it is a good metaphor for how learning works, and how I approach something new.
Technology is a passion for me, not just a job. I write here when I feel like sharing something that interests me: real-world experiences, tools I actually use, new technologies I find worth exploring.
Over the years I have received a lot from the web — solutions found thanks to experiences shared by others. Sometimes I feel like giving some of that back.
— Volt
What you'll find here
- IT & Sysadmin — technical guides, sysadmin, databases
- AI & Dev — development, automation, artificial intelligence
- Gaming — games, retro gaming, apps
- Projects — things I've built and actually use
- Archive — older articles that remain available
About the content
- All written by me, with the help of the AI tools that are now part of everyday work
- Shared freely, because knowledge is more useful when it circulates
- Updated when things change. Or when I get something wrong
“This is for Everyone” — Tim Berners-Lee
* Trivia
0x0E = 14
0x0E (14 in decimal) is the number x86 processors use to identify a page fault. The first 32 entries of the interrupt table (IDT) are reserved for CPU exceptions: 0x00 is divide-by-zero, 0x0D the general protection fault, and 0x0E the page fault.
WHAT HAPPENS
When a program touches a memory page the MMU can’t translate, because it isn’t in RAM or because of a permission problem, the CPU stores the address in the CR2 register and hands control to the operating system. If the page just needs loading, the system loads it and the instruction runs again: the program never notices. Only a truly illegal access ends in the famous segmentation fault.
WHY IT’S HERE
Because it’s the same idea behind the site’s name: a page fault isn’t an error, it’s how a system realises something is missing and goes to fetch it. A bit like learning.