*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {ffffcf829d50cfe0, ffffcf829d50cb26, 4b0020, 32}
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+8a )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41792, fffff6bffe21cb20, 10000000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
Followup: MachineOwner
Er..... I did ask in post #9 if the verifier was running.I wanted you to run the driver verifier but it looks like it might be running?
It's not like a scan of sorts where there's a start and a finish. It runs for as long as you let it run and really the longer the better. If you can leave it going overnight or as near to 12hrs as you can then this is better unless of course errors pop up straight away in which case you can stop.How long does memtest take to complete?
In a word .. no..does memtest can harm your data file?
How do i choose the setting for memtest?