Hi,
I left a new build on overnight and saw there was a blue screen warning (see attached)
I then went to run the Win 7 memory check but when the pc rebooted I got:
"boot memtest.exe missing or corrupt"
I then did a memory test with a different program (passed)
I then did a Windows disc check (passed)
Any ideas?
Thanks,
Mike
Here is the SF grabber files
Hi Mike, welcome to 7F.
Your single dump is a STOP 0x19 which is normally down to a device driver.
The dump itself is inconclusive as it shows no drivers, but this bugcheck has been attributed to ESET in the past. Before we look an enabling Driver Verifier could you please uninstall ESET and install MS Security Essentials and MalwareBytes.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffff8a00f43f090, fffff8a00f43f2f0, 5260409} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkEscape+c3f ) Followup: MachineOwner
NoteMake sure you uncheck the 'Enable Free Trial' box when installing MalwareBytes.
Test and report back.
Hi boozad,
I think the culprit could be a graphic driver.
This pc was built using a ghost image along with 25 others.
The master pc had an ATI card, the newer ones an Nvidia.
Normally Win7 is pretty tolerant of a change like this but maybe the different card freaked it out a bit.
I've used Display Driver Uninstaller and not had a crash since.
More worrying is the "boot memtest.exe missing or corrupt" when trying to use the Win7 memory check.
Any ideas on that?
Thanks mate,
Mike
If you're trying to test the RAM I'd recommend using MemTest86+.
Personally I always go for clean installs of Windows so I don't know in this case what's been copied over and what hasn't. You could always open an elevated command prompt, type in sfc /scannow and hit enter. See what the system file checker says.
When I have 45 pc's to install I'm not doing clean installs:)
Here's the sfc checker, came back as clean.
It hasn't crashed since that initial crash the other day and I've already done a memory check with another program, fingers crossed.
Thanks for the help,
Mike
Oh I understand that, I was just pointing out I've never has experience of ghosting so have no idea of the trials and tribulations involved. It does make sense though that if you had AMD drivers on a machine with nVidia hardware it would cause issues.
Keep us posted mate, glad to hear everything seems in order now.
Quote