Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on Dell XPS 8000


  • Please log in to reply
6 replies to this topic

#1 gd18

gd18

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:39 PM

Posted 17 April 2010 - 07:39 AM

Hello everyone,
I just purchased a new Dell XPS 8000. I have been experiencing BSOD very frequently, usually couple times a day. I called their customer support, however they only ask me to run the diagnostic program which scans the hardware and concludes everything is fine. He also remote debugged my mini dumps and concludes it is a driver problem. However, updating to the newest driver does not solve the problem. I used sfc /scannow to scan the system, there is no integrity violation. So, is my problem caused by hardware? or software?
I have included the specs and two mini dumps I have.
Specs:
1 224-6177 Studio XPS 8000
1 317-2644 Studio XPS 8000, Intel Core i7-860 processor(8MB Cache, 2.80GHz)
1 317-2645 3GB DDR3 SDRAM AT 1066MHZ-3X1GB
1 330-3828 Dell Consumer Multimedia Keyboard, US
1 320-7810 No Monitor
1 320-0844 1024MB nVidia GeForce GT220
1 341-0262 500GB Serial ATA II Hard Drive 7200 RPM
1 330-4490 Dell Resource DVD with Application Backup
1 420-6576 DELL WELCOME,Software Dimension/Inspiron
1 420-8873 Dell Dock Consumer
1 420-6436 PC-Restore, Dim/Insp
1 421-0323 Windows Live Search,Multiple User Interface
1 463-2282 Dell Owners Manual installed on your system,click on icon after system set-up to access
1 330-6097 You have chosen a Windows 7 System
1 421-0092 DELL-DOWNLOAD-FLAG
1 421-1603 Genuine Windows 7 Home Premium, 64bit, English
1 421-2087 eBay Webslice
1 330-3826 Dell Studio USB Optical Mouse
1 410-1867 ADOBE READER 9.0 MULTI- LANGUAGE
1 313-8760 16X DVD+/-RW
1 313-8757 Roxio 10.3, Easy CD & DVD
1 421-1412 Cyberlink Power DVD 8.3 Playback
1 313-7186 Integrated 7.1 Channel Audio
1 313-6138 No Speaker Requested
1 410-2152 McAfee SecurityCenter with anti-virus, anti-spyware firewall, 15-months
1 412-1397 No Productivity Software requested
1 950-3337 1 Year Limited Warranty
1 903-6497 Dell Limited Hardware Warranty Plus In-Home Service [after Remote Diagnosis], Initial Year
1 904-6080 In-home Service after Remote Diagnosis, Initial Year
1 950-9797 No Warranty, Year 2 and 3
1 420-8878 Software, Soft Contracts Dell In-Home
1 960-8700 Dell Limited Hardware Warranty 7X24 Technical Support, Initial Year
1 988-7707 2GB DATASAFE ONLINE 1.1 FOR SDO/DIM/INS/XPS
1 420-9518 DATASAFE ONLINE 1.1 2GB
1 988-0099 To activate your online backupaccount, go to Start, Programs, DataSafe Online
1 330-0172 S and P Drop-in-Box Marcom forDHS Desktops

minidump 1

Loading Dump File [C:\Windows\Minidump\041510-21372-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Thu Apr 15 22:12:54.632 2010 (GMT-4)
System Uptime: 0 days 0:10:40.772
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 1aa5df8d, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42c75 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 000000001aa5df8d
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: WinSAT.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880076206a0 -- (.trap 0xfffff880076206a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001aa5e000 rbx=0000000000000000 rcx=00000000c000ec8b
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbece7 rsp=fffff88007620838 rbp=000000001aa5e000
r8=000000001aa5e001 r9=0000000000002b0d r10=fffff70001080488
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiStackFault+0xe7:
fffff800`02cbece7 00448b8d add byte ptr [rbx+rcx*4-73h],al ds:00000003`0003b1b9=??
Resetting default scope

MISALIGNED_IP:
nt!KiStackFault+e7
fffff800`02cbece7 00448b8d add byte ptr [rbx+rcx*4-73h],al

LAST_CONTROL_TRANSFER: from fffff80002c6bb6e to fffff80002cc0f00

STACK_TEXT:
fffff880`07620538 fffff800`02c6bb6e : 00000000`0000001a 00000000`00041287 00000000`1aa5df8d 00000000`00000000 : nt!KeBugCheckEx
fffff880`07620540 fffff800`02cbefee : 00000000`00000001 adffe0ff`af0deb3b 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42c75
fffff880`076206a0 fffff800`02cbece7 : 00000000`1aa5e000 00000000`00000000 fffff800`02cbed4a 00000000`00000010 : nt!KiPageFault+0x16e
fffff880`07620838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStackFault+0xe7


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42c75
fffff800`02c6bb6e cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42c75

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

minidump 2:
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\041710-14788-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe50
Debug session time: Sat Apr 17 00:15:47.623 2010 (GMT-4)
System Uptime: 0 days 5:36:30.652
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: 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: fffff80002eb5605

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002ec1b69 to fffff80002ec2600

STACK_TEXT:
fffff880`02b69de8 fffff800`02ec1b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02b69df0 fffff800`02ec0032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02b69f30 fffff800`02eb5605 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`04aa1028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeInvalidAccessAllowed+0x5


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
24 errors : !nt (fffff80002eb5642-fffff80002eb577a)
fffff80002eb5640 0d 8b *90 24 00 eb e1 48 8b 0d *08 4f 24 00 eb d8 ...$...H...O$...
fffff80002eb5650 32 c0 *8c 90 90 90 90 90 90 90 *db 90 90 90 90 90 2...............
fffff80002eb5660 48 89 *2d 24 18 48 89 54 24 10 *f7 56 57 41 54 41 H.-$.H.T$..VWATA
fffff80002eb5670 55 41 *1c 41 57 48 83 ec 70 45 *2c f6 4c 8b ea 48 UA.AWH..pE,.L..H
...
fffff80002eb56c0 0f ba *90 10 01 00 00 00 0f 83 *19 08 00 00 48 89 ..............H.
fffff80002eb56d0 bb 18 *5a 00 00 45 0f 20 c4 44 *f9 22 c6 65 48 8b ..Z..E. .D.".eH.
fffff80002eb56e0 0c 25 *21 00 00 00 48 8b 69 58 *47 48 8b 3c 25 20 .%!...H.iXGH.<%
fffff80002eb56f0 00 00 *ca 48 83 c1 50 45 33 d2 *f6 ba 25 42 bf 19 ...H..PE3...%B..
...
fffff80002eb5740 ba a3 *3b 00 00 00 10 48 8b 8b *34 00 00 00 ba 01 ..;....H..4.....
fffff80002eb5750 00 00 *4c 41 0f b6 c2 0f 42 c2 *f1 53 04 89 84 24 ..LA....B..S...$
fffff80002eb5760 c8 00 *1f 00 49 3b ca 0f 84 51 *e8 00 00 8b 41 08 ....I;...Q....A.
fffff80002eb5770 89 41 *65 3b 05 9f 38 21 00 0f *6f 9b 07 00 00 8b .Ae;..8!..o.....

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

BC AdBot (Login to Remove)

 


#2 bandaid1968

bandaid1968

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 17 April 2010 - 08:42 AM

if its still under warrenty take it back

#3 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:02:39 PM

Posted 17 April 2010 - 11:12 AM

The above advice is very adequate.

I called their customer support, however they only ask me to run the diagnostic program which scans the hardware and concludes everything is fine.

Tell them, they're wrong.
Your errors:
IMAGE_NAME: memory_corruption
IMAGE_NAME: hardware

most likely, indicate RAM issue.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#4 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:03:39 PM

Posted 17 April 2010 - 04:05 PM

I agree.

I just purchased a new Dell XPS 8000.


Then you should take it back or ship it back to where you got it. Don't keep a new computer that's already BSOD'ing.
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#5 gd18

gd18
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:39 PM

Posted 17 April 2010 - 05:42 PM

Thanks guys. I will call them and ask for a exchange.

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:02:39 PM

Posted 17 April 2010 - 05:44 PM

Tell them, that if they think, they can outsmart BleepingComputer people....it won't happen...hehehehe

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#7 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:03:39 PM

Posted 17 April 2010 - 06:07 PM

Tell them, that if they think, they can outsmart BleepingComputer people....it won't happen...hehehehe

:huh:

It might take some doing, but they should give you an exchange, gd18. :huh:
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users