Hello. I've had quite a bit of blue screens with my computer since I upgraded to Windows 7. I ran the Upgrade Advisor before attempting anything, then kept the system at Windows XP for a week to ensure everything was working first. My problems seem to point to an issue with the USB subsystem. I've run KB976972 because I have an nVidia GeForce 6600 video adapter, but the problems persist.My system is:HP Pavilion a610y (D7223G) CTO Desktop PCSystem chassis Micro ATX HP Pavilion a-series chassisDimensions (H x W x D): 15.75 x 7.5 x 15.75 inches Processor Intel Pentium 42.6 GHz Motherboard name MIS: MS-6577 M-ATXHP: Giovani2-GL6 Chipset Intel i845GV Front-side-bus (processor dependent) 400 MHz Power output wattage 250 Watt Memory Memory slots: 2 DIMMS512 MB DDR / PC2100 (1 DIMM)Maximum memory: 1 GB (HP tested and recommended), 2 GB (motherboard specified) BIOS Type: Phoenix-Award BIOS v6.00PG BIOS ID: 03/16/2004-i845G-W627-6A69VM4VC-00 BIOS Date: 20040316 BIOS Vendor: Phoenix Technologies, LTD BIOS Version: 3.00 BIOS Size: 524288 Chipset: Intel 2560 rev 1 OEM Sign-on: Rev. 3.00 03/16/2004 Motherboard Name: Hewlett-Packard Motherboard Model: PPPPPP-ABA MMMMM Base Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD Base Product: MS-6577 The various blue screens I've had so far are (using BlueScreeView from NirSoft):==================================================Bug Check String : PAGE_FAULT_IN_NONPAGED_AREABug Check Code : 0x10000050Parameter 1 : 0xd7ff0865Parameter 2 : 0x00000000Parameter 3 : 0x89bd75c6Parameter 4 : 0x00000002Caused By Driver : SYMEVENT.SYSCaused By Address : SYMEVENT.SYS+1bfa0File Description : Symantec Event LibraryProduct Name : SYMEVENTCompany : Symantec CorporationFile Version : 12.8.0.10================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000020Parameter 2 : 0xff8df8f8Parameter 3 : 0xff8df8f8Parameter 4 : 0x4a000018Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+117c4eFile Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : PAGE_FAULT_IN_NONPAGED_AREABug Check Code : 0x10000050Parameter 1 : 0x8e1c3c00Parameter 2 : 0x00000000Parameter 3 : 0x8286b17bParameter 4 : 0x00000000Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+5d17bFile Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : PFN_LIST_CORRUPTBug Check Code : 0x0000004eParameter 1 : 0x00000099Parameter 2 : 0x0002c503Parameter 3 : 0x00000002Parameter 4 : 0x0002c501Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+d1574File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : PAGE_FAULT_IN_NONPAGED_AREABug Check Code : 0x00000050Parameter 1 : 0xcccca3beParameter 2 : 0x00000000Parameter 3 : 0x93d1fbf0Parameter 4 : 0x00000002Caused By Driver : SYMEVENT.SYSCaused By Address : SYMEVENT.SYS+1cc10File Description : Symantec Event LibraryProduct Name : SYMEVENTCompany : Symantec CorporationFile Version : 12.8.0.10================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000003Parameter 2 : 0xa40db8c8Parameter 3 : 0x00000000Parameter 4 : 0xa40db8c8Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+d1574File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0xc0000005Parameter 2 : 0x9418e5c8Parameter 3 : 0xaea77b94Parameter 4 : 0x00000000Caused By Driver : win32k.sysCaused By Address : win32k.sys+ce5c8File Description : Multi-User Win32 DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16385 (win7_rtm.090713-1255)================================================== ==================================================Bug Check String : BAD_POOL_CALLERBug Check Code : 0x000000c2Parameter 1 : 0x00000007Parameter 2 : 0x00001097Parameter 3 : 0x00000000Parameter 4 : 0xfd1cc840Caused By Driver : win32k.sysCaused By Address : win32k.sys+cde00File Description : Multi-User Win32 DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16385 (win7_rtm.090713-1255)================================================== ==================================================Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0xc0000005Parameter 2 : 0x829664a3Parameter 3 : 0x80fc600cParameter 4 : 0x00000000Caused By Driver : BHDrvx86.sysCaused By Address : BHDrvx86.sys+4645File Description : Product Name : Company : File Version : ================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000020Parameter 2 : 0xff3b98e0Parameter 3 : 0xff3b9998Parameter 4 : 0x4a17011cCaused By Driver : win32k.sysCaused By Address : win32k.sys+218fc8File Description : Multi-User Win32 DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16385 (win7_rtm.090713-1255)================================================== ==================================================Bug Check String : PFN_LIST_CORRUPTBug Check Code : 0x0000004eParameter 1 : 0x00000099Parameter 2 : 0x00077a45Parameter 3 : 0x00000001Parameter 4 : 0x00077a35Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+d1574File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000020Parameter 2 : 0x9c2ac9f0Parameter 3 : 0x9c2ac9f0Parameter 4 : 0x0a00020fCaused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+117c4eFile Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : PAGE_FAULT_IN_NONPAGED_AREABug Check Code : 0x00000050Parameter 1 : 0xffffffd8Parameter 2 : 0x00000000Parameter 3 : 0x938ec4d1Parameter 4 : 0x00000000Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+5ec46File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000020Parameter 2 : 0xa031d8c0Parameter 3 : 0xa031dd50Parameter 4 : 0x0a920205Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+117c4eFile Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16481 (win7_gdr.091207-1941)================================================== ==================================================Bug Check String : BAD_POOL_HEADERBug Check Code : 0x00000019Parameter 1 : 0x00000003Parameter 2 : 0x84836790Parameter 3 : 0x84836790Parameter 4 : 0x84806790Caused By Driver : SRTSP.SYSCaused By Address : SRTSP.SYS+2c828File Description : Product Name : Company : File Version : ================================================== ==================================================Bug Check String : NTFS_FILE_SYSTEMBug Check Code : 0x00000024Parameter 1 : 0x001904fbParameter 2 : 0x8de5a6f4Parameter 3 : 0x8de5a2d0Parameter 4 : 0x89430521Caused By Driver : Ntfs.sysCaused By Address : Ntfs.sys+c521File Description : NT File System DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7600.16385 (win7_rtm.090713-1255)==================================================I have minidumps and msinfo files available.Thanks,Chipwich

Greetings, Bug Check 0x4E: PFN_LIST_CORRUPT parameter 1 0x99 indicates a page table entry (PTE) or PFN is corrupt.This error is typically caused by a driver passing a bad memory descriptor list. Bug Check 0x19: BAD_POOL_HEADER Parameter 1 0x3 indicates The pool freelist is corrupt.Bug Check 0x8E Parameter 1 0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred. It seems to have something to do with memory. I recommend you to run Memory Test.1. Restart your computer.2. Press F8 early and repeatedly while booting,( don't hold it down), and the Safe Mode menu screen should show up3. Select “Repair your computer” 4. After a while, you come to System Recovery Options Screen, select “Windows Memory Diagnostic Tool” 5. Select the “Restart now and check for problems” option, the computer will restart.6. Windows Memory Diagnostic Test will run standard test by default (you can press F1 to choose the test type: Basic, Standard, Extended )7. When the test if finished, it will automatically restart the computer. If errors are found, the Windows Memory Diagnostic Tool will attempt to determine which particular memory module in your computer is causing these errors. If that information is available, it will be stated in the results after you log on from the restart.If bad memory is found then you will need to remove that memory and replace it. Generally speaking, after upgrading, you need to update to date your hardware driver.You can install HP Software Update Utility, which will delivers and installs drivers, fixes, and critical software updates for computers and HP products.Also you can use Windows Update to automatically update. (Start -> All Programs-> Windows Update-> Check online for updates from Microsoft Update) In order to check more detail info in dump file, can you upload you minimum log to skydive? Here is a note for it:http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 =================1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. To collect memory dump files if the Blue Screen appears again:=================1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.2. Go to your desktop, right-click on it and create a new folder named "Dump".3. Copy all the memory dump files (looks like [Mini100302-01.dmp]) in minidump to this folder.4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".5. Please upload the file to SkyDrive, select the "Everyone (Public)" option in the "Share with" box and attach the link of the network location here. Please let me know the result, and hope it will help you!

Hello again.Sorry I haven't replied earlier. I thought I was going to get an e-mail notice if anyone posted. I will get this info and get back to you.Chipwich

Well, I think I've got a resolution and yes, Martin, it was a memory problem. I ran the Windows 7 Memory Diagnostics and it took over NINE HOURS for 5 passes! It kept locking at 21% for at least 45 minutes with each pass, but the test ended up showing no problems. On your hunch, I swapped my 2 DIMMS and after reboot, immediately got a STOP 0xA5. I pulled the RAM chip from slot #2, and the system booted fine (although Windows wanted to run a Repair from the STOP error). The repair found nothing wrong. So, the BIOS reports both slots filled and functional, and all memory tests, except the hang time, showed no errors. I removed the RAM chip from slot #1 and put it in #2 and the BIOS wouldn't boot because it found no memory. I swapped it out with the other RAM chip and got the same. I put the second RAM chip in slot #1 and the system booted fine. I think the second DIMM slot is bad, and I'll be looking for a new motherboard, although I'll wait a day or two to see if their are any more issues. It appears to be running fine with the 1 DIMM in slot #1 right now. Thanks for your assistance; I really appreciate it.Chipwich

More bad news (for me). I've had 4 more blue screens today, even after clearing the slot #2 DIMM. I will be uploading my minidumps to SkyDrive soon.Chipwich

More bad news (for me). I've had 4 more blue screens today, even after clearing the slot #2 DIMM. I will be uploading my minidumps to SkyDrive soon.Chipwich hi , when you reboot do you get a small pop up asking for the memory dump o be send to microsoft ?check your problem reports and solutions also and send them all click the link ' Microsoft support ' below in my signature and follow , down and get a chat with the microsoft support staff , the will be able to see what is going on and be able to provide you with a solution have a nice dayScan with OneCare + 50 Windows 7even Tips + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR+ Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! + Get Windows LIVE! +

Thanks for replying. I wasn't sure whether this thread was closed since it's marked as answered. I have uploaded my minidumps to SkyDrive > Chipwich > Dumps. You should have access there. I'm having a bit of trouble getting past the Trusted Sites verification on the Microsoft Support page. I'll try again later.Chipwich

Thanks for replying. I wasn't sure whether this thread was closed since it's marked as answered. I have uploaded my minidumps to SkyDrive > Chipwich > Dumps. You should have access there. I'm having a bit of trouble getting past the Trusted Sites verification on the Microsoft Support page. I'll try again later.Chipwich hi , use the link in my signature , that works , if that still does not go lower your security settings and privacy options in your browser to medium high , turn pop up blocker also off , close the browser and restart it , try again .you can also do a few things yourself , click the onecare link below and run a full scan overnight or so , do NOT use the comp while it scans and close all other security software , email , games , sidebar , etc , .... you can also do a disk check yourself , flag both options ( !! )or as a last hope you can ' repair ' your os with the installation disk of windows , note that you should safe your documents and pictures online and on a good external hard drive ( !! ) have a nice dayScan with OneCare + Support ENDING for windows Vista & XP ! + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR + Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! + Windows LIVE !

Hi,you may perform System File Checker [SFC] scan on the computer, the scan replaces the corrupted system files with the original Windows version files, follow the steps below to perform the scan: 1. Click Start, and then type cmd in the Start Search box. 2. Right-click cmd in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or confirmation, type your password or click Continue 3. At the command prompt, the following line, and then press ENTER: sfc /scannowIn addition, SkyDrive > Chipwich > Dumps is just a relative path for you, you should attach the URL here. Don't miss out putting the dumps into the public folder to share them.

Hi,you may perform System File Checker [SFC] scan on the computer, the scan replaces the corrupted system files with the original Windows version files, follow the steps below to perform the scan: 1. Click Start, and then type cmd in the Start Search box. 2. Right-click cmd in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or confirmation, type your password or click Continue 3. At the command prompt, the following line, and then press ENTER: sfc /scannowIn addition, SkyDrive > Chipwich > Dumps is just a relative path for you, you should attach the URL here. Don't miss out put the dumps into the public folder to share them. hi , i really doubt if the system file checker will provide a solution in this case , .... chip some links so you get more info , dont put any hopes on sfc , you are probably to far ' damaged ' ( not you but the comp ) http://support.microsoft.com/kb/929833http://support.microsoft.com/kb/936212http://support.microsoft.com/kb/188186http://support.microsoft.com/kb/929833/en-ushttp://msdn.microsoft.com/en-us/library/aa382541(VS.85).aspxthis link shows you how to read and find the sfc logs ( called cbs logs ) you can post them chip if you decide to run it http://support.microsoft.com/search/default.aspx?query=CBS%20logs&catalog=LCID%3D1033how to analyse the cbs logs http://support.microsoft.com/kb/928228this is an example why ( sfc ) it will not always be the magical fix some hope it is , ...http://support.microsoft.com/kb/929840have a nice dayScan with OneCare + Support ENDING for windows Vista & XP ! + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR + Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! + Windows LIVE !

I chatted with a Microsoft tech last night from the Support link you gave me. In the end, the conclusion was motherboard/memory (hardware) issues. Oh, and I had already run the SFC, which came back clean. It was a shot in the dark anyway to upgrade this old system. I may try replacing the motherboard, which will still be cheap. Thanks for the feedback, guys. Keep up the good work!Chipwich

I chatted with a Microsoft tech last night from the Support link you gave me. In the end, the conclusion was motherboard/memory (hardware) issues. Oh, and I had already run the SFC, which came back clean. It was a shot in the dark anyway to upgrade this old system. I may try replacing the motherboard, which will still be cheap. Thanks for the feedback, guys. Keep up the good work!Chipwich hi , good to hear that ! okay check and double check first , it might even be better for example to get a good oem from lets say fujitsu or a good brand and put in some extra mem and a few other things you need , ....oh yeah , you can mark what you see fit as the answer till next time have a nice dayScan with OneCare + Support ENDING for windows Vista & XP ! + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR + Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! + Windows LIVE !