new pc BSOD 3 times first week

[Drumbokas]

I have a Dell studio xps 9000
i7-920 @ 2.66
12 gb ddr3 SDRAM @ 1066mhz
mobo is a "dell" 0x501h (intel chipset x58 rev 13)
ATI Radeon HD 5870
Serial ATA II RAID 0 With Dual640GB Hard Drives
Soundblaster X-Fi Titanium
bios is dell a15 dated 02/04/2010


BSOD at seemingly random times

any help is much appreciated

-drumbokas

 

[TorrentG]

Hello.

Unfortunately, my first words to you are to tell you that you have some hardware-based issue. All crashes are of the 0x124 hardware type. What this means is that Windows is complaining that some hardware is faulty. With these crashes, there is no analysis to do because they contain little to no practical, helpful information. More on this at the end of the post.

Further, these crashes have been so abrupt and bad for your machine that it isn't even able to list all drivers in the crash dumps. I can only see approximately 15 percent of them, which is not very helpful here.

You will find the best way to go about troubleshooting or possibly repairing the issue is if you follow this link as carefully as possible. The author is extremely knowledgeable on the matter:

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Please post asking any questions you may have as I might be able to be helpful to you in ways. Good luck.

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


Loading Dump File [E:\Temp\Rar$DI00.406\080410-24944-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Thu Aug  5 00:08:38.844 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:10.968
Loading Kernel Symbols
..............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800ad928f8, 0, 0}

Probably caused by : hardware

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

4: kd> lmtn
start             end                 module name
fffff800`00bbe000 fffff800`00bc8000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`02c01000 fffff800`031dd000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff800`031dd000 fffff800`03226000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c76000 fffff880`00cba000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00cba000 fffff880`00cce000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00cce000 fffff880`00d2c000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d2c000 fffff880`00dec000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00e00000 fffff880`00e0a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00e0a000 fffff880`00e3d000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e3d000 fffff880`00e4a000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00e4a000 fffff880`00e5f000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e5f000 fffff880`00e74000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e74000 fffff880`00ed0000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00ee5000 fffff880`00f89000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f89000 fffff880`00f98000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f98000 fffff880`00fef000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00fef000 fffff880`00ff8000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01014000 fffff880`0101fe00   PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
fffff880`0103c000 fffff880`01158000   iaStor   iaStor.sys   Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`01158000 fffff880`01175000   jraid    jraid.sys    Wed May 27 01:39:35 2009 (4A1CD217)
fffff880`01175000 fffff880`011a4000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`011a4000 fffff880`011af000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`011af000 fffff880`011fb000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122d000 fffff880`013d0000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013d0000 fffff880`01400000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0143a000 fffff880`01474000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01480000 fffff880`014de000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`014de000 fffff880`014f8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`014f8000 fffff880`0156b000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`0156b000 fffff880`0157c000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0157c000 fffff880`01586000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01586000 fffff880`015d2000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`015d2000 fffff880`015e8000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`01675000 fffff880`0167d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01685000 fffff880`01777000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01777000 fffff880`017d7000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`017d7000 fffff880`017e9000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`017e9000 fffff880`017f2000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`017f2000 fffff880`01800000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`02c00000 fffff880`02c13000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`02cde000 fffff880`02dfa000   dump_iaStor dump_iaStor.sys Thu Jun 04 21:53:40 2009 (4A287AA4)
Mini Kernel Dump does not contain unloaded driver list

 

[andsome]

If it's new take it back and complain.

 

[TorrentG]

Yep, I agree with Andsome. If it's under warranty, tell Dell that you are getting 0x124 stops and you need an RMA, please.

 

[Nibiru2012]

No offense intended here toward the purchaser, but with all of the issues DELL has been having lately this really does not surprise me.

Here in the "Land of DELL", you won't find to many natives that use DELL or recommend them either. Most of the users here are with the government entities or businesses that purchased DELL on volume discount bids and/or contracts.

The geeks and ubergeeks here wouldn't touch a DELL for all the contestants in the Miss Universe pageant.

On the flip side, I hope you get your situation resolved soon. Don't let DELL screw you around either, they're notorious for making unfulfilled promises. If you have to take it up to a supervisor level then do that.

If it were me I would get my money back and get another system from either Lenovo, Acer, etc.

 

[Drumbokas]

power?

Could this be caused by insufficient power? From what I have read in other forums, it seems that the studio xps 9000 has a 475watt power supply... the minimum system requirements for the ATI 5870 state that it needs 500watts.

I have noticed that the 9000 is no longer for sale on Dell's site, now they have the 9100, which, apparently, is the same machine with a larger power supply.

thanks for the help.

-drumbokas


also, I have been using dell for many years, and this is my 8th and LAST dell...
the BSOD is not the only problem I've had with this machine.

 

[Nibiru2012]

the minimum system requirements for the ATI 5870 state that it needs 500watts.

DELL should have known that from the beginning if they supplied the 5870 with the computer. If so then they're at fault and should send you an adequate PSU for your system.

If a 500 watt is the minimum recommended for the 5870 you should get at least a 550watt or even a 600watt PSU for a cushion or fudge factor.

Contact DELL and see what their response is.

If you added the 5870 then just go buy a good quality PSU such as Corsair, ThermalTake, Antec, etc., make sure it's at least an 80 PLUS Bronze Certified model and you'll be good.

OEM supplied PSUs are usually junk compared to third-party power supplies, so it may just be best to bite the bullet and buy your own PSU.

 

[Drumbokas]

warranty

Normally I'm that guy that immediately voids the warranty by opening up the box and having a look around, but with this machine I have not done so. I am ok with buying my own power supply, I knew that I would probably be upgrading it eventually, I just didn't expect it to need it so soon. I just don't want to replace the PS and then find that it doesn't fix the problem and Dell will no longer honor the warranty since I opened it up and replaced the PS. I suppose i should go through the miserable process of contacting dell support... /sigh.

thanks
-drumbokas

 

[Nibiru2012]

Sound like it's time to put the monkey on DELL's back then.

Remember, the squeakiest wheel usually gets more grease, especially if you are respectful but firm with them. Don't let them put you off and like I said earlier, take this to a supervisor or even higher if you have to.

Keep us posted on the results.

GOOD LUCK!

 

[andsome]

One of the penalties of buying from the big manufacturers rather than a local expert. Sorry I cannot help personally.

 

[TorrentG]

It would theoretically make sense that the psu could be somehow involved. If it wasn't creating the stable power conditions necessary by the demand of the pc, the pc would not be able to list all drivers. It wouldn't have enough time.

So, it could be what is happening but by no means, definitely.

 

[Nibiru2012]

One of the penalties of buying from the big manufacturers rather than a local expert. Sorry I cannot help personally.

That's true.

The absolute best way to go is just build your own system. You don't have to be a rocket scientist to do it and it extremely easy... easier than one might think.

 

[Drumbokas]

another one

Well, I haven't had time to get in touch with dell, and am really dreading having to deal with them. Today while setting up sharing across my LAN, I got a new BSOD.

Is this one the same as the others, 0x124?

-drumbokas

 

[TorrentG]

Unfortunately, yes. These crashes are not going to resolve themselves and in fact, will become worse with time.

Best advice is to do yourself a huge favor and return the machine. If you have to ship it, politely stand your ground that you don't want to pay for shipping either.

They gave you a lemon. Send them crash dumps if necessary and tell them you know the deal.

 

[Drumbokas]

bleh

I just got off the phone with tech support. Ravi took a look at the dumps, looked at a reliability chart, and ran a pre-boot hardware diagnostic. Even though all the dumps clearly state that this is a hardware issue, the diagnostic did not find any problems; sooo, now I get to restore the machine to its factory defaults.

He will call me back tomorrow night to continue troubleshooting.

He was very confident that this is not a power supply issue...

-drumbokas

 

[TorrentG]

Of course they're confident. lol

What I've told you is extremely accurate.

"So, it could be what is happening but by no means, definitely."

If he is telling you anything else than that at this point, it's a clear lie.

A clean vanilla install of Windows could sort the problem, with 20% chance of being well, as a guesstimate.

 

[andsome]

Why shouild you mess about with things? Insist on them having it back and sorting it.

 

[TorrentG]

Why shouild you mess about with things? Insist on them having it back and sorting it.

Well, it is also theoretically possible that he installed some extremely bad software that is causing this.

Very unlikely but again, theoretically possible. If he did, then it would be his "fault".

I would still push to have it replaced because I can almost (key word=almost) guarantee that this is a lemon pc.

 

[Drumbokas]

crash?

24 hours of fresh install and no problems to report. Then again, no real apps installed, no internet access, no updates... the machine is sitting idle with no problems.

An hour before the dell rep was supposed to call me back, I played a few games of solitaire, changed the wallpaper, added quick launch to the taskbar, and made some other minor changes such as removing categories from the dock.

The dell rep said that since the pc seemed stable so far, that I should install apps and updates and such, and that he will call me back again tomorrow.

I installed Firefox and ZoneAlarm, re-booted, uninstalled McAffee, rebooted, installed AVG and windows updates (including a creative update for the soundcard). reboot. Then I installed flash, configured browser settings(toolbars, homepage, etc.), and started to download WoW.

While waiting, I configured the sound options to use all of the speakers instead of just stereo. I added a desktop toolbar to the taskbar and was curious about a couple of the entries that appeared there that weren't items I could see on my desktop... there is something there called "homegroup" and when I clicked on it my screen went black.

No keyboard response (caps and num lock lights non-responsive), and powering the monitor on and off had no results. Eventually I held down the power button...
No minidump.

I suppose I should have waited between each app install to check for problems, but at this point I'm not sure if it is an app or just actually using the pc that causes the problem.

I will continue to post updates.

-drumbokas

edit: besides the 4 BSODs mentioned in previous posts, before this fresh install I had several crashes such as the one described above, where the screen went black and keyboard was not responding.

 

[Nibiru2012]

Glad things are working somewhat better for you now.

Is there a driver DELL has for the keyboard, they're known for having "special" type keyboard and maybe a driver issue.

Have you installed the internet NIC or wireless drivers yet since you say there is now access?

@andsome -

Why shouild you mess about with things? Insist on them having it back and sorting it.

With DELL that wouldn't solve the problems, they're notorious for poor support and resolving problems.

What Drumbokas is doing is the same thing I would do. Clean fresh install and go from there.


In my opinion, all serious computer users should know how to install the operating system and related drivers, software, etc. It's the only way to really understand their systems.