Consistent BSODS and event errors...please help!

xiaobao12

Senior member
Oct 9, 2004
283
0
0
Hi all,

It's been a long time since I've used this site. It's nice to be back...

I am running a Dell Dinosaur Dimension 4600....2.66 GHZ, 4 GB RAM, 350W Power supply, 200 GB Maxtor HD (bought about 4 years ago and used for the first time 5 days ago), 120GB WD and 2 opticals.

I recently installed Windows 7 Pro 32bit (prior to that, I was using XP). I've spent 5 days dealing with BSODS and errors. Windows updates doesn't work unless I do them a few at a time, manually.

I would appreciate any help. Even if it means my motherboard controller is messed up (somebody suggested). Or could it be my PSU is not enough?

Last night, I thought it was the HD so I reinstalled Windows 7 today (yes, after going through all those updates)....but am still getting all the errors.

I have run memtest86 (no errors) but I didn't run it on each memory stick separately.

Thanks so much.
 
Last edited:

Ken g6

Programming Moderator, Elite Member
Moderator
Dec 11, 1999
16,836
4,815
75
Is that a Pentium 4? A quick search turned up mention of the Dell Dimension 4600 in a list of the worst PCs of all time! Looks like a bad PSU isn't unlikely.

But if it's a P4, you're almost better off starting from scratch. (Edit: Just because the P4 is a hot, underpowered CPU, not because it would cause these errors.)
 

Ken g6

Programming Moderator, Elite Member
Moderator
Dec 11, 1999
16,836
4,815
75
Heh. Cooler Master. Perfect. (Cooler Master isn't the best brand of PSU, but it should do the job.)

Unless you're interested in buying a new PC, or building a new one with some of the old parts, yes, it's worth installing to try to see if it is the PSU.
 

mfenn

Elite Member
Jan 17, 2010
22,400
5
71
www.mfenn.com
The next time it BSODs, run WhoCrashed after your reboot. That'll give you more information. Also, posting the errors that you see in the event log would be helpful.
 

xiaobao12

Senior member
Oct 9, 2004
283
0
0
mfenn, I will try WhoCrashed.

How do I attach files here on Anandtech? I don't see any options, even under the advanced reply options.

Ahh, I just noticed that I am not allowed to upload attachments. I will copy and paste the Event Viewer errors tomorrow then.
 

mfenn

Elite Member
Jan 17, 2010
22,400
5
71
www.mfenn.com
Yep, no attachments allowed on this forum. You wouldn't like the sorts of attachments that the OT folks would post. :awe:
 

xiaobao12

Senior member
Oct 9, 2004
283
0
0
Hi guys, so I installed the new PSU - problem is that there were not enough IDE connectors. So, CD-ROM is not powered as well as one of the addition HDs.

Anyhow, no BSODS yet. Could this have been the cause? And how come the lack of power was a problem after switching to Windows 7? Certainly, the OS doesn't draw more power!?
 

xiaobao12

Senior member
Oct 9, 2004
283
0
0
mfenn,

here are some of the errors that happened before I replaced the PSU:

Kernel- EventTracing Event ID 3
Session "ReadyBoot" stopped due to the following error: 0xC0000188

Bugcheck Event ID 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc000001d, 0x82c1e9da, 0x80d8adf0, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101211-425937-01.

Also, a ton of application errors (here are a few of them):

Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc225
Faulting module name: dwmcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda08
Exception code: 0xc0000096
Fault offset: 0x00008c96
Faulting process id: 0xf58
Faulting application start time: 0x01cc8952f8bcb424
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: C:\Windows\system32\dwmcore.dll
Report Id: cb813d7f-f549-11e0-b547-0007e972dafe

Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc225
Faulting module name: dwmcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda08
Exception code: 0xc0000005
Fault offset: 0x000367cb
Faulting process id: 0x550
Faulting application start time: 0x01cc8943a27735fc
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: C:\Windows\system32\dwmcore.dll
Report Id: 35a35cd0-f546-11e0-b547-0007e972dafe

Faulting application name: chrome.exe, version: 14.0.835.202, time stamp: 0x4e84cf5b
Faulting module name: chrome.dll, version: 14.0.835.202, time stamp: 0x4e84cf05
Exception code: 0xc0000005
Fault offset: 0x000597a2
Faulting process id: 0xd18
Faulting application start time: 0x01cc8946d63eb1dd
Faulting application path: C:\Users\Shinzaemon\AppData\Local\Google\Chrome\Application\chrome.exe
Faulting module path: C:\Users\Shinzaemon\AppData\Local\Google\Chrome\Application\14.0.835.202\chrome.dll
Report Id: 8442ede1-f53a-11e0-b547-0007e972dafe

Faulting application name: WerFault.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc2d9
Faulting module name: USER32.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb2f
Exception code: 0xc0000096
Fault offset: 0x00017529
Faulting process id: 0x864
Faulting application start time: 0x01cc89452431c762
Faulting application path: C:\Windows\system32\WerFault.exe
Faulting module path: C:\Windows\system32\USER32.dll
Report Id: 684b69d0-f538-11e0-b547-0007e972dafe

----

Sorry it is very messy. I didn't know how else to post them. Thanks for your help.
 

xiaobao12

Senior member
Oct 9, 2004
283
0
0
Here are 3 of them from BlueScreenView:

101311-426875-01.dmp 10/13/2011 3:31:34 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x8fafc8fe 0x00000002 0x00000000 0x8fafc8fe usbccgp.sys usbccgp.sys+108fe USB Common Class Generic Parent Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntoskrnl.exe+38b5b usbccgp.sys+108fe ntoskrnl.exe+3236c3 ntoskrnl.exe+2eefb C:\Windows\Minidump\101311-426875-01.dmp 1 15 7600 181,408




101211-425937-01.dmp 10/12/2011 9:01:26 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc000001d 0x82c1e9da 0x80d8adf0 0x00000000 halmacpi.dll halmacpi.dll+49da Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit halmacpi.dll+49da halmacpi.dll+4c16 USBPORT.SYS+8e70 USBPORT.SYS+8807 C:\Windows\Minidump\101211-425937-01.dmp 1 15 7600 143,544




101211-417062-01.dmp 10/12/2011 2:59:32 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x97b0005c 0x9882b5e4 0x00000000 cdd.dll cdd.dll+1005c Canonical Display Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit cdd.dll+1005c cdd.dll+147b8 win32k.sys+b9336 win32k.sys+becde C:\Windows\Minidump\101211-417062-01.dmp 1 15 7600 143,360


Thanks for your help.
 

mfenn

Elite Member
Jan 17, 2010
22,400
5
71
www.mfenn.com
Most of those errors are low-level system errors. If a new PSU cleared up the problem, I'd say that the cause was that the old one wasn't providing enough clean power to run the system properly. Windows 7 certainly uses more system resources than XP, so I could see that putting additional load on the PSU.

Oh yeah, if your new PSU has a spare SATA power connector, you can use an adapter like this one to convert to a Molex.