|
|
|
#1
|
||||
|
||||
|
computer has rebooted from a bugcheck 0x0000001A
Seems a commom problem http://www.google.ca/#hl=en&sclient=...w=1366&bih=609 I thought at first it must be a hardware problem, as is usually the case when computer just shuts down on its own. Its one of these cases when you dont know where to start I will have to look at the mindump, Anybody had experience with it Last edited by johnrobert; 03-11-2012 at 05:06 PM. |
|
#2
|
|||
|
|||
|
Hi
The 0x00000022 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer. The best advice would be to restore the computer to an earlier time if the computer does still boot. I hope this helps or at least points you in the right direction. |
|
#3
|
||||
|
||||
|
I copied the mindump folder C:\windows\minidump
How can I view the mini dump file to find the problem Looks not so easy. Last edited by johnrobert; 03-16-2012 at 11:05 PM. |
|
#4
|
|||
|
|||
|
Blue screen view should help. http://www.nirsoft.net/utils/blue_screen_view.html
|
|
#5
|
|||
|
|||
|
Quote:
__________________
Hartland Computer Services, Lexington, Ky 40515 (859) 536-4107 www.CrosbyDrive.com |
|
#6
|
||||
|
||||
|
I get about 40 minidumps of MEMORY_MANAGEMENT all with same address
I would guess you are right about it being bad MEMORY Bug check string MEMORY_MANAGEMENT Bug check code 0x0000001a Caused by driver ntoskrnl.exe Caused by address ntoskrnl.exe+705c0 File description NT Kernel & System Crash address ntoskrnl.exe+705c0 |
|
#7
|
|||
|
|||
|
Probably is the RAM, but best to test it either way. Windows 7 has a built in memory tester in the boot menu. I tend to use memtest myself.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|