Windows 7: Issues on startup (occasional BSOD or 'No Input')

scamander · 18 Nov 2011

Hi all,

I seem to get occasional issues on startup. Either I get no input with the PC seemingly doing it's thing but with no image on the monitor or a brief Blue Screen (which has some sort of screendump going on). I might also get a 'loading files' white bar along the bottom of the screen leading onto Startup Repair.

I've tried to attach the perfmon/report but it keeps saying "invalid file"? Even though I'm saving it as an HTML. Any ideas?? I'll give some info on here:

Warnings
Missing Events in Event Log
Investigate why 21% (4,571) events were lost during data collection. The settings for Event Tracing for Windows (ETW) maximum buffers and buffer size may not be optimal depending on which data sets are being collected.

The Security Center is unable to identify an active anti-virus application. Either there is no anti-virus product installed or it is not recognized.
(odd as I have MSE and this works fine - though if I have noticed that startup issues are often followed with a request to update my MSE antivirus). Perhaps this triggers or is a link in some way?

Basic System Checks
(all passed)

Security Information
There's a reddish highlight on this one
root\SecurityCenter:SELECT * FROM AntiVirusProduct

I can access any other info as needed - if it is not possible to attach the report.

Other info as requested
I have Windows 7 (64 bit) and it's OEM. Six months or so I had to have Windows re-installed (by a PC repair shop) as I was having lots of issues and apparently Windows was really corrupted).

From what little I can deduce it seems there are issues with Windows realising I have MSE - although I could be wrong.

Any ideas or opinions gladly appreciated.

FredeGail · 18 Nov 2011

Hello Scamander and welcome!

- Possible memory corruption or driver as UNEXPECTED_KERNEL_MODE_TRAP often are caused by those. Our first step would be checking your sticks, one thing at a time as people used to say.

Follow these instructions.

RAM - Test with Memtest86+

Pay extra attention to part 3.

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff880012b1bff

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ed41e9 to fffff80002ed4c40

STACK_TEXT:  
fffff880`009ecca8 fffff800`02ed41e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eccb0 fffff800`02ed26b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ecdf0 fffff880`012b1bff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`00000060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCheckAttributeRecord+0x2f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ed26b2 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:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

Fred.

scamander · 19 Nov 2011

cheers Fred - will see if I can do this - at the moment it's not picking the USB up on startup, so I'm going to access BIOS - is it a specific key to tap to access this on startup or does it vary?

Thanks again. Today, for example, startup repair did it's thing again - seems 1 out of 3 times Windows Repair kicks in during startup - though it never finds a problem.

FredeGail · 19 Nov 2011

Quote: Originally Posted by scamander

cheers Fred - will see if I can do this - at the moment it's not picking the USB up on startup, so I'm going to access BIOS - is it a specific key to tap to access this on startup or does it vary?

Thanks again. Today, for example, startup repair did it's thing again - seems 1 out of 3 times Windows Repair kicks in during startup - though it never finds a problem.

You're welcome!

Try TAB, DELETE, F12 or read in your motherboard manufacture manual.

Fred.

scamander · 25 Nov 2011

Hi Fred,

Ran this and there were no errors. However, I went through my startup applications and stripped them back. I then had no issues with startup repair appearing.

That was until this morning (I ran the test thereafter). Interestingly the involvement of MSE was further suggested as when the PC did load up I had Security Control notifications that I needed to update MSE.

I've suspected that MSE updates is somehow causing something to trip Windows Repair. Thoughts on this??

Influx · 25 Nov 2011

I think so, MsMpEng.exe is associated with MSE.

Windows 7: Issues on startup (occasional BSOD or 'No Input')

Issues on startup (occasional BSOD or 'No Input') problems?