Without multiple dump files (assuming that some get further through than others) there is no "smoking gun" here so only vague advice about making sure your chipset drivers are up to date (in Safe Mode), as are any other device drivers for additonal hardware you know about. The kernel stack information is virtually empty suggesting the system wasn't stable enough to collect all the data needed for the file. It does look like a corrupt or outdated driver but there's not enough information in a single dmp to get any more clues. Here's the main part of the minidump but most of this you'll have got from BlueScreen. Tried clean boot (unticked everything from the Startup using msconfig) dmp to BlueScreenView where it highlighted ntoskrnl.exe in red (I've also added the dmp file to this thread) PC loads fine in all Safe Mode options, including Safe Mode with networking This happens after the user has logged on to the Desktop. Everything was fine for about 3-4 days when I got a phone call that Windows is crashing with BSOD.
So this is what I did and returned the PC back to my client about a week ago. So, the only way forward was to re-install Windows 7 and all the applications.
About 10 days ago something happened to a Windows 7 PC as all Office programs stopped working - error message was something related to incompatible 32 or 64-bit version, even though it had been working fine for 3-4 years.
0 kommentar(er)
