Unfortunately, while my previous BSOD issue was solved, I've been experiencing new BSODs with a different error code, this time C5 stop codes. The blue screen itself points to an issue with one of the drivers but I'm not exactly sure which one it could be, seeing as the latest driver I installed was Catalyst 10.4 and that's been working fine for weeks prior to this. I've attached the dump files and hope you guys can help. Thanks.
These were probably casued by two differernt things. First your RAID driver and second realplayer.
I would update the RAID driver and remove real player.
Code:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Jun 1 18:06:38.770 2010 (GMT-4) System Uptime: 1 days 4:21:30.380 BugCheck C5, {fffffa8009dc4218, 2, 1, fffff8000380790d} *** WARNING: Unable to verify timestamp for iaStor.sys *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys Probably caused by : iaStor.sys ( iaStor+26417 ) BUGCHECK_STR: 0xC5_2 PROCESS_NAME: IAStorDataMgrS ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed May 26 18:49:46.905 2010 (GMT-4) System Uptime: 0 days 9:50:53.497 BugCheck C5, {8, 2, 1, fffff8000380b90d} Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceOpen+409 ) BUGCHECK_STR: 0xC5_2 PROCESS_NAME: realplay.exe
That's for your bugcheck C5.Usual causes: Device driver, ?Memory.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
Enable driver verifier: Using Driver Verifier to identify issues with Drivers
Taking your advice into account, I have uninstalled Realplayer and run memtest86 for the requisite number of passes. However, memtest86 turned up nothing out of the ordinary and my RAID driver was fully up to date, all of it leading up to experiencing another BSOD. I've attached the dump file (again) and I'm starting to get the feeling that there's something wrong with a component in the machine itself. Any help would be appreciated.
This one points to the network adapter drivers.Update them, or uninstall and install a fresh copy.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp16_Minidump.zip\052110-18361-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0415c500? Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e95e50 Debug session time: Fri May 21 14:27:02.725 2010 (GMT-4) System Uptime: 0 days 5:21:55.724 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8005d61060, fffff8000415c518, fffffa800a9758c0} *** WARNING: Unable to verify timestamp for Rt64win7.sys *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys Probably caused by : Rt64win7.sys Followup: MachineOwner ---------
Updated the network driver but got hit with another BSOD. Attached the dump file. At this point, it's almost getting marginally ridiculous how so many different programs/drivers are causing BSODs.
Another BSOD, though this time it wasn't a C5 error. Attached the dump file.
Your .dmp files shows daorigins.exe ( Dragon Age Origins ) as the cause of your crash... Uninstall and then try reinstalling ... be careful where you get the file ...
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff800037f690d, address which referenced memory Debugging Details: ------------------ BUGCHECK_STR: 0xC5_2 CURRENT_IRQL: 2 FAULTING_IP: nt!ExAllocatePoolWithTag+53d fffff800`037f690d 48895808 mov qword ptr [rax+8],rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: daorigins.exe
Weird. The game is legit and wasn't gotten through "alternative" means and hasn't had any faults before for the past month. This entire process is just getting weirder and weirder and I have no clue what's at the root cause for so many of these errors. Each time I uninstall something which causes the BSOD, I get another BSOD which points to a different program being the root cause.Your .dmp files shows daorigins.exe ( Dragon Age Origins ) as the cause of your crash... Uninstall and then try reinstalling ... be careful where you get the file ...
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff800037f690d, address which referenced memory Debugging Details: ------------------ BUGCHECK_STR: 0xC5_2 CURRENT_IRQL: 2 FAULTING_IP: nt!ExAllocatePoolWithTag+53d fffff800`037f690d 48895808 mov qword ptr [rax+8],rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: daorigins.exe
Had a weird as heck BSOD as I was shutting down the computer. Dump file is attached.
Quote