New
#11
I accidentally switched from small memory dump to Kernel....
i am sure it will crash in no time and i will provide the file
COmputer was idle and BSOD'ed with 0x000001E code
I accidentally switched from small memory dump to Kernel....
i am sure it will crash in no time and i will provide the file
COmputer was idle and BSOD'ed with 0x000001E code
For some reason, i can't locate the DMP files....Win7 is not generating and I checked all the options
A driver may well be behind all of this.
Lets give Driver Verifier a try see if it can pick anything up.
Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests
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.
Information
We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It
Driver Verifier will make the system laggy, this is normal so don't worry.
Before enabling DV, make sure that you have earlier System restore points made in your computer.
If there are no points, make a System Restore Point Manually
Post back the results.
After the crash, memdump should be created?>
crashes out, but nothing is created.
Tried running Lightroom from Safe mode....BSOD - hardware.
Clueless
Ah yes I forgot.
You had errors before in memtest.
Try testing each stick at a time.
I am re-installing win7 and will try with a clean system. Will report back
i am leaning towards driver conflict
Did you replace the faulty RAM?
If I recall correctly, you:
1. Got 2 errors when all the DiMM's were inserted; and
2. Got 0 errors when you tested them individually
When you performed the individual tests, did you run for a minimum of 8 passes on each?
If you haven't solved this particular issues, then I would concluded either the RAM and/or motherboard is faulty. You will continue to experience 0x124 BSOD's until you get to the bottom of that.