BSOD, probably faulty RAM

[squishycube]

Hello all,
I registered here because I did a Google search and found people who can interpret Pstat output.
My problem is mostly described in the title, once in so many hours I get a BSOD, I'll give you the exact error I got last time:
"DRIVER_IRQL_NOT_LESS_OR_EQUAL

Stop: 0x000000D1 (0x00000028, 0x00000002, 0x00000001, 0xF7B87B4A)

usbohci.sys - Address F7B87B4A Base at F7B86000, Datestamp 41107d62"

(I skipped the part about contacting the admin and shutting down to prevent damage.)

Anyway, attached is the output that pstat gave me, any help is very welcome. (The stats of my PC should be visible, I filled them in in my profile.)

I read that several BSOD's are needed before anything sensible can be said about it, this is the first one I wrote down so I'll have to wait for more...

EDIT: I found out that I don't need to copy the BSOD by hand, I included the last three BSOD's now. The latest one should be the same as the one I typed above.

 

[cpc2004]

This is software error and not memory problem. The culprit maybe daemon tool. Can you recall under what condition your windows crashes? BTW do you have HP USB printer?


FYI

STACK_TEXT:
8055028c f7b78bc9 865849dc 864eef90 805502bc usbohci!OHCI_PollAsyncEndpoint+0x298
8055029c f68a72ba 865849dc 864eef90 804e2eb4 usbohci!OHCI_PollEndpoint+0x1f
805502bc f68a8578 026c6f50 865840e0 864eee18 USBPORT!USBPORT_PollEndpoint+0xe8
805502e4 f68abed0 86584028 50457270 804e2eb4 USBPORT!USBPORT_CoreEndpointWorker+0x2be
80550314 f68b9fb0 86584028 804e2eb4 86584028 USBPORT!USBPORT_DpcWorker+0x18a
80550350 f68ba128 86584028 00000001 8637b834 USBPORT!USBPORT_IsrDpcWorker+0x37e
8055036c f771ca7f 8658464c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
WARNING: Stack unwind information not available. Following frames may be wrong.
805503ac 804dbbd4 8658464c 86584028 00000000 sptd+0xda7f
805503d0 804dbb4d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
805503d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26

 

[squishycube]

Thanks for your reply.

- I do have Daemon tools installed, but for years already. Crashes only started 10 days ago or so
- The last crash is the first one to happen while I was actually at my pc, so I wouldn't know about a pattern (yet)
- I do have an HP USB printer, but I don't think it has been connected since I last reinstalled windows

What would the stack text tell me?

I would attach more minidumps, but I have had no crashes since I took the new RAM out (pc has run for 12 hours+)

 

[AlbertLionheart]

The problem - and this is becoming increasingly common - is that a windows update has interfered with previously stable processes. Sometimes very hard to find but you could try a system restore or uninstalling the last few updates. MS usually get to hear of the problem and produce a patch for the patch - an example was a string of problems with Skype.

 

[squishycube]

But how would you explain that I have had no crashes since I took the RAM out? (Since two days ago, pc has been on 30+ hours)

 

[gbhall]

well, bad ram has to cause a problem in software at some point, which is what the dumps show you. It seems like bad ram to me. albertL is perfectly correct in what he says, it just may not be your particular problem.

 

[mscrx]

according to dump file analysis your problem is this:

CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: USBOHCI.sys
OriginalFilename: USBOHCI.sys
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: OHCI USB Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

I suggest to update chipset drivers first. if you already did then uninstall everything under "universal serial bus controllers" in the device manager and reboot the machine.

 

[mscrx]

sorry I over read you put the ram out. but this might not be the only problem as it was already mentioned by the other guys!

 

[cpc2004]

Refer the following problem and they are related to HP USB Printer driver
https://www.techspot.com/vb/topic61392.html

From the stack trace, I find the footprint of daemon tool
STACK_TEXT:
8055028c f7b78bc9 865849dc 864eef90 805502bc usbohci!OHCI_PollAsyncEndpoint+0x298
8055029c f68a72ba 865849dc 864eef90 804e2eb4 usbohci!OHCI_PollEndpoint+0x1f
805502bc f68a8578 026c6f50 865840e0 864eee18 USBPORT!USBPORT_PollEndpoint+0xe8
805502e4 f68abed0 86584028 50457270 804e2eb4 USBPORT!USBPORT_CoreEndpointWorker+0x2be
80550314 f68b9fb0 86584028 804e2eb4 86584028 USBPORT!USBPORT_DpcWorker+0x18a
80550350 f68ba128 86584028 00000001 8637b834 USBPORT!USBPORT_IsrDpcWorker+0x37e
8055036c f771ca7f 8658464c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
WARNING: Stack unwind information not available. Following frames may be wrong.
805503ac 804dbbd4 8658464c 86584028 00000000 sptd+0xda7f <--- The footprint of daemon tool
805503d0 804dbb4d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
805503d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26

 

[squishycube]

I decided to try some of the solutions here and put the RAM in again after that.
What I did:
- Remove all USB devices (and let the connected ones reinstall themselves again on reboot)
- Uninstall Daemon Tools

I did not update my motherboard drivers, since I can't for the life of my discover of what exact mobo my OEM board is a clone.

Anyway, It seemed to be working, computer was running fine for something like 12 hours and then boom, BSOD. But: it didn't show it properly, the screen was full with strange characters, like when you open an mp3 with notepad.

Then I reboot, but it wouldn't start the memory check. I waited a bit, took the RAM out, but it still didn't want to boot. Waited some more and then it booted (still with new RAM out). This sounds to me like an overheating problem, case is properly cooled though...

I've attached the minidump, I hope that is more readable than the BSOD was.

Thanks for all your help so far, it has been useful.