I think that for some reason we are misunderstanding each other which will not anyhow lead us to any solution to the issue.
I am stopping posting in your thread, but I will give the other members of the forum a call to post in your thread.
Ok, that is fine. I appreciate that and all your help thus far.
But for your understanding, I believe the original problem that I posted about was addressed by the re-install of Windows 7 (minidumps were created). My impression is that this Event 41 w/o the minidump must be a new issue, so it seems like a new thread would have been warranted.
Thanks
Last edited by jmom; 08 Jun 2015 at 07:43.
Hello jmom look I am not great expert but in the last dump there is something amiss with the touchpad system and I am just wondering if you can get in and make sure the latest driver for it is installed.
As I said I ma not that experienced as some but take a look at this one.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 00000000000000d0, Handle value being referenced. Arg3: fffffa80074be2b0, Address of the current process. Arg4: fffff88003eba3b9, Address inside the driver that is performing the incorrect reference. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_f6 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: SynTPEnh.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff80002f164ec to fffff80002a83a40 STACK_TEXT: fffff880`046141b8 fffff800`02f164ec : 00000000`000000c4 00000000`000000f6 00000000`000000d0 fffffa80`074be2b0 : nt!KeBugCheckEx fffff880`046141c0 fffff800`02f2baa4 : 00000000`000000d0 fffffa80`074be2b0 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`04614200 fffff800`02cde950 : fffff800`02d78cf0 fffff880`04614430 fffffa80`03d03a00 00000000`20040000 : nt!VfCheckUserHandle+0x1b4 fffff880`046142e0 fffff800`02d5c9f5 : 00000000`00000000 fffffa80`10000000 fffffa80`03d03a40 fffff800`02d5c900 : nt! ?? ::NNGAKEGL::`string'+0x1a10e fffff880`046143b0 fffff800`02f2b838 : 00000000`00000000 00000000`00000018 fffff880`03ef37c0 fffff800`02f2337c : nt!ObReferenceObjectByHandle+0x25 fffff880`04614400 fffff880`03eba3b9 : fffff980`0c444fc8 00000000`20040000 00000000`20040000 00000000`00000003 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`04614450 fffff980`0c444fc8 : 00000000`20040000 00000000`20040000 00000000`00000003 fffff980`0c444fd0 : SynTP+0x123b9 fffff880`04614458 00000000`20040000 : 00000000`20040000 00000000`00000003 fffff980`0c444fd0 00000000`00000000 : 0xfffff980`0c444fc8 fffff880`04614460 00000000`20040000 : 00000000`00000003 fffff980`0c444fd0 00000000`00000000 fffff880`04614580 : 0x20040000 fffff880`04614468 00000000`00000003 : fffff980`0c444fd0 00000000`00000000 fffff880`04614580 fffff880`03ed2899 : 0x20040000 fffff880`04614470 fffff980`0c444fd0 : 00000000`00000000 fffff880`04614580 fffff880`03ed2899 fffff880`04614580 : 0x3 fffff880`04614478 00000000`00000000 : fffff880`04614580 fffff880`03ed2899 fffff880`04614580 00000000`20040000 : 0xfffff980`0c444fd0 STACK_COMMAND: kb FOLLOWUP_IP: SynTP+123b9 fffff880`03eba3b9 b90b0004e0 mov ecx,0E004000Bh SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: SynTP+123b9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SynTP IMAGE_NAME: SynTP.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47ec46b4 FAILURE_BUCKET_ID: X64_0xc4_f6_SynTP+123b9 BUCKET_ID: X64_0xc4_f6_SynTP+123b9 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_syntp+123b9 FAILURE_ID_HASH: {a1c75ec5-9c55-6a89-f49f-f12d7ae47561} Followup: MachineOwner ---------
Thanks for taking the time to look :).
I have already fixed that issue a few days ago. So now I'm looking at reboots happening since 5 June (so 6 June and later). Reboots with Event 41 but no minidumps.
Thanks!
Ok jmom mate take a look at this I found on a Google for the error code https://support.microsoft.com/en-us/kb/2028504#method1 it might offer something for you.
Would you please prepare an OS boot disk such as Peppermint3 - Create Live CD/DVD/USB To Use For Emergency Backup - Windows 7 Forums.
Now power down and carefully pull the data cable off of your hard drive. Reboot and tap the HP ESC key to boot the disk, select F9 Boot Menu and select disk to boot.
Now run as much as normal as you can with the boot disk to see if you can replicate the shutdown. If so then you'll know it is most certainly hardware as neither the hard drive nor the OS is connected.
If the problem doesn't replicate then did you wipe the hard drive with at least Diskpart Clean Command before doing the reinstall since boot code can cause such a condition? And looking over the steps for Clean Reinstall Windows 7 how closely did you come to those steps which compile a perfect install with everything that works best for Win7? If you feel that it could have been done better then I will work with you to do a diagnostic install which wipes the drive and then phases the reinstall to isolate the problem by when it occurs.
I have just reread this thread about 3 times and 2+2 is not equaling 4.
I think a great place to start is with a very basic thing.
@jmom
Complete this tutorial by Brink and post it here.
Windows Genuine and Activation Issue Posting Instructions
If things are okay there (in the log) I would suggest going to Greg's post 26. He can give you guidance to get those things completed.
Thanks for the multiple replies! I will do as suggested and post here (when I get home from work later this evening).
Note that this is a laptop, so if I get to post #26, then I'm not sure about pulling the cable for the hard drive?? I can cross that bridge though if and when I get there.
[BTW, I'm so curious why you say 2+2 is not equaling 4 :). Wondering what doesn't make sense in the thread! :)]
From post #1
I have an HP G60-553NR Notebook computer running Windows 7 Home Edition 64 bit, purchased in 2007.From post #3Note that I had to use the HP F11 recovery option (using Recovery partition) as I have no recovery disks
From post #5Given the laptop is back at the factory state, and is still rebooting, does this lead towards a hardware issue?
Windows 7 didn't even come out until 2009.Because after loading SP1, the reboots still were occurring. I was able to get the recovery disks, so reinstalled Windows from the disks since I thought it may be more reliable than the recovery partition.
A (what ever recovery partition or drive will not install Windows 7). They will most likely not repair a proper install Windows 7 OEM or Retail version.
Their are more things. Those are just a few.
We need to know where you got Windows 7 from and how it was installed and activated.
Post the log as per the tutorial so we can see exactly what you have installed.
I see. :)
Thanks - the year was just a general recollection about when I thought we gave my mother-in-law the laptop (present from all her kids) --- I didn't go back to look at the actual year - that was pointed out to me :).
Regarding the series of Windows 7 installations:
1. Her laptop has a Recovery partition, so I first tried that and ran into issues. Additionally, I didn't think she had recovery disks as HP info says they don't provide them if there is a Recovery partition. Lo and behold she found her packet of info for the laptop and there were recovery disks with my handwriting! So apparently I created the recovery disks when we gave her the laptop umpteen years ago.
2. So I did a reinstallation with the actual recovery disks, thinking the Recovery partition may have been corrupted (as I'd run into many issues). I still had the reboot issue.
3. Per suggestion from Arc here, I got a Windows 7 Home Premium iso (non-OEM version) and burned a disk and installed from that - this went fairly smoothly but I still had reboot issues. I used the Windows product key from the bottom of the laptop and activated over the phone/smartphone. It said it was successful.
So that's the backstory!
I will get back to you with the additional information in a few hours.
Thanks!
Quote