All I want for Christmas is a cpu that doesn't freeze.

usasma · 27 Dec 2009

Please zip up and upload the CBS.log file - usually in C:\Windows\Logs\CBS

This is a STOP 0x7F error, more info here: BSOD Index

You have symbol errors in your debugger, please do this to correct them:

Symbol File Path:
FYI - Open WinDbg, go to File...Symbol File Path
Delete anything in the box.
Then copy the stuff in the Code box below and paste it into the box.

Code:

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Then click on OK to exit the dialog.
Then close WinDbg and answer Yes when it asks you if you want to "Save information for workspace"

Please do this to upload the dump files:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
{Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

Sweettooth1074 · 27 Dec 2009

Hey, USASMA thank you so much for all your posts. You have been very helpful and patient along the way. Hopefully we can get to the bottom of this situation.

I completely forgot about the CBS Logs. Good thinking. Here is your LOG FILE as requested.

Attachment 43938

Also, I switched the coding so that all dumps go into the Minidump folder. I have no idea why it switched over to the MEMORY.DMP. Anyways that is fixed. The next time I get a BSOD, I will zip up the contents in the Minidump folder.

Finally, I am downloading the correct symbols and will have it uploaded very soon.

usasma · 27 Dec 2009

The only failures that were noted in the CBS.log file (from 12/22/09 to present) were due to failed uploads (presumably to the Windows Update website). Are there times that the system isn't connected to the internet?

The symbol file thing will correct those errors in your debug reports that you posted. If there are any .dmp files in the C:\Windows\Minidump folder - please zip them up and upload them with your next post. We can work with some different command and extract some more information from them.

Sweettooth1074 · 27 Dec 2009

It appears the Security Processor Loader Driver is running back to normal. Don't ask me how. I just checked my device manager and my system information to confirm.

Attachment 43952

Still waiting for another BSOD. Once I get it I will make sure to zip it and post the contents.

Sweettooth1074 · 27 Dec 2009

I am still waiting for another BSOD. So far I have seen my screen freeze up twice and one time the video was distorted (look like a gpu issue).

I did manage to retrieve an older memory dump (last night). Here is what it displayed:

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b7f810
Debug session time: Sat Dec 26 23:35:04.852 2009 (GMT-6)
System Uptime: 0 days 0:09:25.834
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 801de000, 0, 0}

PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+5f )

Followup: MachineOwner

Sweettooth1074 · 27 Dec 2009

This might help...after talking with my friend about the problem he alerted me that...

we tried to install a graphic card four months ago.

It was a Nvidia 8600GT PCI-E graphic card if my memory serves me right. Well, when I installed the card I didn't encounter any issues. After one day, I decided to take the card out of my cpu because I didn't trust the card would run well with my specs. I didn't have any issues when the card was taken out properly. I made sure to uninstall all of the drivers immediately and my system ran fine...that is until I got these random freezes and BSODs.

Could this be the source of my problem? Or just add more crap to the equation?

usasma · 27 Dec 2009

Use "!analyze -v" (without the quotes) to get more info from the memory dump file.
You type that in the blank box at the bottom of the debugger screen and press Enter

Could be just c***, or it could be significant. Do you still have the old card? If so, uninstall the current card and install the old card. If the BSOD's stop - you've found the culprit.

Sweettooth1074 · 28 Dec 2009

Here you go, I used "!analyze -v" and this the result:

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b7f810
Debug session time: Sat Dec 26 23:35:04.852 2009 (GMT-6)
System Uptime: 0 days 0:09:25.834
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 801de000, 0, 0}

PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+5f )

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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801de000
Arg3: 00000000
Arg4: 00000000

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

PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 0x28)
eax=ffff0023 ebx=00000000 ecx=875e3d08 edx=00000001 esi=875e3d08 edi=00000000
eip=82a7d57b esp=a154aff4 ebp=a154aff4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiTrap0E+0x5f:
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h ss:0010:a154affc=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 00000000 to 82a7d57b

STACK_TEXT:
a154aff4 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x5f

STACK_COMMAND: .tss 0x28 ; kb

FOLLOWUP_IP:
nt!KiTrap0E+5f
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+5f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f

BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f

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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801de000
Arg3: 00000000
Arg4: 00000000

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

PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 0x28)
eax=ffff0023 ebx=00000000 ecx=875e3d08 edx=00000001 esi=875e3d08 edi=00000000
eip=82a7d57b esp=a154aff4 ebp=a154aff4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiTrap0E+0x5f:
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h ss:0010:a154affc=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 00000000 to 82a7d57b

STACK_TEXT:
a154aff4 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x5f

STACK_COMMAND: .tss 0x28 ; kb

FOLLOWUP_IP:
nt!KiTrap0E+5f
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+5f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f

BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f

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

chev65 · 28 Dec 2009

You do realize that your Dell 531s is not on the Dell compatablity list for Windows 7.
Dell - Support

According to Dell:
If your computer is not on this list, installing Windows 7 is not recommended (the computer may not have the minimum hardware requirements needed or have very little functionality).

It might be worth running the Windows 7 compatibility update advisor which can be accessed from this page>
Dell - Technical Support

From what I have read the 32 bit editions are working on your notebook but not the 64 bit versions. According to Dell there is no support for either.

Sweettooth1074 · 28 Dec 2009

I did see that that the Dell 531s is not on the Dell compatibility list for Windows 7.

I tested the system with the Upgrade Advisor and discovered there were no problems. FYI this problem started to creep up with Windows Vista Basic. Once I switched over to Windows 7 Ultimate I noticed the freezing issue and BSOD a little more often.

Thanks for your help.

Here is a fresh minidump from a BSOD that occurred almost ten minutes ago.
Attachment 44176