Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.
Collaborate in the cloud with Office, Exchange, SharePoint, and Lync
|
|||||||
Collaborate in the cloud with Office, Exchange, SharePoint, and Lync
Minidump decrypted, please help.
|
|
Thread Tools | Search this Thread |
|
#1
10-04-2006
|
|||
|
|||
|
Minidump decrypted, please help.
4 Mini dumps can you please help.
My system keeps rebooting for no reason and I cant figure out the problem. text files attached to account. ==== Opened log file 'c:\debuglog.txt' 1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols 1: kd> .reload;!analyze -v;r:kv;lmnt;.logclose;q Loading Kernel Symbols ........................................................................... ........................................................................... ....................................... Loading User Symbols Loading unloaded module list ..................................... *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffff0, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 9b0c3410, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffffff0 FAULTING_IP: Fastfat+410 9b0c3410 8b4df0 mov ecx,dword ptr [ebp-10h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System LAST_CONTROL_TRANSFER: from 00000000 to 9b0c3410 STACK_TEXT: 00000000 00000000 00000000 00000000 00000000 Fastfat!_SEH_epilog STACK_COMMAND: kb FOLLOWUP_IP: Fastfat+410 9b0c3410 8b4df0 mov ecx,dword ptr [ebp-10h] SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Fastfat IMAGE_NAME: Fastfat.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb7 SYMBOL_NAME: Fastfat+410 FAILURE_BUCKET_ID: 0x50_Fastfat+410 BUCKET_ID: 0x50_Fastfat+410 Followup: MachineOwner --------- ^ Bad register error in '.reload;!analyze -v;r:kv;lmnt;.logclose;q' ======= Dump 2 Opened log file 'c:\debugmini02.txt' 1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols 1: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q Loading Kernel Symbols ........................................................................... ........................................................................... ...................................... Loading User Symbols Loading unloaded module list .................. *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffffc, memory referenced. Arg2: 00000001, value 0 = read operation, 1 = write operation. Arg3: a027e447, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: fffffffc FAULTING_IP: Fastfat!FatDeferredCleanVolume+fc a027e447 834dfcff or dword ptr [ebp-4],0FFFFFFFFh MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System LAST_CONTROL_TRANSFER: from 80537851 to a027e447 STACK_TEXT: bad1bd7c 80537851 8a532288 00000000 8a6bdda8 Fastfat!FatDeferredCleanVolume+0xfc bad1bdac 805ce7d4 8a532288 00000000 00000000 nt!ExpWorkerThread+0xef bad1bddc 805451ce 80537762 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: Fastfat!FatDeferredCleanVolume+fc a027e447 834dfcff or dword ptr [ebp-4],0FFFFFFFFh SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Fastfat IMAGE_NAME: Fastfat.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb7 SYMBOL_NAME: Fastfat!FatDeferredCleanVolume+fc FAILURE_BUCKET_ID: 0x50_W_Fastfat!FatDeferredCleanVolume+fc BUCKET_ID: 0x50_W_Fastfat!FatDeferredCleanVolume+fc Followup: MachineOwner Last edited by topcash; 10-09-2006 at 09:31 AM.. |
|
|
#2
10-05-2006
|
||||
|
||||
|
run memtest 86+ to check your memory. Run for 7 or more passes.
|
|
#3
10-09-2006
|
|||
|
|||
|
Hello and welcome to Techspot.
I have deleted your other thread on this subject. Please don`t open any more thread for this. Thanks. Please attach 5 or 6 of your latest minidumps here. Regards Howard 
|
|
#4
10-09-2006
|
|||
|
|||
|
Here are my most recent dumps. I thought I would just take back the entire computer and the problem would go away. I returned it, got a new computer since my last post, and the blue screens are back. I this may be from my Antivirus, but I could be wrong on that.
Last edited by topcash; 10-09-2006 at 09:50 AM.. |
|
#5
10-09-2006
|
|||
|
|||
|
I think you forgot to attach your minidumps.
Regards Howard 
|
|
|
#7
10-09-2006
|
|||
|
|||
|
All your minidups crash at Fastfat.SYS. This is the Windows Fast FAT File System Driver.
I suggest you run a complete hard drive check as in this thread HERE. If that doesn`t help, then run your hard drive manufacturers disk checking utility on the drive. Let us know the results please. Regards Howard
|
|
#8
02-20-2008
|
|||
|
|||
|
I'm getting a similar BSOD on Vista on a brand new ThinkPad T61. I already had this BSOD on Vista on a ThinkPad T60. It usually happens once a week (sometimes more often).
I opened a support ticket with Microsoft about this but this didn't brought any resolution. I run memtest overnight with 11 successful passes. The last answer I got from them is that it might be a hardware problem. But I'm wondering if I have the same hardware problem on two completely different machines. I bought the T60 a year ago and the T61 last week. Can someone have a look at the attached mini dump? I would really appreciate it. Thanks, KM |
|
#9
02-20-2008
|
||||
|
||||
|
For future needs you need to start your own thread. Two things: Run a harddrive diagnostics and also contact Lenovo. Their T61 is their top of the line models and it is only a week old.
Tell them that your minidump was read and it is a Fast.Fat.sys 0x50 error which is a Windows error. They need to rectify this matter. |
 |
| Similar Topics | ||||
| Topic | Replies | Forum | ||
 New minidump
|
9 | Windows BSOD, Freezing, Restarting Help | ||
|
Minidump
|
14 | Windows BSOD, Freezing, Restarting Help | ||
|
Minidump
|
1 | Windows BSOD, Freezing, Restarting Help | ||
|
5 Minidumps decrypted. Each one is saying something else
|
0 | Windows OS | ||
|
5 Minidumps decrypted. Please help read them
|
2 | Windows OS | ||
| Thread Tools | Search this Thread |
|
|
All times are GMT -4. The time now is 05:24 AM.