BSOD - Random igdkmd64.sys 0x0000007f on HP DM1-4015TU

Hi Guys,

I am wondering if someone could have a quick look at the attached files relating to random BSOD i am getting on a 3 month old HP DM1-4015TU - Core i3 / Intel HD3000, 4GB Ram, 640 GB disk :-

Attachment 207011

Bluescreen view is reporting it as the Intel Graphics driver, idgkmd64.sys but I dont think this is the root cause. I have reloaded the supported driver from HP's site and the crashes seem to be the same each time, just getting more frequent and with no pattern appear to be random ( can occur whilst doing anything ). I have run HP hardware tests on machine and the ram is as supplied ( 1x4GB simm ).

The machine is used for mainly email, skype, office productivty etc..

I trust the above and attached is sufficient for an initial look. Please let me know if you need more information.

Thanks in advance,

Kind regards,

Simon

Attachment 207012

Virtually all of these were related to your video driver, but that could mean the driver, heat, power, the video card itself, etc.

It seems like software passing bad information into memory.

If it is still under warranty why not have HP fix it?

Hi,

Thanks for the quick response..

Yes, I agree the response to date has been to re install the graphics drivers from the HP site - Intel version 8.15.10.2476 ( current on Intel site 8.15.10.2656 ) and to run some tests on the system for graphics, ram etc.. Which did not turn up anything from a Windows or BIOS perspective.

The suggestion was to see how it ran.. However it is getting worse not better and they pointed more to another software coruption issue rather than the graphics driver. I am not getting video corruption on the screen or anything I can consistently repeat to cause the BSOD.

I can push for a replacement or refund, but I am not convinced either that its a hardware issue right now..

Many thanks,

Simon

Simon NZ said:

Hi,

Thanks for the quick response..

Yes, I agree the response to date has been to re install the graphics drivers from the HP site - Intel version 8.15.10.2476 ( current on Intel site 8.15.10.2656 ) and to run some tests on the system for graphics, ram etc.. Which did not turn up anything from a Windows or BIOS perspective.

The suggestion was to see how it ran.. However it is getting worse not better and they pointed more to another software coruption issue rather than the graphics driver. I am not getting video corruption on the screen or anything I can consistently repeat to cause the BSOD.

I can push for a replacement or refund, but I am not convinced either that its a hardware issue right now..

Many thanks,

Simon

The crashes all point to software and you could always run verifier to pin down which driver is the underlying cause

Hi,

Many thanks will give verifier a go, but with the usual pre-cautions etc..

Kind regards,

Simon

Re: Verifier..

Created a system restore point..

Then ran verifier will all loaded driver selected, as all of the drivers are signed in the system..

Rebooted and the system booted but crashed with:

BSOD STOP 0xC4 in tcpipreg.sys

Which appears to be know issue:

STOP 0xC4 may occur in tcpipreg.sys following a reboot after Driver Verifier is enabled on Windows 7 SP1 or Windows Server 2008 R2 SP1

So not much further forward..

Any further suggestions.. ?

Simon NZ said:

Re: Verifier..

Created a system restore point..

Then ran verifier will all loaded driver selected, as all of the drivers are signed in the system..

Rebooted and the system booted but crashed with:

BSOD STOP 0xC4 in tcpipreg.sys

Which appears to be know issue:

STOP 0xC4 may occur in tcpipreg.sys following a reboot after Driver Verifier is enabled on Windows 7 SP1 or Windows Server 2008 R2 SP1

So not much further forward..

Any further suggestions.. ?

Obviously I would have to look at that DMP because it isnt one of the ones you uploaded.

Yours do not point to tcpipreg.sys

Hence the link isnt relevant

Hi,

Please find attached the additional DMP files since the verifier was turned on and then off as below:

1/ Same BSOD today when using the system... Verifier has been turned off...

041412-27783-01.dmp 14/04/2012 11:35:45 a.m. UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 fffff880`04d3eff7 igdkmd64.sys igdkmd64.sys+f8ff7 x64 C:\Windows\Minidump\041412-27783-01.dmp 4 15 7601

2/ BSOD from Verifier

041312-34944-01.dmp 13/04/2012 9:21:28 p.m. DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 tcpipreg.sys tcpipreg.sys+35a5 x64 C:\Windows\Minidump\041312-34944-01.dmp 4 15 7601

3/ BSOD from Verifier

041312-33181-01.dmp 13/04/2012 9:19:15 p.m. DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 tcpipreg.sys tcpipreg.sys+35a5 x64 C:\Windows\Minidump\041312-33181-01.dmp 4 15 7601

Thanks again for your assistance,

Kind regards,

Simon

Attachment 207156

May be a false positive.

From your link

This problem has only been observed after the machine's TCP/IP configuration has been changed from a static IP address to a dynamic address with DHCP, which leaves an empty value for the IPAddress registry key for the network interface.

If you havent done that chances are verifier is causing it. It seems rather odd that all the previous logs say video and then when you turn verifier on it becomes tcipreg.sys.

Try these to verify that tcpipreg.sys may be a false positive. The stack backtrace doesnt mention tcpipreg.sys at all

0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

• A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
• A hardware problem.

Hi,

Yes its very strange.. I might try turning verifier on again.. When turned on, last time the machine booted and I logged in, but did not get to the desktop. It did not present a BSOD screen simply hung just before presenting the desktop..

It think it might be a false positive, but I am really keen to get to the bottom of this..

Many thanks,

Simon