Solved Temporary Profile Problem

[thejman129]

Ok, my pc has been working perfectly fine latlely. No shuttering or hangs. No problems what so ever. Until...

I bought the new Kings of Leon CD (deluxe edition, woot) and started to import it to iTunes. It gets to about song three, and then everything freezes up for a sec, then BSOD (FATALITY).

So as my pc is rebooting, im thinking standard procedures should clean this up. Probably a problem with iTunes. Low and behold, when I log in, the Temporary Profile is loaded. Windows proceeds to say logging out, then in, should fix the problem. No cigar.

I turned to the Google, and tried all of the "non-hazardous" solutions. Safe mode, adding a password, creating alternate user profiles, to no avail. From what I've read, it's either a problem with my user registry files, or iTunes.

Now, I know alot about computers, but the registry is just something I don't like to f**k with. Would anyone with a little more experience like to lend a hand? I'd rather not make things worse by flailing around in the OS's sensitive areas.

-TheJMan129

 

[thejman129]

Heres the BSOD Dump, but I cant get a profile report seeing as I'm in a temp.

 

[zigzag3143]

Heres the BSOD Dump, but I cant get a profile report seeing as I'm in a temp.

These were caused by mmemory corruption. I would

1-run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-Run a system file check
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S


Let us know if you need help


Ken J

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\101910-19936-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c0f000 PsLoadedModuleList = 0x82d57810
Debug session time: Tue Oct 19 20:10:02.825 2010 (GMT-4)
System Uptime: 0 days 6:06:38.947
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c08026b0
Arg3: 0000ffff
Arg4: 00000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82cc23fe to 82cc8b1d

STACK_TEXT:  
9e44bb40 82cc23fe 668e0002 66a5dfff 86eb9d48 nt!MiDeleteVirtualAddresses+0x41a
9e44bc10 82cb41a4 86e8f030 86e94318 86e8f030 nt!MiRemoveMappedView+0x325
9e44bc40 82e57d22 bbd743b3 86eb9d48 000000ff nt!MmCleanProcessAddressSpace+0x198
9e44bcb4 82e8c151 00000000 875d5d28 00000001 nt!PspExitThread+0x683
9e44bccc 82cb7123 875d5d28 9e44bcf8 9e44bd04 nt!PsExitSpecialApc+0x22
9e44bd1c 82c524e4 00000001 00000000 9e44bd34 nt!KiDeliverApc+0x28b
9e44bd1c 76f664f4 00000001 00000000 9e44bd34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
0331c1e4 00000000 00000000 00000000 00000000 0x76f664f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteVirtualAddresses+41a
82cc8b1d cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+41a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a

BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a

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

 

[thejman129]

It was bad memory if I recall. I apologize for never having confirmed my findings. I do appreciate the help though!