| Home | Articles | Register | Members | Search | Windows 7 Support | Links |
 |
| Thread Tools |
|
Guest
Posts: n/a
Thanked:
|
Hello.
I am trying to figure out an updated 64-bit Windows 7 HPE's random blue screen crashes' dump files (mini, kernel, and small) with WinDbg v6.12.0002.633 AMD64. I am not a developer/programmer to understand the these technical results, but I would like to see if I can get more clues. I understand that they have commands and ways to dig deep like "!analyze -v" command. What else are good to know? I also have weird freezes/hangs as well. Both of these issues can happen even after rebooting and idling before logging in. It can take minutes, hours, days, and weeks to reproduce so it is random. I already tried memtest86s, prime95, KNOPPIX liveCD, etc. for days without any problems. So maybe it is a driver or something? I tried to find the latest drivers from Dell's web site, but they all seem to be updated from 2009. I noticed the problems/symptoms got worse and worse over the last few months. Looking at WhyCrash shows these blue screen dumps: On Tue 9/20/2011 5:58:10 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\092011-17128-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0xD9 (0x1, 0xFFFFFA8008247070, 0xFFFFFA800A1AEDD0, 0x40) Error: LOCKED_PAGES_TRACKER_CORRUPTION 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 the internal locked-page tracking structures have been corrupted. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 9/20/2011 5:58:10 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: vmx86.sys (vmx86+0x508D) Bugcheck code: 0xD9 (0x1, 0xFFFFFA8008247070, 0xFFFFFA800A1AEDD0, 0x40) Error: LOCKED_PAGES_TRACKER_CORRUPTION file path: C:\Windows\system32\drivers\vmx86.sys product: VMware kernel driver company: VMware, Inc. description: VMware kernel driver Bug check description: This indicates that the internal locked-page tracking structures have been corrupted. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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: vmx86.sys (VMware kernel driver, VMware, Inc.). On Tue 9/20/2011 12:59:39 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091911-19718-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0x4E (0x99, 0x5FE52, 0x0, 0x11B5D2) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 9/20/2011 12:59:39 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x4E (0x99, 0x5FE52, 0x0, 0x11B5D2) Error: PFN_LIST_CORRUPT Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 7/15/2011 6:53:37 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071511-39702-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1A (0x41287, 0x12A5678C0, 0x0, 0x0) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 7/12/2011 1:39:46 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071111-37190-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1A (0x403, 0xFFFFF68000141DC0, 0xC9700000A7CD2847, 0xFFFFF6FC8061ADDA) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 7/7/2011 8:57:07 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070711-33602-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1A (0x403, 0xFFFFF68000052B30, 0xA5F00000AAB52867, 0xFFFFF6FC80626652) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/3/2011 1:53:37 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070511-37003-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x109 (0xA3A039D89D1EA667, 0x0, 0x1CCE998271631324, 0x101) Error: CRITICAL_STRUCTURE_CORRUPTION 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 the kernel has detected critical kernel code or data corruption. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 6/23/2011 9:31:31 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\062311-18751-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1A (0x41287, 0x142FE78C0, 0x0, 0x0) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 6/10/2011 8:18:40 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\061011-21465-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1A (0x5003, 0xFFFFF90000812000, 0x4D7F, 0x81B500009AEE) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 6/8/2011 7:47:14 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\060811-20654-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0xDE (0x2, 0xFFFFF8A01935C8F0, 0xFFFFF8A01BC29909, 0x2B2BB8C0) Error: POOL_CORRUPTION_IN_FILE_AREA 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 driver has corrupted pool memory that is used for holding pages destined for disk. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. Here is what I did already so far over the last few months in details: -Ran Prime95's default tests nonstop over the weekend (~63 hours) without any problems. -ran some of dell utility's tests (couldn't leave all overnight due to required medias and interactions; up to SATA HDD test and media drives) -Memtest86+ v4.2 (USB flash) passed without errors with 8 GB of RAM after a whole weekend. Old UPS was beeping when returned though (battery replacement needed). -Memtest86 v4.0 (CD-RW) passed without errors with 8 GB of RAM overnight (almost 16 hours). -tried cleaning old drivers and reinstalling the latest ATI drivers again. -disabled ATI Catalyst AI -resetted ATI driver settings with factory defaults and each section's defaults button. -disabled UAC -uninstalled free partition programs and Zentimo -unplugged headphone cable, network, and all USB devices during six days vacation. No BSoD, but starting to freeze and then hard lock up after logging in. Event logs showed it started three days before my return. -replaced with a new and powerful UPS. -tried a new monitor (Acer instead of Philips). -loaded CMOS/BIOS settings back to defaults (didn't seem to change even after twice)? -enabled Intel SpeedStep and C-State Tech -disabled SAS service. -disabled virtual memory/pagefile -upgraded Realtek audio driver to the latest. -changed power AC cable -uninstalled N360 -no malwares found with the latest Spybot S&D, SuperAntiSpyware, MalwareBytes AntiMalware, The Cleaner v8 portable, LUed N360 v3 and v4, and MRT. -used two different USB keyboards (Acer and Dell) -disconnected UPS' USB cable -ran a disk defragger -ran SmartCTL's long tests for HDD problems (all passed) -Virtual Disk service from manual to started automatic -disable all memory card readers -disable power sleep for USB devices -upgraded DVD burner drive's firmware from 102 to 103. -upgraded Gears driver SYMPTOMS: -almost 17.3 minutes to a over weeks uptimes. Used to be longer like months in the before those short uptimes. -Sometimes blue screens without memory dumps and anything recorded. -Hanging/freezing with spinning mouse cursor (can move, but no click and keyboard reactions [even lights]). Unplugging and reconnecting USB and DVI did not help, but DVI showed a blank screen (still has video signal) -Saw a freeze/lock up with a Windows login screen after a reboot over a weekend. -Freezes, but sometimes come back but still freezes. -Seen this hang problem with old default three 1 GB of RAM, but no blue screens. -Blue screens during usages and idled times (most big programs (Office 2007, VMware Workstation v7.1.x, Mozilla's SeaMonkey v2.0.x, etc. are closed/exited, even after a reboot). -Nothing odd in event logs. -During Memtest86 v4.0 (CD-RW) after almost 16 hours, all keyboard lights were on and not responding. Had to reconnect USB devices (keyboard too) to make it work to reboot. -Most of the times, memory.dmp is created. A few times, they aren't. Thank you in advance.  -- Quote of the Week: "The shadows now so long do grow,... That brambles like tall cedars show,... Molehills seem mountains, and the ant... Appears a monstrous elephant." --Charles Cotton's poem /\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site) / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ / Please nuke ANT if replying by e-mail. If crediting, ( ) then please kindly use Ant nickname and AQFL URL/link. |
|
|
|
|||
|
|
| |
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
On Tue, 20 Sep 2011 15:27:31 -0500, (Ant) wrote:
>Hello. > >I am trying to figure out an updated 64-bit Windows 7 HPE's random blue >screen crashes' dump files (mini, kernel, and small) with WinDbg >v6.12.0002.633 AMD64. I am not a developer/programmer to understand the >these technical results, but I would like to see if I can get more >clues. I understand that they have commands and ways to dig deep like >"!analyze -v" command. What else are good to know? > >I also have weird freezes/hangs as well. Both of these issues can happen >even after rebooting and idling before logging in. It can take minutes, >hours, days, and weeks to reproduce so it is random. I already tried >memtest86s, prime95, KNOPPIX liveCD, etc. for days without any problems. >So maybe it is a driver or something? I tried to find the latest drivers >from Dell's web site, but they all seem to be updated from 2009. I >noticed the problems/symptoms got worse and worse over the last few >months. > > > >Thank you in advance. http://www.nirsoft.net/utils/blue_screen_view.html http://www.nirsoft.net/utils/app_crash_view.html Unk |
|
|
|
|
|||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
Guest
Posts: n/a
Thanked:
|
|
|
|
|
||
|
|
| |
|
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Blue Screens Frequently | cypress209 | Crashes, BSODs and Debugging | 2 | 01-02-2011 02:23 PM |
| Startup Blue Screens | W0LF0S | Windows 7 Support | 1 | 12-22-2010 12:02 AM |
