New
#11
No problem mate, we'll be here.
Just had another BSOD, hopefully uploaded the zip files!
Many thanks inadvance
Nick your single dump is a 0x4E (PFN_LIST_CORRUPT), this could be down to bad RAM or a device driver. No drivers are showing in your dump (it may be too small a sample size) so first of all I'd like you to rule out your RAM being a problem.
Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+
Note
Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 307df2, 2, 307df0} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 0000000000307df2, page frame number Arg3: 0000000000000002, current page state Arg4: 0000000000307df0, 0
Ok,thanks.
I have run memtest86 I ran it for 5 passes the other day from an iso file.
I will do that tonight and leave it until at least 8 passes, It did 5 passes in around 6 hours, does that sound normal?
Ah! not sure so I will follow your instructions above.
Will post the results tomorrow.
Ok, 16 hours of testing and all is good, no errors.
That's good. Time to try and weed out the bad driver then.
Diagnostic Test
DRIVER VERIFIER
Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable
Enable Driver Verifier but only enable these options:
- Standard settings and IRP logging step 3.
- Don't enable Force Pending I/O Requests
WarningMake a System Restore point before enabling Driver Verifier.
NoteYour system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Post any resulting dump files.
Thanks, will follow next step, just doing a back up now.