treaz

New Member
Joined
Jan 10, 2014
Messages
16
Hi,

I find myself in front of a very hard problem... random BSOD. I've had it for a long time now (changing HDD or RAM did not help).

Specs:
win7 x64 home premium sp1
avg free edition 2014.0.4259
ZoneAlarm Free Firewall version: 11.0.780.000


The funny thing is that I get the BSOD when doing medium intensity activity (working on docs and browsing), I NEVER got the BSOD when playing games.

And, unfortunately, I don't know how to read the damn dump file (I've opened it with dumpchk, but I don't understand what exactly I should be looking for).

I've just had one BSOD tonight, I hope someone can figure it out.
 


Attachments

Last edited:
Solution
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffffa80081c32c0, fffff9800eed0e10, 0}

*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+35dd )

Followup: MachineOwner

Hi,
the...
Another thing that struck me is before you fitted the new RAM were you still getting bsod's?
 


Yes, don't you remember that I found those issues in memtest86 with my old RAM?
That's why I bought the new RAM.
 


I thought you'd perhaps had removed a stick and were not getting any bsod's although i could well be getting your case mixed up with another I answered recently. How is the system doing with one stick removed?
 


Working fine for the moment, but it's too soon to tell (I've seen it bsoding after a few days of working non stop).
 


Hmm... If it seems fine try alternating the slots in which the single stick is inserted. If you find you suddenly bsod after swapping slots then there is a good chance a slot might be bad.
 


Some of these details are history for myself... Using a single sodimm, placed on the lower memory slot it eventually BSOD, attached are the details. Same issue in the dump?

After the bsod, I placed that same sodimm in the other slot (the upper one). We'll see how that fares.

Cheers
 


Attachments

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8039aeb19c5, 0, 41}

Probably caused by : win32k.sys ( win32k!UserProcessDwmInput+168 )

Followup: MachineOwner

Hi,
the above had a exception code of 0xC0000005 which means a memory access violation occurred.
Causes:
Faulty device driver or system service. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

See how you go now you've changed slots. If you don't see a bsod then it could that the slot was/is bad..
 


Same as the above. Did you try swopping sticks to see if the bsod still occurred? (in the same slot of course)

Plus can you check that the bsod's still continue if you remove this driver:

rimssne64.sys Thu Oct 21 02:33:06 2010: RICOH Memory Stick driver
 


Last edited:
For the reference, I'm buying a new laptop since the bsods never went away.
Kemical, thank you for trying to help me out.

Thread closed.
 


Back
Top