[Coolyxxx]

Hi,
2 blue screens in one day makes me feel strange... Whocrashed says that my computer crashed because of oemhx9f3.sys. But the time shown is 7 am, whereas the computer was off at 7am. The date is correct though. Using Everest, the first error was 1003: Error code 10000050, parameter1 bad0b154, parameter2 00000000, parameter3 805c4a53, parameter4 00000000, the second was 1003: Error code 00000003, parameter1 00000000, parameter2 00000000, parameter3 00000000, parameter4 00000000.

2 different codes, 2 different causes? But after rebooting, I sent an error report, then it opened up a microsoft page, which said that it was caused by a driver. There was:
Do a virus scan: did that yesterday.
Check hard drive for errors: did that after first error, and yet second error came up.
Remove new hardware/software: tried that after first crash, also didn't work.
Install latest drivers: only outdated driver was my printer driver, which after updating, disallows me to print for some reason, so I keep with my current drivers.

All these problems with my computer lately.
Once again, any help appreciated.
Thanks.

[philthomas]

Some info here that may be useful.

Might be worth checking your Ram

[Coolyxxx]

The relevant item on that page requires subscription to view. Will check my RAM and see what happens then. And can anyone find anything on oemhx9f3.sys? Because I can't....

[Glaswegian]

Lack of info on a file suggests malware. You'll be able to find info etc on a legit file name, but not on malware. Scans would seem to be in order here - or follow the guide for posting logs.

[Glaswegian]

Just noticed you had already posted a log...

Do you have a location for the file in question?

[Coolyxxx]

Nope, can't find that file Want the other logs from the guide?

[Coolyxxx]

Well, decided to give logs anyway

Malwarebytes' Anti-Malware 1.34
Database version: 1801
Windows 5.1.2600 Service Pack 3

25/02/2009 6:33:11 PM
mbam-log-2009-02-25 (18-33-11).txt

Scan type: Full Scan (C:\|Y:\|Z:\|)
Objects scanned: 309895
Time elapsed: 2 hour(s), 26 minute(s), 51 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)
_________________________________________________

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 02/25/2009 at 06:37 PM

Application Version : 4.21.1004

Core Rules Database Version : 3774
Trace Rules Database Version: 1733

Scan type : Complete Scan
Total Scan Time : 02:29:24

Memory items scanned : 533
Memory threats detected : 0
Registry items scanned : 5871
Registry threats detected : 0
File items scanned : 213390
File threats detected : 0

[Coolyxxx]

Just done Memtest as well. My RAM passed.

[Glaswegian]

Looks like that file, assuming it was bad, has already been deleted. Still having the same problem?

[Coolyxxx]

Hmmm. Not seeming to get any blue screens yet... Could be problem fixed. Thanks.