BSOD caused by SYSTEM_SERVICE_EXCEPTION ntroskrnl.exe

XP ROCKS!

No I haven't. I'm a little apprehensive to do this as I know if you make a mistake, you run the risk of destroying your machine.

I have found the following guide which describes in a dummy way how to update using a USB stick. It quotes it is for Windows Millenium but was linked from a Windows 7 guide.  Will the files it provides and the guide work for Windows 7?

http://www.techpowerup.com/forums/threads/howto-easily-flash-mb-vga-bios-using-usbstick.47812/

Appreciate your comments as without confidence that I can do it correctly, I won't be attempting to upgrade my BIOS.

Regards

Dave

Please, do not resort to taking advice about updating your BIOS, from parties other than your Motherboard/system maker. 

I have linked you to two methods to update, both provided by ASUS

0: kd> !sysinfo machineid

 Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=2294]

 BiosMajorRelease = 8

 BiosMinorRelease = 15

 BiosVendor = American Megatrends Inc.

BiosVersion = 0316

BiosReleaseDate = 12/22/2009

 SystemManufacturer = System manufacturer

 SystemProductName = System Product Name

 SystemFamily = To Be Filled By O.E.M.

 SystemVersion = System Version

 SystemSKU = To Be Filled By O.E.M.

 BaseBoardManufacturer = ASUSTeK Computer INC.

 BaseBoardProduct = M4A77TD

 BaseBoardVersion = Rev X.0x

Update your BIOS to the latest version Available.

 ASUSTeK M4A77TD BIOS Version  2104.

http://dlcdnet.asus.com/pub/ASUS/mb/socketAM3/M4A77TD/M4A77TD-ASUS-2104.zip?_ga=1.174271909.644953069.1430598853

Here is how.

http://www.asus.com/support/FAQ/1008280/ 

or

http://www.asus.com/support/FAQ/1008282/

BIOS Disclaimer

Updating BIOS should only be done if necessary (to solve a compatibility problem, for example). It can be a complicated process, and if an error occurs, your computer could be rendered inoperable. Be sure to follow the manufacturer's instructions exactly.

Dave

Should I reinstate it to avoid that error?

Yes I would enable it.

What does it actually do?

http://en.wikipedia.org/wiki/Card\_reader

The FSX error is persistent. In Google I found a number of variants and none seem easy to resolve.

Gerry

I think I disabled the SmartCard reader when I was experimenting previously. I wasn't sure why I had it so disabled it. Should I reinstate it to avoid that error? Was does it actually do?

The FSX error is an interesting one as the timestamp ties up with me closing FSX.  I have been getting a 'FSX has experienced an error' when closing the sim of late. I'll uninstall a program I installed recently to see I remove the error.  I do not believe it is an issue with the software from the link you provide but as I said, I'll do some trial and error.

Thanks as always

Dave

XP ROCKS!

No I haven't. I'm a little apprehensive to do this as I know if you make a mistake, you run the risk of destroying your machine.

I have found the following guide which describes in a dummy way how to update using a USB stick. It quotes it is for Windows Millenium but was linked from a Windows 7 guide.  Will the files it provides and the guide work for Windows 7?

http://www.techpowerup.com/forums/threads/howto-easily-flash-mb-vga-bios-using-usbstick.47812/

Appreciate your comments as without confidence that I can do it correctly, I won't be attempting to upgrade my BIOS.

Regards

Dave

David

[Problem Devices]

Device PNP Device ID Error Code       

archlp  ROOT\LEGACY_ARCHLP\0000              This device is not present, is not working properly, or does not have all its drivers installed.

Microsoft Usbccid Smartcard Reader (WUDF)              USB\VID_413C&PID_2101&MI_01\6&31180A4F&0&0001    This device is disabled.      

Did you disable this device?

This is a persistent error in your Event Viewer Application log.

Log Name:      Application

Source:        Application Error

Date:          04/05/2015 23:19:13

Event ID:      1000

Level:         Error

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x04246c81

Faulting process id: 0xf20

Faulting application start time: 0x01d0868bd1238b29

Faulting application path: C:\FSX\fsx.exe

Faulting module path: unknown

From the quote below extracted from Google it would seem that there are various modules which work with Flight Simulator Are you able to identify the module and eliminate the error?

To verify this, you can try to disable both our modules, one by one, by setting the <Disabled>True</Disabled) for bglmanx.dll (in the %APPDATA%\Microsoft\FSX\DLL.XML file) and for Couatl.exe in the (in the %APPDATA%\Microsoft\FSX\DLL.XML file).

This will allow you to test FSX as it is now, without the modules loaded, without having to uninstall anything. If you are still getting crashes, you would know for sure it doesn't have anything to do with any of our products.

Source: http://www.fsdreamteam.com/forum/index.php?topic=11609.0