Get the above BSOD when playing a game, installed the latest audio and video drivers i could find but get that error everytime i try and do the same thing in the game ...full error code is ...0x0000000A (0x00000000 0x0000001C 0x00000001 0x80502300Hopefully someone out there knows whats causing this problem, doesnt happen on any of my other games just Fallout new vegas, and i know lots of people are having problems with that

In Administrative Tools choose Reliability and Performance Monitor andchoose MonitoringTools then Reliability Monitor (type Reliability in searchon Start) . This list is a chart of software installs, uninstalls, Windowsupdates, and crashes by date. See if your crashes started happening afteryou installed or uninstalled something. In Control Panel choose Problem Reports and Solutions (type problem inStart's searchbox), go to Problem History, right click your error and chooseCheck For Solution. The two causes of blue screens are faulty drivers or a hardware fault. Try these steps to rule out the hardware faults that Windows can detect. Type memory in Start's search box and choose Memory Diagnostic then Reboot.This will take a few minutes. In Computer right click your drives and choose Properties, then Tools tab,then click Check Now. Tick BOTH checkboxes then Ok. Reboot. This will takeovernight. After running chkdsk (which is what the above does) check for filecorruption by clicking Start - All Programs - Accessories - Right clickCommand Prompt and choose Run As Administrator. Type sfc /scannow -- ..--"fingers75" wrote in message news:17e827d6-b290-43fa-9ae8-ee2e82663219...> Get the above BSOD when playing a game, installed the latest audio and > video drivers i could find but get that error everytime i try and do the > same thing in the game ...full error code is ...>> 0x0000000A (0x00000000 0x0000001C 0x00000001 0x80502300>> Hopefully someone out there knows whats causing this problem, doesnt > happen on any of my other games just Fallout new vegas, and i know lots of> people are having problems with that>

I should of put on the first message I have Windows XP Home Edition, i dont have...In Administrative Tools choose Reliability and Performance Monitor andchoose MonitoringTools then Reliability Monitor (type Reliability in searchon Start) . This list is a chart of software installs, uninstalls, Windowsupdates, and crashes by date. See if your crashes started happening afteryou installed or uninstalled something. In Control Panel choose Problem Reports and Solutions (type problem inStart's searchbox), go to Problem History, right click your error and chooseCheck For Solution.Options for those il try the other things you have advised though, As this is annoying me now lol

Mini112310-02.dmp 23/11/2010 01:53:11 BAD_POOL_HEADER 0x00000019 0x00000020 0x891dd910 0x891de1f8 0x0b1dc99c ntoskrnl.exe ntoskrnl.exe+22f43 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636) 32-bit E:\WINDOWS\Minidump\Mini112310-02.dmp 2 15 2600 Mini112310-01.dmp 23/11/2010 00:57:48 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x8054b71c 0x9f19fb30 0x00000000 fltmgr.sys fltmgr.sys+70fd Microsoft Filesystem Filter Manager Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5512 (xpsp.080413-2111) 32-bit E:\WINDOWS\Minidump\Mini112310-01.dmp 2 15 2600 Mini112210-04.dmp 22/11/2010 23:54:25 IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x00000000 0x0000001c 0x00000001 0x80502300 ntoskrnl.exe ntoskrnl.exe+2b300 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636) 32-bit E:\WINDOWS\Minidump\Mini112210-04.dmp 2 15 2600 Mini112210-03.dmp 22/11/2010 23:47:40 IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x00000001 0x0000001c 0x00000001 0x80502300 ntoskrnl.exe ntoskrnl.exe+2b300 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636) 32-bit E:\WINDOWS\Minidump\Mini112210-03.dmp 2 15 2600 Mini112210-02.dmp 22/11/2010 23:09:08 IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x00000004 0x0000001c 0x00000001 0x80502302 32-bit E:\WINDOWS\Minidump\Mini112210-02.dmp 2 15 2600 Mini112210-01.dmp 22/11/2010 22:32:41 DRIVER_CORRUPTED_EXPOOL 0x100000c5 0x00000005 0x00000002 0x00000001 0x8054bfd2 ntoskrnl.exe ntoskrnl.exe+74fd2 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636) 32-bit E:\WINDOWS\Minidump\Mini112210-01.dmp 2 15 2600 Mini092110-01.dmp 21/09/2010Hope someone can point me on the right path, installed fallout vegas and been having bsod ever since. Not sure whats the problem, done harddrive tests and memory tests and they say there fine. not sure whats causing the problem or how to solve it, please help

Hi,You should check with experts in the Answers XP Forums.Answers - XP Forumshttp://social.answers.microsoft.com/Forums/en-US/category/windowsxp==============================================Here are VISTA troubleshooting method which can help. One tip is anywhere is says to useStart - Search in Vista then use RUN in XP instead. =================================================================Check this thread for information on using BlueScreenView, MyEventViewer, and other methods totroubleshoot BlueScreens - top 3 methods (+1 other). Remeber these are Vista methods so youwill need to translate to XP methods which is not that difficult in most cases. http://social.answers.microsoft.com/Forums/en-US/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009-------------------------Drivers could be at fault however disk issues or antivirus/antispyware/security products arejust as likely to be the root cause as they can force a driver to corrupt or go out of bounds.The video driver or something affecting it would be very suspect.Be sure the drivers, BIOS, and low level chipset driver are all updated by manually checkingat the System maker and device makers's sites. -----------------------------------BCCode: 0A 0x0000000A <-- all of this section applies to XP, Vista, or Windows 7.CauseThis bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.Resolving the ProblemIf a kernel debugger is available, obtain a stack trace.To resolve an error caused by a faulty device driver, system service, or BIOSRestart your computer. Press F8 at the character-based menu that displays the operating system choices.Select the Last Known Good Configuration option from the WindowsAdvanced Options menu. This option is most effective when only one driver or service is added at a time. To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup toolCheck the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.Try disabling memory caching of the BIOS. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.Make sure the latest Service Pack is installed. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks. If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.CommentsBefore upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.BCCode: 0A 0x0000000A <-- read this linkhttp://www.faultwire.com/solutions-fatal_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-*1025.htmlHope this helps.Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

It appears you have Blue Screen View installed, but we will need more information to reduce the amount of guessing and trying things.Please provide additional information about your system:What is your system make and model?What is your XP version and Service Pack?Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.Does the afflicted system have a working CD/DVD drive?Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?Fill in the blank: My system was working fine until _________________________________________.Click Start, Run and in the box enter:msinfo32Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information back here.There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.This will minimize back and forth Q&A and eliminate guesswork.Download BlueScreenView from here:http://www.nirsoft.net/utils/blue_screen_view.htmlUnzip and run it (BSV installs nothing) and let it finish scanning all your crash dump files. If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files. Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt. Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:==================================================Dump File : Mini062110-01.dmpCrash Time : 6/21/2010 11:51:31 AMBug Check String : MANUALLY_INITIATED_CRASHBug Check Code : 0x000000e2Parameter 1 : 0x00000000Parameter 2 : 0x00000000Parameter 3 : 0x00000000Parameter 4 : 0x00000000Caused By Driver : i8042prt.sysCaused By Address : i8042prt.sys+27fbFile Description : i8042 Port DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2108)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\minidump\Mini062110-01.dmp==================================================Send the information from the last 5 memory dumps.Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

==================================================Dump File : Mini112310-02.dmpCrash Time : 23/11/2010 01:53:11Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000020Parameter 2 : 0x891dd910Parameter 3 : 0x891de1f8Parameter 4 : 0x0b1dc99cCaused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+22f43File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112310-02.dmpProcessors Count : 2Major Version : 15Minor Version : 2600====================================================================================================Dump File : Mini112310-01.dmpCrash Time : 23/11/2010 00:57:48Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0xc0000005Parameter 2 : 0x8054b71cParameter 3 : 0x9f19fb30Parameter 4 : 0x00000000Caused By Driver : fltmgr.sysCaused By Address : fltmgr.sys+70fdFile Description : Microsoft Filesystem Filter ManagerProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112310-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600====================================================================================================Dump File : Mini112210-04.dmpCrash Time : 22/11/2010 23:54:25Bug Check String : IRQL_NOT_LESS_OR_EQUALBug Check Code : 0x1000000aParameter 1 : 0x00000000Parameter 2 : 0x0000001cParameter 3 : 0x00000001Parameter 4 : 0x80502300Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+2b300File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112210-04.dmpProcessors Count : 2Major Version : 15Minor Version : 2600====================================================================================================Dump File : Mini112210-03.dmpCrash Time : 22/11/2010 23:47:40Bug Check String : IRQL_NOT_LESS_OR_EQUALBug Check Code : 0x1000000aParameter 1 : 0x00000001Parameter 2 : 0x0000001cParameter 3 : 0x00000001Parameter 4 : 0x80502300Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+2b300File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112210-03.dmpProcessors Count : 2Major Version : 15Minor Version : 2600====================================================================================================Dump File : Mini112210-01.dmpCrash Time : 22/11/2010 22:32:41Bug Check String : DRIVER_CORRUPTED_EXPOOLBug Check Code : 0x100000c5Parameter 1 : 0x00000005Parameter 2 : 0x00000002Parameter 3 : 0x00000001Parameter 4 : 0x8054bfd2Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+74fd2File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112210-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600==================================================My computer is home built.OS Name Microsoft Windows XP Home EditionVersion 5.1.2600 Service Pack 3 Build 2600OS Manufacturer Microsoft CorporationSystem NameSystem Manufacturer To Be Filled By O.E.M.System Model To Be Filled By O.E.M.System Type X86-based PCProcessor x86 Family 15 Model 107 Stepping 2 AuthenticAMD ~2792 MhzBIOS Version/Date American Megatrends Inc. P2.60, 09/04/2008SMBIOS Version 2.4Windows Directory E:\WINDOWSSystem Directory E:\WINDOWS\system32Boot Device \Device\HarddiskVolume2Locale United StatesHardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"Total Physical Memory 3,072.00 MBAvailable Physical Memory 2.27 GBTotal Virtual Memory 2.00 GBAvailable Virtual Memory 1.96 GBPage File Space 4.84 GBPage File E:\pagefile.sysIm using microsoft security essentials for virus checker I,m using a copy of my microsft windows xp home edition diskMy system does have a working cd dvd driveThe problem started after installing a new audio card and installing fallout new vegas, only crashes during that game and im having no problems/crashes when doing anything elseChecks that i have made: memtest86 10 passes no fails. chkdsk: 3 times sfc /scannow no problems foundgoing to try disabling audio card now and see if thats causing the problem

Seems to be the audio card thats causing the problemdid a driver roll back and my pc crashed==================================================Dump File : Mini112310-03.dmpCrash Time : 23/11/2010 22:37:23Bug Check String : IRQL_NOT_LESS_OR_EQUALBug Check Code : 0x1000000aParameter 1 : 0xcffffffcParameter 2 : 0x0000001cParameter 3 : 0x00000000Parameter 4 : 0x80502367Caused By Driver : win32k.sysCaused By Address : win32k.sys+1244File Description : Multi-User Win32 DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.6033 (xpsp_sp3_gdr.100831-1644)Processor : 32-bitComputer Name : Full Path : E:\WINDOWS\Minidump\Mini112310-03.dmpProcessors Count : 2Major Version : 15Minor Version : 2600==================================================Went back to the original sound driver and the system crashedDisabled the soundcard and everything is working fine,Does that mean the audio card cant be solved as even the original driver causes system crashes? Would i be better off just going out and buying a better audio card?

Is the computer dual booting? The dump is on E?Hope this helps, Gerry Cornell

I have 2 hard drives using the larger harddrive atm, Its definately a sound card problem seems i need a new one as no driver fixes the problem tried 7 now and always the same outcome, disable it and everything works fine

On 11/23/2010 7:29 PM, fingers75 wrote:I have 2 hard drives using the larger harddrive atm, Its definately asound card problem seems i need a new one as no driver fixes theproblem tried 7 now and always the same outcome, disable it andeverything works fineYou said in a earlier post: "The problem started after installing a new audio card and installing fallout new vegas, only crashes during that game and im having no problems/crashes when doing anything else"I would think that the problem is with the game rather than the sound card. Did you ask the game support people about the problem? These game vendors usually have support forums, did you check or ask on one of these forums?John

Hi,You can disable on-board sound in the BIOS or remove an add-in Sound Card to see ifthat stops the issues. An add-in sound card is not that expensive and there are alsoinexpensive USB Sound Cards available.Hope this helps.Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

Once i disabled the soundcard everything worked fine even the game ran without any problems, Been out and bought a new soundcard and installed it yesterday and im happy to report everythings going swimmingly so far. nothing seems to be out of place and the pc is running fine, thanks for your help guys, this problem definately seems to be solved atleast, who knows what the next one will be lol

Glad to have helped. Good Work sorting that out.Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.