Hi Akshay--
I assume all these BSODs' you reported are IRQL_NOT_LESS_OR_EQUAL STOP:
0x0000000A, but I don't know that to be the case.
That stop error, like many of them, is rather general and can be caused by a
number of situations. It can be from a software or hdw incompatiblity
problem.
You'll love this--It's generated when a kernel mode process or driver
attempts to access a memory location at an interrupt request level (IRQL)
that is to high or tries to access a memory location for which it doesn't
have permission.
Here's the thing though that can be practical for you. ***You can use the
stop error (blue screen message) often to determine which driver is
offending if it is a driver problem. Remember, because people often forget
or don't realize, software has drivers as well as hdw, and sometimes several
drivers are installed for a software program. Put "driververifier" (lose
quotes) in your run box and you'll get that idea.
Are your stop errors all the same and do they implicate Jetico? If they do,
uninstalling it completely should help so use the Win Installer Cleanup
Utility.
Download at bottom--simple box--you highlight anything (look carefully) that
has the name of the driver specified in the IRCQ error in it (if there is).
and delete that entry. Again it does not uninstall the program, but corrupt
keys, strings, and .dlls associated with
it. Remember software programs have drivers--often several of them and it's
often the inspection of them by driver verifier that creates a BSOD.
http://support.microsoft.com/kb/290301
If you have a Vista DVD you can try Startup Repair, a Repair Install or
Running System Restore from it:
I'd try every possible restore point from every possible
source--instructions are below--you can
access system restore by
1) typing restore into the search box
2) F8ing to the various safe modes (I commend you for thinking of trying the
long shot Last Known Good)--by the way do you realize that LKG is similar to
a restore point in that it invokes a registry snapshot but the difference is
changes since the LKG configuration won't be preserved. Using SR in XP, (a
registry snapshot) and Vista (VSS) will preserve changes since the restore
point with the exception of shortcuts, new folders you created and shortcuts
in them and program installs--and often it does despite the MSFT party line
on this.
3) You can run SR from either the command prompt reached by the Recovery
Link on the Vista DVD, or from the Recovery Link (there's a system restore
option as part of Win RE on the DVD.
If you can't boot, you can try sfc from the cmd prompt reached at the
Recovery Link of the DVD:
Instructions for your various options are below:
***SFC as a Remedy***:
SFC or System File Checker is a bit like the spare tire in your car or a
backup battery I suppose. In Vista of course, they have changed it somewhat
and come up with a new name--Redmond stands for name it something different
twice a year and now it's part of WRP or Windows Resource Protection. It
scans protected resources including thousands of files, libraries, critical
folders, and essential registry keys, and it replaces those that are
corrupted with intact ones. It fixes a lot of problems in Windows XP, OE,
Windows Vista, Win Mail, IE6, and on Vista or if it is installed on XP, IE7.
It protects these things from changes by any source including
administrators, by keeping a spare of most of them.
-----------------
How to Run SFC:
Type "cmd" into the Search box above the Start Button>and when cmd comes up
at the top of the Start menu>right click cmd and click "run as Admin" and
when the cmd prompt comes up at the cmd prompt type "sfc /scannow" no quotes
and let it run. This may fix things quite a bit. It replaces corrupt files
with intact ones, if you're not familiar with it.
Other Recovery Options I suggested in Vista:
It will automatically take you to this on your screen:
http://www.vistaclues.com/wp-content/uploads/2006/12/click-repair-your-computer.png
The gray screen after you click the first link in the above pic will look
like this:
http://www.windowsreinstall.com/winvista/images/repair/staruprepair/Image17.gif
You could also try a Repair Install with Vista which is done exactly the
same way as in XP:
***Repair Install Steps*** (can be used for Vista) MVP Doug Knox
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx
***Using the F8 Environment***
***Taking Full Advantage of the F8 Options (Windows Advanced Options Menu)
by starting the PC and tapping F8 once per second when the firmware screen
with the pc manufacturer's name shows a few seconds after restarting***:
The F8 options in Vista are the same as XP, and the link for Safe Mode Boot
options is labled XP by MSFT but they are the same for Vista (they haven't
updated to add Vista to the title as they have with several MSKBs that apply
to both).
Again, pressing F8 repeatedly when you seem the firmware screen may be is a
generic way to launch Windows RE on some OEM Vista computers.
You could also:
Think: I have 4 different ways to get back my XP at F8 and try 'em in order.
1) Safe Mode 2) Safe Mode with Cmd to Sys Restore which is simply a cmd
prompt in safe mode 3) Safe Mode with Neworking 4) LKG or Last Known Good
Configuration
Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.
These methods are outlined in
A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/
Frequently Asked Questions Regarding System Restore from MSFT:
http://www.microsoft.com/technet/prodtechnol/winxppro/plan/faqsrwxp.mspx
System Restore can be run from the Win RE recovery environment from the same
link as Startup Repair, and sometimes it will work from one F8 safe mode
location or from the Win Recovery Environment when it won't work from other
locations.
How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;304449
Good luck,
CH
