(0x0000007e) followed by restart?

I got another blue screen error while booting in safe boot, it's frustrating.
If I install Vista or XP will i continue to have these problems?

if XP or vista won't have this problem, should I create a new partition when i install or upgrade?


Since the problem follows me when i format Windows 7, is the problem in my partition or the computer it self? I could delete the partition and re-insall.

Upload your latest dump and let's see what it tells us.

Win 7 is a more intense user of RAM and other components that are Vista and XP. In other words, Win 7 stresses a system more. Thus XP may not trigger a BSOD where Win 7 will if there is a wink link in the system.

Let's test your RAM with Memtest. Read the following tutorial and run Memtest for at least 7 passes. This will take 6-8 hours.

RAM - Test with Memtest86+

Don't forget to upload that latest dump.

I have seen this happen before where the system was reporting the amount of RAM incorrectly and there were no crashes. This does not mean there couldn't be a relationship here. Run Memtest and let's see what shows up.

The dump indicates a hardware problem.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a86e50
Debug session time: Sun Nov  7 08:51:47.031 2010 (GMT-5)
System Uptime: 0 days 0:00:10.078
Loading Kernel Symbols
..............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5100, fffff6fc40022480, 10, 4e}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+675 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fc40022480
Arg3: 0000000000000010
Arg4: 000000000000004e

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


BUGCHECK_STR:  0x1a_5100

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028c7385 to fffff8000281d652

STACK_TEXT:  
fffff800`03be4c98 fffff800`028c7385 : 00000000`ffffffed 00000006`4881424d fffff800`02a41c40 00000000`00000001 : hal!HalProcessorIdle+0x2
fffff800`03be4ca0 fffff800`028c1ebc : fffff800`02a33e80 fffff800`02a41c40 00000000`00000000 fffff880`00e14f44 : nt!PoIdle+0x675
fffff800`03be4d80 00000000`00000000 : fffff800`03be5000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PoIdle+675
fffff800`028c7385 e9a1fdffff      jmp     nt!PoIdle+0x41b (fffff800`028c712b)

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+675

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_5100_nt!PoIdle+675

BUCKET_ID:  X64_0x1a_5100_nt!PoIdle+675

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

Thank you for the update. I am glad to hear that you have not had a further crash. It is not unusual for reseating the RAM to eliminate a problem. Good job! Please update us again in a couple of days. If your system is still running smoothly, we will ask the moderators to mark this thread as solved.