Debug Files Please

thomamon · 05 Jun 2010

richc46 said:

Your family, now. We stick together.

Thanks!

I just got the message "Windows Resource Protection did not find any integrity violations.

So that's done and its set not to automatically reboot anymore.

richc46 · 05 Jun 2010

Stop the restart and then we see what happens. Just use normally, at that juncture.

thomamon · 05 Jun 2010

richc46 said:

Stop the restart and then we see what happens. Just use normally, at that juncture.

Thanks! Will keep you updated.

richc46 · 05 Jun 2010

Can be hardware, RAM, overheating, etc.

Since you have a mini dmp. I will contact our expert. I have contacted one of our best people in BSOD, he will read your mini dmp report and get back to you.

Jonathan_King · 05 Jun 2010

Some of the dmps point to memory_corruption.

Wikipedia said:

Memory corruption happens when the contents of a memory location are unintentionally modified due to programming errors. When the corrupted memory contents are used later in the computer program, it leads either to program crash or to strange and bizarre program behavior.

What that article didn't mention was that it can also be caused by bad RAM.

I know you tested RAM already, but please make sure you did it with Memtest86, and run for at least 5 or 6 passes.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Check your temperatures as well, during heavy usage, with Speedfan.

Some of the dmps point to your hard drive. Please run a test with one of these diagnostics and let us know the result: HD Diagnostic

One of the possibilities is a bad driver as well. Since the dmps don't say which one, we can either guess, or run driver verifier.

If I had to guess about a bad driver, I would guess one of these old ones. Please update their respective programs:

Code:

PxHlpa64.sys Fri Feb 02 16:24:22 2007- CD ROM driver
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008- related to your Balckberry software

Why don't you just start with the hardware tests and updating the old drivers. Upload any new dmps, and we'll go from there.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 07:53:54.026 2010 (GMT-4)
System Uptime: 0 days 19:45:45.680
BugCheck 7A, {fffff6fc40009860, ffffffffc000000e, 7a52860, fffff8800130c69c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 19:05:14.317 2010 (GMT-4)
System Uptime: 0 days 14:01:40.956
BugCheck 7A, {fffff6fc400097a0, ffffffffc000000e, 11743f860, fffff880012f402c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 19:49:29.442 2010 (GMT-4)
System Uptime: 0 days 4:21:46.081
BugCheck F4, {3, fffffa80052f34a0, fffffa80052f3780, fffff80002fdf540}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 19:49:29.442 2010 (GMT-4)
System Uptime: 0 days 4:21:46.081
BugCheck F4, {3, fffffa80052f34a0, fffffa80052f3780, fffff80002fdf540}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 19:05:14.317 2010 (GMT-4)
System Uptime: 0 days 14:01:40.956
BugCheck 7A, {fffff6fc400097a0, ffffffffc000000e, 11743f860, fffff880012f402c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 07:53:54.026 2010 (GMT-4)
System Uptime: 0 days 19:45:45.680
BugCheck 7A, {fffff6fc40009860, ffffffffc000000e, 7a52860, fffff8800130c69c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 08:01:43.275 2010 (GMT-4)
System Uptime: 0 days 0:06:48.055
BugCheck F4, {3, fffffa80061c4b30, fffffa80061c4e10, fffff80002d85540}
Probably caused by : hardware_disk
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 13:23:50.431 2010 (GMT-4)
System Uptime: 0 days 1:18:14.070
BugCheck F4, {3, fffffa8005a9eb30, fffffa8005a9ee10, fffff80002fe1540}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR_C00000C0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 13:37:50.046 2010 (GMT-4)
System Uptime: 0 days 0:12:46.560
BugCheck F4, {3, fffffa8005a83600, fffffa8005a838e0, fffff80002fc8540}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:17:37.236 2010 (GMT-4)
System Uptime: 0 days 0:11:52.015
BugCheck F4, {3, fffffa800534ab30, fffffa800534ae10, fffff80002d83540}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 07:03:32.859 2010 (GMT-4)
System Uptime: 13 days 22:29:16.073
BugCheck 7A, {fffff6fc50045600, ffffffffc000000e, 74fb9880, fffff8a008ac0bc8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c4e )
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  OUTLOOK.EXE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:01:40.238 2010 (GMT-4)
System Uptime: 0 days 3:56:55.017
BugCheck F4, {3, fffffa80050d3b30, fffffa80050d3e10, fffff80002de2540}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

richc46 · 05 Jun 2010

When you download memtest86, be sure to get the one compatble with 64 bit. I think that is what you have.

Jonathan_King · 05 Jun 2010

Yep, he has 64-bit. Memtest does not come in 64 and 32 bit flavor. Here is a direct link to the download: http://memtest.org/download/4.10/mem...+-4.10.iso.zip

richc46 · 05 Jun 2010

Thanks Jon, I knew there was the old and now the new version with the + .

thomamon · 06 Jun 2010

Just a small update, since I have disabled the automatic reboot, it has not rebooted.

Jonathan_King said:

Some of the dmps point to memory_corruption.

Wikipedia said:

Memory corruption happens when the contents of a memory location are unintentionally modified due to programming errors. When the corrupted memory contents are used later in the computer program, it leads either to program crash or to strange and bizarre program behavior.

What that article didn't mention was that it can also be caused by bad RAM.

I know you tested RAM already, but please make sure you did it with Memtest86, and run for at least 5 or 6 passes.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Check your temperatures as well, during heavy usage, with Speedfan.

I used memtest86, I ran it for 9 passes since I did it over night.

I am going to install speed fan right now to keep an eye on that.

Jonathan_King said:

Some of the dmps point to your hard drive. Please run a test with one of these diagnostics and let us know the result: HD Diagnostic

Will do so right now!

Jonathan_King said:

One of the possibilities is a bad driver as well. Since the dmps don't say which one, we can either guess, or run driver verifier.

If I had to guess about a bad driver, I would guess one of these old ones. Please update their respective programs:

Code:

PxHlpa64.sys Fri Feb 02 16:24:22 2007- CD ROM driver
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008- related to your Balckberry software

Why don't you just start with the hardware tests and updating the old drivers. Upload any new dmps, and we'll go from there.

Will I still get dmps if it doesn't reboot? Will start ASAP!

Thanks

richc46 · 06 Jun 2010

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.