Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: From Win XP to Win 7 - Same BSOD As Before!

10 Jul 2010   #1
J Spangle

Windows 7
 
 
From Win XP to Win 7 - Same BSOD As Before!

Can anyone help me analyze the attached minidump?

I used to get a BSOD on my old Win XP machine that I could not resolve (I seem to be no use at analyzing minidumps). Now I've bought a new Win 7 machine I thought all my troubles will be over but no, they're back!

I must have a piece of software installed on both machines that is causing it but I have no idea what. All I have on my new machine is stuff I really need for work so I'm kind of bummed.

The crash usually comes when the machine has been on for 6 -7 hours or more. The machine becomes unresponsive at first, the fan whirs like crazy. Some infinite loop eating resources is suggested but I see no process eating memory or CPU.

My old machine was a Dell D630, new one is a HP DM4 (6GB ram, i5 processor).

Thank you thank you if you can help!


My System SpecsSystem Spec
.
10 Jul 2010   #2
J Spangle

Windows 7
 
 
Should have added...

I have done a full virus scan (different av products on each machine) and found no virus.
My System SpecsSystem Spec
10 Jul 2010   #3
Tews

64-bit Windows 8.1 Pro
 
 

My System SpecsSystem Spec
.

10 Jul 2010   #4
J Spangle

Windows 7
 
 
Okay...

Sticking to the rules, the attachment is now a zip file.

To recap, the BSOD occurs after the machine has been running for several hours (e.g. I will find the crash in the morning if the machine is left on overnight) and there is no obvious condition that precedes the crash, other than slow response. No high memory usage, no high CPU usage.

On a couple of occasions on the XP machine, Bluetooth manager and ZoneAlarm reported their own internal errors, but this was not repeatable, and has not yet occured on the Win 7 machine.

Generally speaking I will get either a full shutdown, or the screen is blank (no UI at all) and does not wake up ... when this happens, the fan whirs like crazy to cool the processor.

Any help gratefully received.
My System SpecsSystem Spec
10 Jul 2010   #5
Tews

64-bit Windows 8.1 Pro
 
 

Your .dmp file is reporting a fault in ntkrnlmp.exe with a bugcheck of 7F, 8.....

0x00000008, or Double Fault, is when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. This is almost always caused by hardware problems.

Stop 0x7F usually occurs after the installation of faulty or mismatched hardware (especially memory) or in the event that installed hardware fails. If hardware was recently added to the system, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner, to determine which hardware component has failed. For details on these procedures, see the owners manual for your computer. Check that all the adapter cards in the computer, including memory modules, are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Be sure to wipe the cleaned contacts off, removing all cleaning debris, before reinstalling the adapter card into the computer. If compressed air is available, use it to clear out the adapter card slot.

Make sure that your ram modules are matching and is supported by your motherboard..

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.


Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 6f8, fffff80002c93e58}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002c93e58

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02cc9032 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

---------
My System SpecsSystem Spec
10 Jul 2010   #6
J Spangle

Windows 7
 
 
Oh boy, but it's a new machine

Could it also be a device connected to the machine? It's a laptop and I have external monitor, mouse, keyboard, drive connected by USB, and a wireless network printer.

Thank you for your efforts so far!
My System SpecsSystem Spec
Reply

 From Win XP to Win 7 - Same BSOD As Before!




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:06.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App