Squall Leonhart
-
Posts
382 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Events
Posts posted by Squall Leonhart
-
-
mrgreywater, CoreTemp has the wrong TJmax for that cpu, the 65nm chips are 90
http://www.tomshardware.co.uk/intel-dts-specs,news-29460.html
-
No its not a bug, an adapter is displayed for each dvi/display/hdmi port on the card
-
randomly after a while.
and like i said, just on Motherboard\Memory
i can have any other views/lists open for weeks on end and it runs fine
its actually the drive i have all my games installed on, and none of those crash (barring the odd game bug)
-
aida64 initiates a driver when run, requiring admin elevation.
-
the Tjmax for SB is 95c
the Tjmax for IB is 105c
as long as you keep below this point it should be safe.
-
Raid enumeration + IRSTe 3.2 or IRST 11.2 are required
IRSTe is not available yet
-
i should mention, i've also seen this on other Intel systems, those being 2 Pentium dual core notebooks, and also on a amd laptop while sitting on the memory tab, so i can't really tell whats going on. Maybe whatever function to access the page file stats is tripping windows up eventually?
-
Complete removing the driver also requires some registry work, as the driver installs a lowerfilter that is not removable via the limited inf uninstallation capabilities
-
Usually about the 75% mark, windows starts to aggressively page out what it can in pre-empt of more memory being needed
-
Sometimes i forget to switch back to one of the other pages after looking at the current memory stats (i mainly use it to see how much the page file is loaded).
Faulting application name: aida64.exe, version: 2.50.2018.0, time stamp: 0x2a425e19
Faulting module name: aida64.exe, version: 2.50.2018.0, time stamp: 0x2a425e19
Exception code: 0xc0000096
Fault offset: 0x002f6074
Faulting process id: 0x1334
Faulting application start time: 0x01cd51797c2d7dbe
Faulting application path: D:\Tools\System Tools\AIDA64\aida64.exe
Faulting module path: D:\Tools\System Tools\AIDA64\aida64.exe
Report Id: 39103caa-bd71-11e1-b497-a668464cb7fa
I was thinking it may have been a general exception or virtual alloc leak, but windows event viewer reported something much much different.
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program AIDA64 Extreme Edition because of this error.Program: AIDA64 Extreme Edition
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
Now thats a strange thing to report. The drive its on is still present in the system, i can subsequently restart Aida64 immediately after this crash and simply changing from the Memory page to any one of the others will have it work fine for ever after.
Do you have any Symbols i could use in windbg so i can attach the debugger and get a crash dump?
-
Hmm, that flashing thing is very similar to the low memory scenario i was describing.
are either of the Paged pools using alot of memory on the performance tab?
-
indeed. a friend of mine had to mess with his radeon drivers because of the lack of edid causing issues with digital scaling.
-
Check for any of your apps having a higher amount of memory used in the Commit column vs the Working set column (Windows only displays private bytes by default, so both of these need to be enabled in the columns configuration in task manager)
if the commit column is a fair bit higher, it means part of the process's memory usage has been paged out to disk
the Memory page in aida64 will also tell you how much Pagefile is being utilised too.
-
try the new 11.2.0.1006 drivers sora
also how much ram d oyou have? maybe when you're gaming the windows components are paged out and you get excessive disk thrashing after closing the game
-
having 2 applications accessing smart at once can cause lag and heavy DPC in my testing.
-
Its definitely a driver bug then, Fiery if you could forward Arctucas's findings to intel it might prevent 11.5 finally landing with critical bsod issues.
-
the gadget is compiled, a simple hex edit will not be enough to ensure compatibility.
-
try reproducing the issue against Crystal Disk info 5 alpha
-
coincidentally it also fixed the ndis and usbstor dpc bugs
-
check and make sure raid member enumeration is enabled
-
the service is part of the GUI (C:\Program Files (x86)\Intel\Intel® Rapid Storage Technology\IAStorDataMgrSvc.exe)
The beta pack available only updates the driver components.
Barring any changes to the driver functionality wise (other then the changes to SPTI and SMART routines), the older UI/Service executables are fully compatible with the new driver
-
There is no GUI in this beta.
Intel only update the GUI when needs be, which is why there has been a couple of recent versions which have an older driver version but newer gui or older gui and newer driver.
-
spin up and spin down is the most intensive part of a hdd's operations anyhow, so its best to either keep spin ups low or always keep it spinning
-
just run dpinst in the extracted folder (if you get it from stationdrivers)
it will handle the installation
Still getting a consistently reproducible crash when leaving Aida64 to sit on the Memory Page.
in Bug reports
Posted
in VS it says
The thread tried to execute an instruction whose operation is not allowed in the current machine mode.
in all dumps for this particular crash