Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Blue screen may be clue to my problems-LOOK!

Featured Replies

Chip type: GeForce 8600 GTSI have attached a screenshot of what maybe a hint of what is affecting my system. I don't remember these hangs (maybe they did happen before it) before I got this external HD WD 500GB, but my P5VD2-MX and PCI-E card may be in conflict.I have now disconnected my ext HD since flashing my BIOS for the ASUS update of the PCI-E mobo fix didn't work. Failing this, I will try to clean out my drivers (video) and then install the Beta Nvidia drivers (174 I think). Failing that I will try a system reinstall.What made me upgrade to this new card about 5 months ago was my ATI card had accumulated too much dust and had a poor standard fan on it. I think it cooked.... This new card has a mega awesome fan with temp software. I also look inside my sys case from time to time.Any help with resolving this issue will be appreciated as you probably know......------------------System Information------------------Time of this report: 4/24/2008, 20:32:31 Machine name: DHOME Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254) Language: English (Regional Setting: English)System Manufacturer: System manufacturer System Model: System Product Name BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel® Core2 CPU 6300 @ 1.86GHz (2 CPUs) Memory: 2046MB RAM Page File: 421MB used, 3518MB available Windows Dir: C:WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904)DX Setup Parameters: Not found DxDiag Version: 5.03.2600.2180 32bit Unicode------------DxDiag Notes------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found.--------------------DirectX Debug Levels--------------------Direct3D: 0/4 (n/a)DirectDraw: 0/4 (retail)DirectInput: 0/5 (n/a)DirectMusic: 0/5 (n/a)DirectPlay: 0/9 (retail)DirectSound: 0/5 (retail)DirectShow: 0/6 (retail)---------------Display Devices--------------- Card name: NVIDIA GeForce 8600 GTS Manufacturer: NVIDIA Chip type: GeForce 8600 GTS DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_0400&SUBSYS_82411043&REV_A1 Display Memory: 256.0 MB Current Mode: 1280 x 1024 (32 bit) (60Hz) Monitor: Plug and Play Monitor Monitor Max Res: 1600,1200 Driver Name: nv4_disp.dll Driver Version: 6.14.0011.6921 (English) DDI Version: 9 (or higher)Driver Attributes: Final Retail Driver Date/Size: 12/5/2007 01:41:00, 5773568 bytes WHQL Logo'd: Yes WHQL Date Stamp: n/a VDD: n/a Mini VDD: nv4_mini.sys Mini VDD Date: 12/5/2007 01:41:00, 7435392 bytesDevice Identifier: {D7B71E3E-4740-11CF-FA68-4AA200C2CB35} Vendor ID: 0x10DE Device ID: 0x0400 SubSys ID: 0x82411043 Revision ID: 0x00A1 Revision ID: 0x00A1 Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch Registry: OK DDraw Status: Enabled D3D Status: Enabled AGP Status: EnabledDDraw Test Result: Not run D3D7 Test Result: Not run D3D8 Test Result: Not run D3D9 Test Result: Not run-------------Sound Devices------------- Description: SoundMAX HD Audio O Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIOFUNC_01&VEN_11D4&DEV_1986&SUBSYS_1043818F&REV_1005 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: ADIHdAud.sys Driver Version: 5.10.0001.4151 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 10/6/2005 01:21:10, 141312 bytes Other Files: Driver Provider: AnalogDevices HW Accel Level: Full Cap Flags: 0xF5F Min/Max Sample Rate: 100, 192000Static/Strm HW Mix Bufs: 33, 32 Static/Strm HW 3D Bufs: 33, 32 HW Memory: 0 Voice Management: Yes EAX 2.0 Listen/Src: Yes, Yes I3DL2 Listen/Src: Yes, YesSensaura ZoomFX: Yes Registry: OK Sound Test Result: Not run---------------------Sound Capture Devices--------------------- Description: SoundMAX HD Audio I Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: ADIHdAud.sys Driver Version: 5.10.0001.4151 (English) Driver Attributes: Final Retail Date and Size: 10/6/2005 01:21:10, 141312 bytes Cap Flags: 0x41 Format Flags: 0xCCC-----------DirectMusic----------- DLS Path: C:WINDOWSSYSTEM32driversGM.DLS DLS Version: 1.00.0016.0002 Acceleration: n/a Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal Registry: OK Test Result: Not run-------------------DirectInput Devices------------------- Device Name: Mouse Attached: 1 Controller ID: n/aVendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/aVendor/Product ID: n/a FF Driver: n/a Device Name: Top Gun Afterburner Attached: 1 Controller ID: 0x0Vendor/Product ID: 0x044F, 0xB101 FF Driver: n/a Device Name: Microsoft Wireless Optical Mouse

STOP 0x0000000A IRQL_NOT_LESS_OR_EQUALis either a bad memory stick, a overclock that is too high and unstable or a driver conflictFollow that route to find the culprit. Test the memory using MEMTEST 86 in DOS and if it finds no errors after a few hours then start uninstalling hardware/drivers one by one till the error ceases

OK, that sounds like a common sense plan to me.Excellent.By looking at that, it could be a driver issue....somewhere. But what you have said really clears up my issues.I am not overclocking that I know of!

Found it. Via driver Via standard to PCIE bridge.This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)Click Troubleshoot to start the troubleshooter for this device.

>>>>STOP 0x0000000A IRQL_NOT_LESS_OR_EQUAL>>is either a bad memory stick, a overclock that is too high and>unstable or a driver conflict>>Follow that route to find the culprit. Test the memory using>MEMTEST 86 in DOS and if it finds no errors after a few hours>then start uninstalling hardware/drivers one by one till the>error ceasesThanks very much. I should have had a quick look in my device manager before asking. Hope it is of help to someone else then.All fixed.

I fixed it for a few hours.....What I deleted was the PCI-to PCI-E bridge.Now I will work on this.

Would a USB WD 500 GB external Hard Disk be causing this?http://wer.microsoft.com/responses/Respons...cb-a0743288a30cI changed from default in my MOBO setup from the ex-Sata to PCI-E controller. Anyone know if this does anything, and what does it do?I also pulled out my external hard drive.

Would the MOBO's VIA chipset be a possible cause to my blue screens? Or should I just reinstall XP?

Have you tested the memory to see if there is a defective stick in the system?

No, I will do it now.Running VOZ and Just Flight PSS 757 is giving me serious system locks which need to be reset. This is after reinstalling and playing other 3d games where I didn't have the problem (only once?).With my version of Nero it doesn't 'do' bin files.Can you help me to get the memtest going?Hang on, looks like I could get an ISO file there.Starting now.

Yes, I tested it for 19 hours and 6 passes, no faults.

>Yes, I tested it for 19 hours and 6 passes, no faults.Good then that has been ruled outThis is either a driver crash (could be any one of them) or something forcing a crash in the sim, one of the two.My next suggestion would be to use 3DMark.. and set it up to run loops of the test over and over. If you see a crash then we have eliminated the sim, if not then the possibility of something in the sim is causing the crash still exists.I assume you have updated DirectX by going to MS and downloading the latest version installer, and, Windows from Windows Update? I would make sure those areas are covered although this type of crash would typically not be from the lack of such updates.I would make sure all the temps are remaining in range.. VC, CPU, tower, etc... a way to test that and be sure the readouts are not incorrect is remove the side of the tower placing a small fan next to it (blowing into the tower) and running what you normally do and see a crash. If no crash appears it is very likely a temp issue of some type.

I keep an eye on temps since my poorly built ATI card failed due to dust/temp issues. I blew out ymy computer with compressor air about 14 days ago and the most dust had built up on my CPU fan. The video fan was looking OK and it was far more robust than the Sapphire card fan which I had before.I will run 3Dmark and also have the Hard Drive test ISO (burnt to CD already) running (from Samsung), I ran a quick test but will need to do extensive testing anyway later. I think it is a driver issue, not sure if it is conflicting with the VIA drivers being a MOBO that isn't quite the spec for PCI-E.Thanks for your help.Is there a 'perfect' hardware compatability, such as MOB+Video? Also can you buy a MOBO with a good video card for a good price?

Greetings!I took delivery on a new system from Aerodrifting Systems yesterday and got multiple identicle blue screens as I first started to load FSX and other stuff. An email to the builder resulted in this response.------------------------Hello, Dear BruceIn fact I was just about to email you:The blue screen and "NVGTS.SYS error" is caused by the motherboard SATA driver when an optical SATA drive (DVD Burner) is connected to the motherboard. It's a common issue with the 780i boards.A fix just came out, please click this link to download the latest Beta driver from EVGA website: http://us.download.nvidia.com/Windows/nFor...nglish_whql.exeOnce the download is finished, install the new driver. It will promote you to remove the old driver and restart.Everything will be fixed by this new Beta driver.Thank you for contacting us and sorry for the inconvenience it has caused you.Sincerely, HowardAerodriftingsystemsI just installed this driver and have no experience with it yet. You don't seem to have the same mobo, but thought you might like to see this response.Bruce

Thanks for the post.I am building a new test bed system o I can check if it is because the mobo has been damaged by a previously cooked video card.I'll update as I go.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.