Reputation
312
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 3 14
Impact
~45k people reached

  • 0 posts edited
  • 0 helpful flags
  • 8 votes cast
Feb
28
answered How to setup Windows 7 firewall to work like a normal personal firewall?
Feb
28
revised Firefox always the one causing BSOD 0x124 on Windows 7 64-bit
added 875 characters in body
Feb
17
awarded  Popular Question
Feb
13
answered Why does Firefox crash then pops with a BSOD error?
Feb
13
revised Firefox always the one causing BSOD 0x124 on Windows 7 64-bit
added 890 characters in body
Feb
13
comment Firefox always the one causing BSOD 0x124 on Windows 7 64-bit
Thanks +1 for a great answer. Once upon a time, there were Windows 3.1/95/98/98se/Me which were all characterized by applications having access to the kernel's address space. With the intro of W2K (based on NT4), this problem seems to have been solved, as I never experienced this kind of application crashing the OS in Windows 2000 and XP. What happened to in Windows 7? or to Firefox? Does Firefox interact with the OS in the Kernel level?
Feb
13
comment Firefox always the one causing BSOD 0x124 on Windows 7 64-bit
@techie007 Kernel level yes. Video driver impossible, as it always bugcheck 0x124 which leads to ntoskrnl.exe.
Feb
12
asked Firefox always the one causing BSOD 0x124 on Windows 7 64-bit
Jan
11
comment How to find the source of this BSOD? How to fix it?
Yes it's a good thing but I already get all that information from BlueScreenView. The only advantage of !analyze -v is the ability to show the source code if I have it and since I am not the developer of ntoskrnl.exe, it doesn't help me. Aside from the fact that it's horribly bloated and further compromises the stability of the system. Installing it is only justified when you develop drivers.
Jan
9
comment How to find the source of this BSOD? How to fix it?
BlueScreenView is exactly where I took the information I posted in my question. The back-track stops at what I posted originally: ntoskrnl.exe+18d513. The comment posted by @AndrejaKo is the best answer so far.
Jan
9
comment How to find the source of this BSOD? How to fix it?
This is good for driver developers, not for an admin.
Jan
8
revised How to find the source of this BSOD? How to fix it?
added 6 characters in body
Jan
8
awarded  Commentator
Jan
8
comment How to find the source of this BSOD? How to fix it?
@AndrejaKo This is a great resource. Looks like exactly what I have been looking for. Please re-post as an answer and I will accept it. Thanks +1 for now.
Jan
8
asked How to find the source of this BSOD? How to fix it?
Dec
22
awarded  Supporter
Dec
22
accepted Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Dec
22
comment Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Thanks, the CHKDSK x: /f /r from Windows 2000 worked. (repeating recovery console was futile, I am lucky that I had Windows 2000 on that computer in dual boot config). It turns out that the SYSTEM registry file was corrupt. All I had to do is find some way to fix it.
Dec
22
asked Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Nov
4
awarded  Teacher