treaz
New Member
- Joined
- Jan 10, 2014
- Messages
- 16
- Thread Author
-
- #1
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.
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...
treaz
New Member
- Joined
- Jan 10, 2014
- Messages
- 16
- Thread Author
-
- #26
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
After the bsod, I placed that same sodimm in the other slot (the upper one). We'll see how that fares.
Cheers
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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..
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
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:
Similar threads
- Solved
- Replies
- 3
- Views
- 2K
- Replies
- 4
- Views
- 4K
- Replies
- 1
- Views
- 3K
- Solved
- Replies
- 4
- Views
- 6K
- Replies
- 1
- Views
- 1K