Debug Files Please

[thomamon]

If you encounter any of the conditions that would normally trigger a dmp.file, it will be generated. The only difference is, now, you will not reboot. Since, you used my suggestion to turn of the automatic reboot, it is possible that you will not encouter any other problems. In the meantime just enjoy.

OK, so I didn't get to run those diagnostics yet because my wife was happy her computer was working, now she just got the BSOD... Not sure if this helps, but here it is below and now she will let me do the other tests that it did it again.

 

[richc46]

Follow this tutorial and you will be helped.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[thomamon]

Follow this tutorial and you will be helped.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

Here you go...

 

[richc46]

Did you also get a stop error? Something like 0000890884x?

 

[thomamon]

Did you also get a stop error? Something like 0000890884x?

It was just what I showed you. However, it just crashed again.

This time I got the BSOD that is attached and a dump file. Then when I restarted it seemed to be different telling me there was a problem and a dump file. I have attached the latest BSOD and the dump file for what just happened.

 

[richc46]

Dont have time right now to study all the files. But the last one clearly shows hardware disk

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_060610-21528-01[1].zip\060610-21528-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Sun Jun  6 15:11:32.547 2010 (GMT-4)
System Uptime: 0 days 1:10:43.061
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8005b7a760, fffffa8005b7aa40, fffff80002fcd540}
Probably caused by : hardware_disk
Followup: MachineOwner

 

[thomamon]

Does this mean I should order a new hard drive?

Dont have time right now to study all the files. But the last one clearly shows hardware disk

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_060610-21528-01[1].zip\060610-21528-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Sun Jun  6 15:11:32.547 2010 (GMT-4)
System Uptime: 0 days 1:10:43.061
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8005b7a760, fffffa8005b7aa40, fffff80002fcd540}
Probably caused by : hardware_disk
Followup: MachineOwner

 

[richc46]

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

http://www.sevenforums.com/crashes-debugging/63428-chkdsk-errors.html#post566952

The debug tool is good, but not always precise. I can give you the leads then its up to you.
To help you decide about the Hard drive, follow the links

 

[thomamon]

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

http://www.sevenforums.com/crashes-debugging/63428-chkdsk-errors.html#post566952

The debug tool is good, but not always precise. I can give you the leads then its up to you.
To help you decide about the Hard drive, follow the links

In addition, probably, piece meal, I will analyse the other dumps.

Gonna run these tests now... Keep you posted.

Thanks again for your time.

 

[richc46]

And thank your for using the Forum.

 

[thomamon]

And thank your for using the Forum.

I love this forum, and I will spread the word about it and plan on visiting here frequently.

Well, it turns out I may have found the culpret. Running the WD Diagnostics on the first drive I get the screen pasted below. The wired thing is, this is the E: Drive, not the drive where Windows is installed. Can this still be the problem?

Thanks

Edit: Could this also be what causes the kernel 41 error?

 

[thomamon]

In addition, probably, piece meal, I will analyse the other dumps.

What does piece meal mean?

Edit: While running the longer test on the drive the system did a Kernel 41 Reboot... I hope replacing the drive is the issue.

 

[richc46]

In addition, probably, piece meal, I will analyse the other dumps.

What does piece meal mean?

Edit: While running the longer test on the drive the system did a Kernel 41 Reboot... I hope replacing the drive is the issue.

Just means I cannot do it all at once. Ill try for another, right now.

 

[thomamon]

In addition, probably, piece meal, I will analyse the other dumps.

What does piece meal mean?

Edit: While running the longer test on the drive the system did a Kernel 41 Reboot... I hope replacing the drive is the issue.

Just means I cannot do it all at once. Ill try for another, right now.

Oh, no worries. Did you see the above post? The above drive failed the diagnostic test? And that it rebooted kernel 41 while running the more thorough test?

 

[richc46]

Just did two more, here is one; points toward drivers and memory.

After reading most of the dumps. I would say that the reason you are having these problems is due to drivers and/or memory. Based upon one of them the hard drive can also be having problems

I would back up the information on the hard drive just in case.
Download and run memtest86.
Go to the device manager look for any yellow warning stickers,indicating driver problems and make sure that all drivers are up to date.
http://www.geekstogo.com/forum/Guide-to-using-Memtest86-t246994.html
http://xpdrivers.com/index.cfm

  Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_060410-19032-01[1].zip\053010-24133-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Sun May 30 07:03:32.859 2010 (GMT-4)
System Uptime: 13 days 22:29:16.073
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc50045600, ffffffffc000000e, 74fb9880, fffff8a008ac0bc8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c4e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50045600, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000074fb9880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a008ac0bc8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000000e
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  OUTLOOK.EXE
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002b420a8 to fffff80002acd600
STACK_TEXT:  
fffff880`0356b5d8 fffff800`02b420a8 : 00000000`0000007a fffff6fc`50045600 ffffffff`c000000e 00000000`74fb9880 : nt!KeBugCheckEx
fffff880`0356b5e0 fffff800`02abf42b : fffffa80`0653ce90 fffff880`0356b750 fffff800`02c59b40 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`0356b6c0 fffff800`02ae84a4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000001 : nt!MiIssueHardFault+0x28b
fffff880`0356b790 fffff800`02a94562 : 00000000`00000000 0000a0a0`00000080 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`0356b8f0 fffff800`02a6f724 : fffffa80`06901780 fffff8a0`08ac0bc8 fffffa80`043e3ab8 00000000`00000fff : nt! ?? ::FNODOBFM::`string'+0x5ef1
fffff880`0356b940 fffff800`02a6fd69 : 00000000`00000000 00000000`00000000 fffff880`0356bc60 fffffa80`03bde9a0 : nt!MiLockProtoPage+0x118
fffff880`0356b990 fffff800`02db5dc1 : fffff880`00000010 fffffa80`043e3701 fffffa80`043e3720 fffff800`02ad36ef : nt!MiGetWorkingSetInfoList+0x4b1
fffff880`0356ba80 fffff800`02acc853 : 00000000`00000694 fffffa80`06901780 00000000`00000000 00000000`0301e808 : nt!NtQueryVirtualMemory+0x67f
fffff880`0356bb70 00000000`776500ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0301e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776500ea
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`02b420a8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34c4e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e
BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e
Followup: MachineOwner
---------

 

[thomamon]

Well, color me confused...

- The memory passes the MemTest through eight passes, the correct MemTest.
- The Hard Drive fails the test from WD
- It also could be drivers.

I don't know where to go from here. I know it started with the kernel 41 reboot error, I then updated all the drivers I could find to the latest drivers. Since then, it has the BSOD reboots.

So what do you suggest I do from here?

Just did two more, here is one; points toward drivers and memory.

After reading most of the dumps. I would say that the reason you are having these problems is due to drivers and/or memory. Based upon one of them the hard drive can also be having problems

  Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_060410-19032-01[1].zip\053010-24133-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Sun May 30 07:03:32.859 2010 (GMT-4)
System Uptime: 13 days 22:29:16.073
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc50045600, ffffffffc000000e, 74fb9880, fffff8a008ac0bc8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c4e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50045600, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000074fb9880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a008ac0bc8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000000e
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  OUTLOOK.EXE
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002b420a8 to fffff80002acd600
STACK_TEXT:  
fffff880`0356b5d8 fffff800`02b420a8 : 00000000`0000007a fffff6fc`50045600 ffffffff`c000000e 00000000`74fb9880 : nt!KeBugCheckEx
fffff880`0356b5e0 fffff800`02abf42b : fffffa80`0653ce90 fffff880`0356b750 fffff800`02c59b40 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`0356b6c0 fffff800`02ae84a4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000001 : nt!MiIssueHardFault+0x28b
fffff880`0356b790 fffff800`02a94562 : 00000000`00000000 0000a0a0`00000080 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`0356b8f0 fffff800`02a6f724 : fffffa80`06901780 fffff8a0`08ac0bc8 fffffa80`043e3ab8 00000000`00000fff : nt! ?? ::FNODOBFM::`string'+0x5ef1
fffff880`0356b940 fffff800`02a6fd69 : 00000000`00000000 00000000`00000000 fffff880`0356bc60 fffffa80`03bde9a0 : nt!MiLockProtoPage+0x118
fffff880`0356b990 fffff800`02db5dc1 : fffff880`00000010 fffffa80`043e3701 fffffa80`043e3720 fffff800`02ad36ef : nt!MiGetWorkingSetInfoList+0x4b1
fffff880`0356ba80 fffff800`02acc853 : 00000000`00000694 fffffa80`06901780 00000000`00000000 00000000`0301e808 : nt!NtQueryVirtualMemory+0x67f
fffff880`0356bb70 00000000`776500ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0301e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776500ea

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`02b420a8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34c4e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e
BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e
Followup: MachineOwner
---------

 

[richc46]

I would concentrate on the drivers, but that hard drive is porbably ready to go. You can lose everything if not backed up.

The memory is ok
The hard drive is potentially a problem. But not much more you can do than test and if you feel it had it, replace it
Only the drivers remain. Work on that. If you are still not up and running, you have to look into the hard drive. May not help the BSOD, but you cannot work with a hard drive that may go any time

You took the HD test and saw the results, must be looked into.

 

[thomamon]

I would concentrate on the drivers, but that hard drive is porbably ready to go. You can lose everything if not backed up.

The memory is ok
The hard drive is potentially a problem. But not much more you can do than test and if you feel it had it, replace it
Only the drivers remain. Work on that. If you are still not up and running, you have to look into the hard drive. May not help the BSOD, but you cannot work with a hard drive that may go any time

You took the HD test and saw the results, must be looked into.

Running the driver utility right now.

Luckily the drive is just a storage drive and (not the main boot up drive) that is ready to go and is backed up nightly to an external. But we will be replacing it very soon.

 

[thomamon]

So I've run the program and it tells me some of the drivers are out of date.. But here is the thing about this, I've run driver utilities in the past couple weeks and for example, it tells me that the below drivers are out of date. When I tried installing the new drivers that Radar Sync told me were the correct ones, the program told me the drivers I had were newer. I went to intels website to find newer drivers and installed the latest, so why would these still come up as not the latest?

• Intel 4 SEries Chipset PCI Express Root Port -2E21,
• Intel ICH10 Family PCI Express Root Port 1 - 3A40
• Intel ICH10 Family SMBus Controller - 3A30

It also tells me that the INtel ICH10 Family USB Enhanced Controller - 3A3A are out of date.

Also, Realtec PCIe GBE Family Controller is out of date according to this, but I've downloaded the latest from the Gigabyte website.

Same thing witht he ATI High Definition Audio Decice, Downloaded it from ATI Website to make sure I had the latest.

 

[richc46]

Evidentally, the tests that are used to determine the fact that a driver is current or not isn't completly accurate. The only cure is to download from the website, which is the suggested procedure, anyway. Once you have updated all the potentially problemsome drivers from the website, you are done. Even if some test says its not up to date, not much you can do.