* Desktop, Windows 7 Home, 2 years old. AMD Athlon II processor
* When booting, the computer will crash with a Blue Screen of Death anywhere from instantly to around 4 minutes of time being up.
* No applications are being used when it crashes. Just letting it reboot and sit with out touching it, will still result in the crash with in a couple of minutes.
*The Bug Check codes (BSOD) in the dump files appear to vary from crash to crash. I have all the .dmp files in case they are needed
*Safe mode is stable and stays up
*This does not appear to be Malware related as I was helped in the other forum in this thread to clean any possible issues and none were found that could relate to an issue like this http://forums.whatthetech.com/index.php?sh…125209&st=0
*A clean boot did not resolve the problem
*A "system restore" to a date before the problem was encountered did not resolve the problem
I am wondering if you have any suggestions before I try a full system recovery which I believe will place the computer back in its original state when I purchased it.
Hi Maldini,
1 Its great news that patndoris have determined that your computer seems to be clear of infections, so that's one area that we can eliminate from our diagnostic prcedures.
I think the key to the issue may be found in that safe mode with networking works fine with no blue screen, but as soon as you boot into normal mode a crash almost always follows within a few minutes.
2 We can deduce therefore that something that is loading in normal mode (but not in safe mode) may be at the heart of the problem.
3 It may of course be necessary in the final analysis to restore your computer to its out of the box or "factory" state, so the fact that your back ups are 100% accurate, up to date, comprehensive, and reproducible is good news. To be on the safe side double check them….and then keep an extra copy safe offsite on removable media (an external USB hard drive is good)
4 before we consider the severe measure of a "factory restore" lets see if we can help you zero in on the part of the starting and early running of your computer that is causing the problem.
5 You will need paper and pencil to help keep track of the items we are going to disable (sounds old fashioned I know but it does simplify things!)
6 If you boot into Safe Mode with Networking? and it solves the problem, then something is starting at boot up that is causing the problem. We need to zero in on the culprit!
Advanced startup options - XP
Advanced startup options - Vista
Advanced startup options - Windows 7
Use msconfig to determine what is causing the problem
Click on Start then Run, type msconfig and press Enter.
Click on the Startup tab, record on your sheet of paper, what is currently starting, then click the Disable All button.
Reboot and see if it runs better.
If yes then use msconfig to enable several items at a time (recording each one on your sheet of paper) till you find the culprit. (you will need to reboot each time…. its tedious and time consuming but well worth trying!)
If no, start msconfig and click on the Services tab.
Check/Tick the Hide All Microsoft Services box, record what is currently starting then click the Disable All button.
Again, do a boot into normal mode, see if it runs OK and without crashing
If yes then use msconfig to enable services (recording them on your paper as you go) till you find the culprit.
Once you've found the culprit, uninstall it or find out how to eliminate it from your system. Simply disabling it in msconfig is a temporary fix at best.
Enable everything else you disabled.
(Thanks to Rich for the basic canned)
Let us know how you go.
If you think that the foregoing steps are a little too much work then its worth going here:
http://www.resplendence.com/downloads
scroll down about half way down the page til your arrive at:
"Who Crashed" v 4.01 Crash Analysis tool and download the free Home Edition, run it and follow the directions… if your are stuck then copy and paste the output in to your reply
Regards
paws
Hi Paws,
Thank you so much for the directions. I am going to start focusing in on what startup piece is causing me the problems.
I will let you know how it goes.
Shoot. It was neither the startup or the services. With both at a disabled all state, the computer still crashes.
I set my bios back to a default state and that also has not fixed the problem.
Am I at the "perform a system recovery" part now?
I have not yet updated the two drivers it suggested. Please let me know if you think that is safe to try
============================================
Crash Dump Analysis
——————————————————————————–
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 1/6/2013 9:54:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-16567-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D7B220, 0xFFFFF8800592AEE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 9:52:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-20186-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F43D03E)
Bugcheck code: 0x3D (0xFFFFF88002F1AD50, 0x0, 0x0, 0xFFFFF8800F43D03E)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 197.39
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 197.39
Bug check description: This bug check appears very infrequently.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 197.39 , NVIDIA Corporation).
Google query: NVIDIA Corporation INTERRUPT_EXCEPTION_NOT_HANDLED
On Sun 1/6/2013 9:41:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-19983-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F45D03E)
Bugcheck code: 0x3D (0xFFFFF88002F1AD50, 0x0, 0x0, 0xFFFFF8800F45D03E)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 197.39
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 197.39
Bug check description: This bug check appears very infrequently.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 197.39 , NVIDIA Corporation).
Google query: NVIDIA Corporation INTERRUPT_EXCEPTION_NOT_HANDLED
On Sun 1/6/2013 9:39:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-20498-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F65303E)
Bugcheck code: 0x3D (0xFFFFF8800311AD50, 0x0, 0x0, 0xFFFFF8800F65303E)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 197.39
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 197.39
Bug check description: This bug check appears very infrequently.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 197.39 , NVIDIA Corporation).
Google query: NVIDIA Corporation INTERRUPT_EXCEPTION_NOT_HANDLED
On Sun 1/6/2013 9:34:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-21060-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002A94310)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 9:32:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-20295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x20, 0x2, 0x0, 0xFFFFF80002B5B22C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 9:30:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002DBDFDE, 0xFFFFF88007421160, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 9:27:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-20139-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8005575B50, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 9:21:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-16894-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2BA74)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880011A2A74)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 1/6/2013 4:20:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-18423-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002DEC38C, 0xFFFFF88006824EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/6/2013 4:15:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-39842-01.dmp
This was probably caused by the following module: nvstor64.sys (0xFFFFF88000DA88A9)
Bugcheck code: 0xD1 (0xC2, 0x2, 0x0, 0xFFFFF88000DA88A9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvstor64.sys
product: NVIDIA nForce™ SATA Driver
company: NVIDIA Corporation
description: NVIDIA® nForce™ Sata Performance Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvstor64.sys (NVIDIA® nForce™ Sata Performance Driver, NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 3/7/2011 11:19:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030711-25989-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C08617, 0xFFFFF88008D487C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/23/2011 11:49:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022311-22557-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 2/17/2011 11:17:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021711-19593-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002FFB557)
Bugcheck code: 0xA (0xFFFFFA80F330F468, 0x2, 0x0, 0xFFFFF80002FFB557)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
——————————————————————————–
Conclusion
——————————————————————————–
14 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 197.39 , NVIDIA Corporation)
nvstor64.sys (NVIDIA® nForce™ Sata Performance Driver, NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Hi maldini,
Yep you now have very little to lose, if your back up is sound and your next step is to restore to factory then before you do this try and update the drivers, at the same time update all your drivers and see if this helps
Regards
paws
