15 BSOD's from Vista within 1 day out of the Box

Arcanon10

Beta member
Messages
1
Hey all,

2 days ago ... I received my new comp from IBUYPOWER. It is shown below.

OS Name Microsoft® Windows Vista™ Home Basic-32bit
Version 6.0.6002 Service Pack 2 Build 6002
Power Source is 500W
2 HDD: 80GB + 500GB
OS Manufacturer Microsoft Corporation
System Manufacturer IBUYPOWER
System Model System Product Name
System Type X86-based PC
Processor AMD Athlon(tm) II X2 245 Processor, 2900 Mhz, 2 Core(s), 2 Logical Processor(s)
Graphics Card Nvidia 9600GT 512mb
BIOS Version/Date American Megatrends Inc. 1603, 3/27/2009
SMBIOS Version 2.5
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.0.6002.18005"
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.00 GB
Available Physical Memory 1.98 GB
Total Virtual Memory 6.19 GB
Available Virtual Memory 5.29 GB

Soon after setting it up, I began to have BSOD's frequently. The two most common were as follows:

Stop: 0x0000008E ***fltmgr.sys. Adress 80750D52

Stop: 0x0000000A. *** IRQL_Not_Less_or_Equal.

These happened multiple times when 1.) Playing computer games such as World of Warcraft and 2.) Simply typing in a forum, and 3.) attempting to burn a DVD.

Researching these errors, I sought to update all the drivers I could. I upgraded from Windows S1 to S2, updated my Nvidia drivers, my audio drivers ... any driver I could find, until Windows said that all drivers were up to date (not sure if I believed that, however).


As a test, I went on World of Warcraft a few minutes ago in order to induce a BOSD ... sure enough, within 3-4 minutes of being on and just sitting idly, I ran into a BOSD again. The in-game performance is excellent, I should add. Its not as if I'm starting to lag or freeze or my computer is getting overworked. I was typing ... using my keyboard to type.

I then went to the Event Viewer and looked in the Application + System log and found the following Errors at the time of the crash.

Under Application:

11:10:09 AM: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

11:12:47 AM: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
_______________

Under System:

11:10:02 AM: DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC}

11:10:09 AM: DCOM got error "1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

11:10:10 AM: DCOM got error "1068" attempting to start the service netman with arguments "" in order to run the server:
{BA126AD1-2166-11D1-B1D0-00805FC1270E}

11:10:10 AM: DCOM got error "1068" attempting to start the service netman with arguments "" in order to run the server:
{BA126AD1-2166-11D1-B1D0-00805FC1270E}

11:10:20 AM: The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

11:12:47 AM: The following boot-start or system-start driver(s) failed to load: i8042prt
_________________________________________________________________

I am unable to verify if these particular error messages are the same for every BSOD that has hit me. Sorry there is not more descriptive info of every BSOD I have encountered.

Thanks for any advice that is given. Cheers.
 
My advice would be to contact them and send the thing back. It could be all manner of things, memory, motherboard etc. but if you start poking around inside the case you may well invalidate the warranty - and yes you could run memtest and similar to try and find out the cause, but you'll most likely need to send the whole thing back anyway.

As it is something's clearly pretty seriously wrong with it, and was at the time of purchase, so I don't think you should have any quibbles getting a replacement.
 
If you recently received the PC. Contact them and send it back. As well as what berry said don't open it Just in case.

Good luck
 
Back
Top Bottom