New
#11
Still getting them sadly...
Still getting them sadly...
Your latest crash dump not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Let us know the results, with the subsequent crash dumps, if any.
Will do, thanks!
Blue screened at 7pm. First with java and flash player running (does it quite a bit like that) and then upon pushing enter to log back in to windows following a restart.
Don't know if that information helps :)
Also, one blue screen error was 'paged area in non paged area' or something similar
The first one is caused by the display driver.
Update it from Latest NVIDIA ForceWare Video Drivers Windows 7.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {91e0000c, 0, 0, 82cb0118} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+6ac2e ) Followup: MachineOwner ---------
But the other one, Page fault in non-paged area is not giving any information. If after updating the display driver it crashes again, enable driver verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Let us know the results, with the subsequent crash dumps, if any.
Crashed 3 times after another.
First saying: cyfs.sys or cyls.sys error
second saying dxgkrnl.sys - driver over ran stack based buffer, overrun allow user to gain control
third, remaining stuck at 5% when writing the dump for 15mins
You first Do some disc checks.
- Update your SSD's Firmware (Skip it, if it is not a SSD)
- Re-seat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Uninstall Spybot.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.
Rollback the graphics driver to an older one.
- Download and install Driver Fusion.
- Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
- Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.
And, plan to update the BIOS. It is too old.
Let us know the results.Code:BiosMajorRelease = 8 BiosMinorRelease = 15 BiosVendor = American Megatrends Inc. BiosVersion = V2.0S BiosReleaseDate = 12/16/2008
I followed your steps.
The SSD resulted in the attached image. I configured the drive to IDE correctly.
Check disk found nothing.
Haven't ran Seatools yet since no free CD's, should be getting some today.
Uninstalled Spybot. Installed the NVidia driver as instructed.
Where would I go to find a BIOS update? Since I couldn't find any help
Also attached new logs
Last edited by Popesture; 03 Dec 2012 at 06:58.
For updates, search in your SSD manufacturer's website.
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C5, {c1d00004, 2, 1, 82d734c1} Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+4b7 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * 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: c1d00004, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 82d734c1, address which referenced memory Debugging Details: ------------------ BUGCHECK_STR: 0xC5_2 CURRENT_IRQL: 2 FAULTING_IP: nt!ExAllocatePoolWithTag+4b7 82d734c1 897004 mov dword ptr [eax+4],esi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe TRAP_FRAME: a1877704 -- (.trap 0xffffffffa1877704) ErrCode = 00000002 eax=c1d00000 ebx=82d896c0 ecx=858b3990 edx=858e1e18 esi=82d89898 edi=82d896c4 eip=82d734c1 esp=a1877778 ebp=a18777c0 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!ExAllocatePoolWithTag+0x4b7: 82d734c1 897004 mov dword ptr [eax+4],esi ds:0023:c1d00004=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 82d734c1 to 82c92cdb STACK_TEXT: a1877704 82d734c1 badb0d00 858e1e18 a1877774 nt!KiTrap0E+0x2cf a18777c0 82e939ac 00000000 00000088 66496553 nt!ExAllocatePoolWithTag+0x4b7 a18777e4 82e878b6 00000000 a1877850 8ba729b3 nt!SeLocateProcessImageName+0x3a a1877888 82e7331e 194a0a00 00002000 a1877cd0 nt!ExpGetProcessInformation+0x355 a1877d00 82e83ed4 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1035 a1877d1c 82c8f8fa 00000005 194a0a00 00002000 nt!NtQuerySystemInformation+0x76 a1877d1c 77417094 00000005 194a0a00 00002000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 05f1f2cc 00000000 00000000 00000000 00000000 0x77417094 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExAllocatePoolWithTag+4b7 82d734c1 897004 mov dword ptr [eax+4],esi SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExAllocatePoolWithTag+4b7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 503f7f43 FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+4b7 BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+4b7 Followup: MachineOwner ---------
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Let us know the results, with the subsequent crash dumps, if any.
Also, your BIOS is very old. If possible, update it.
Code:Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=1768] BiosMajorRelease = 8 BiosMinorRelease = 15 BiosVendor = American Megatrends Inc. BiosVersion = V2.0S BiosReleaseDate = 12/16/2008
I did for the SSD, the update would not complete.
And I asked last post where about could I find BIOS update?