why am i getting bsods on my new dell?

[skald89]

I keep getting bsod on my new xps 15. I got it within the first few minutes of opening the laptop. All i have is stuff from download.com,cnet, and adobe.com.

 

[zigzag3143]

I keep getting bsod on my new xps 15. I got it within the first few minutes of opening the laptop. All i have is stuff from download.com,cnet, and adobe.com.

We really need the actual DMP file

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.


If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[Lemur]

Welcome to SF.

First, do the following:

HOW TO FILL OUT YOUR SYSTEM SPECS

In the line at the top of “www.SevenForums.com” you will see UserCP.
That is an abbreviation for User Control Panel.
Click on UserCP.
In the left-hand column, under Your Profile you will see Edit System Spec.
Click on Edit System Spec
You can copy and paste from the output of Speccy, Speccy - System Information - Free Download to fill out much of the info. Be sure to use the Other Info section of your System Specs for such info as your optical drive, your wireless adapter, your speakers, etc.


Then do this:


BSOD Posting Instructions

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[JMH]

I keep getting bsod on my new xps 15. I got it within the first few minutes of opening the laptop. All i have is stuff from download.com,cnet, and adobe.com.

Hi skald & welcome,

Assuming that your computer is indeed new & under warranty -

IMHO -
I would suggest a duty of care applies even to volunteers assisting.

As I see it we volunteers should not be putting at risk the rights,YOU, the consumer has under that warranty...

Therefore I would strongly suggest that you should seek advice asap.

 

[skald89]

I keep getting bsod on my new xps 15. I got it within the first few minutes of opening the laptop. All i have is stuff from download.com,cnet, and adobe.com.

Hi skald & welcome,

Assuming that your computer is indeed new & under warranty -

IMHO -
I would suggest a duty of care applies even to volunteers assisting.

As I see it we volunteers should not be putting at risk the rights,YOU, the consumer has under that warranty...

Therefore I would strongly suggest that you should seek advice asap.

I'm sorry you lost me. May you dumb that down for me?

 

[JMH]

I gather you are using a NEW Dell laptop.
Is that computer under warranty? It should be.
You say you have problems on this new computer in fact soon after opening it.
If this is all accurate information something is obviously wrong.
Therefore if it is accurate & Dell have a Warranty in place they are obliged / duty bound to correct the problem that exists.

 

[skald89]

I already called them but the cs rep seemed like an idiot. She wanted me to do a system restore and I said no. She said a tech will come and replace the hdd. Which is stupid b.c if it happened within the first few minutes of using it then obviously a system restore wont fix it.

 

[JMH]

I already called them but the cs rep seemed like an idiot. She wanted me to do a system restore and I said no. She said a tech will come and replace the hdd. Which is stupid b.c if it happened within the first few minutes of using it then obviously a system restore wont fix it.

We have all put up with that type of rot at some stage. Tis called avoiding responsibility.
I would persist by asking to speak with a supervisor - these types of complaints can be escalated.... Believe me.
Or you could carefully package up the new computer, make sure you have the docket / receipt etc of payment, take it back to the store where you purchased it, politely explain what happened on opening it, let them know you are not happy etc.
They {Retailers} carry weight with the computer manufacturers.

 

[Bill2]

I would agree with JMH, one should not need to start troubleshooting on a newly opened computer, that too on a premium product. Since its brand new, it makes sense to call Dell. Just one thing you may or may not know, all vendors including Dell use refurbished/"like-new" parts in warranty replacements. Theres nothing catastrophic about that, but i've seen lots of people hitting the roof about that.

Dell has a good service record (at least in some parts of the world) and they also have a return period somewhere around 15-30 days (i think within 21 days of shipment). So, you also have the option to return this machine, if the purchase fullfills that criterion.

 

[skald89]

when the tech comes I will talk to him and if he says he is just replacing the hd and the touch buttons that stopped working. I will call and speak with a supervisor that this is unacceptable from a new product that I have so many issues out of the box. I bought it from dell.com

They are being extremely slow and stupid with my laptop. I ordered it on nov 28 and got it on dec 6 and they still havent registered my service tag and express number to my laptop. They can only find my records through the order number.

 

[DustSailor]

I would also see about installing drivers. Provided he doesn't do that for u. I know before I've had my comp crash before i found a faulty driver that only needed an updated driver

 

[skald89]

its just crazy how its brand new and has more problems than my 12 yr old pc.

 

[JMH]

its just crazy how its brand new and has more problems than my 12 yr old pc.

This sometimes happens with electronics. It is most infuriating we know.
There are times when we need to grit our teeth & persevere.
I have had my fair share of these "battles."{ one over the past few months with another manufacturer HP.} They can be won!

 

[skald89]

im going to try to get them to just give me a new one and demand an memory upgrade for the hassle but thats just wishful thinking.

I really need to know why i get the bsod to argue with them

 

[skald89]

ordered it from dell.com on nov 28 and got it on the 6th or 7th.

If I know why it happens I can tell them that the stuff they say is wrong or correct.

 

[Bill2]

ordered it from dell.com on nov 28 and got it on the 6th or 7th.

If I know why it happens I can tell them that the stuff they say is wrong or correct.

See post #2 in this thread.

 

[wish]

ordered it from dell.com on nov 28 and got it on the 6th or 7th.
If I know why it happens I can tell them that the stuff they say is wrong or correct.

It seems Zone Alarm causing the problem.
Try to uninstall it completely and see if the problem persist.
Use this tools after uninstall ZA:
http://download.zonealarm.com/bin/free/support/cpes_clean.exe

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002e41ec0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002e41ec0

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e78ca9 to fffff80002e79740

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02e78ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02e77172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02e41ec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0c477dc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

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

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

 

[skald89]

I ran whocrashed and it gave me this as the results


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12/9/2010 6:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-26364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E41EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12/9/2010 6:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x11A8)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E41EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software UNEXPECTED_KERNEL_MODE_TRAP





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswtdi.sys (avast! TDI Filter Driver, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



funny how avast and zone alarm seem to be the reasons. Both run in the background when it happens and theyre suppose to help the computer, ironic.

 

[skald89]

Oh and additional to the bsod I have had similar situations were instead of it freezing up and going to the bsod it restarts itself.

 

[DustSailor]

I would also see about installing drivers. Provided he doesn't do that for u. I know before I've had my comp crash before i found a faulty driver that only needed an updated driver

I ran whocrashed and it gave me this as the results


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12/9/2010 6:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-26364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E41EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12/9/2010 6:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x11A8)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E41EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software UNEXPECTED_KERNEL_MODE_TRAP





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswtdi.sys (avast! TDI Filter Driver, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



funny how avast and zone alarm seem to be the reasons. Both run in the background when it happens and theyre suppose to help the computer, ironic.

Almost wanna say I told you so, cause I did