bsod dump files

here is a link of the archived minidump folder (i tried attached but it said invalid file)
storage.to - Download
i get this bsod's at random i could say..could any of you guys help me figure out what the problem is?

i have the x64-bit version of win7..on a laptop msi gx623

gigimasinuta said:

here is a link of the archived minidump folder (i tried attached but it said invalid file)
storage.to - Download
i get this bsod's at random i could say..could any of you guys help me figure out what the problem is?

i have the x64-bit version of win7..on a laptop msi gx623

Click to expand...

Please ZIP up the minidump folder contents and upload the zip archive here. That other site makes it hard work to get to your RAR.

gigimasinuta said:

here is a link of the archived minidump folder (i tried attached but it said invalid file)
storage.to - Download
i get this bsod's at random i could say..could any of you guys help me figure out what the problem is?

i have the x64-bit version of win7..on a laptop msi gx623

Click to expand...

View attachment 28873
Gigima... Open a reply to this tread and click on the paper clip. circled in snip. use that window to upload your zip file. after uploading to this window. close the window and click on the down arrow beside the clip and select your attachment. good luck to you with this problem and welcome to Seven forums!

View attachment 28887 ok it worked now..thank you for the explination ..here it is..earlier it said invalid file..it had the rar extension then too

bump..really sorry for this..but i see that now my topic is not on the first pages ..so i think it may pass without anyone answering it can somebody help me please?

These are not simple.

4 out of 6 are memory related, in the sense that the contents of memory are not what they should be, for reasons currently unknown. It could be a bad driver corrupting memory or even bad hardware.

One of these appears directly attributable to fspad_wlh64.sys, the touchpad driver.

The last is your video driver - atikmdag.sys - being stuck in some sort of endless loop, either because of a bug in the driver or something to do with the video hardware.

There's a natural tendency to assume that all these crashes are somehow linked by a single underlying cause, but that may not be the case. My gut feeling is that at least the touchpad crash is different, and the video one may be unrelated as well.

Suggestions:

- Update the ATI video drivers first.
- Update the touchpad driver or deactivate the touchpad if you're not using it.
- If crashes persist, come back so that somebody can explain how to use the driver verifier to work out what driver may be corrupting memory.

ok..thank you very much for the answer..i will try do to what you said..i hope the crashes stop..

btw..can anyone help me..my video card is ati radeon hd 4670.the right driver from the ati site is the driver for the 4600 series?

hi..i did what you said..i didn't get any other bsod until yesterday but also i didn't spend that much time at the computer like before..yesterday i got another one View attachment 30230 can you please tell what is this one about? and what to do next?

H2SO4 said:

- If crashes persist, come back so that somebody can explain how to use the driver verifier to work out what driver may be corrupting memory.

Click to expand...

hours later it crashed again..can somebody explain to me how to use the driver verifier, to see witch one causes me problems? please

gigimasinuta said:

H2SO4 said:

- If crashes persist, come back so that somebody can explain how to use the driver verifier to work out what driver may be corrupting memory.

Click to expand...

hours later it crashed again..can somebody explain to me how to use the driver verifier, to see witch one causes me problems? please

Click to expand...

"Driver verifier" (DV) is a type of behaviour by the OS kernel which is disabled (off) by default. Instead of treating drivers as trusted code, once DV is enabled the kernel starts scrutinising the activities of the specified drivers much more closely, at the cost of degraded performance. The aim is to detect problems in drivers right at the point where they occur, as opposed to later after the damage is already done and it's hard to trace back to the original culprit.

To enable driver verifier:
- Run a CMD prompt as admin (right-click the CMD shortcut, run as admin).
- Type this command: verifier /standard /all
- Reboot
- Wait for the next BSOD, then zip and upload the dump.

Analysis of that next dump may prove more conclusive. To disable verifier once you're done with the troubleshooting:

- Run: verifier /reset
- Reboot

I can not find a dump file for me to look at. Where would that be any one?

View attachment 30558

this is the zipped dump filed from two posts ago..meanwhile..i activated that verifier..but anything on my computer started moving slower..really noticeable(has this happened to anyone else? i am not sure that this is the cause..but after the reboot it was moving painfully slow..until this, it has worked like a charm..again, there could be another software that caused this..i am not sure..)..i restored to a previous point..no crashes in the last 2 days..

gigimasinuta said:

View attachment 30558
..i activated that verifier..but anything on my computer started moving slower..really noticeable(has this happened to anyone else?

Click to expand...

Yes, running with all verifier settings enabled will make your machine perform like an arthritic slug. That's why it's disabled by default.

If you simply can't stand it, it's possible to run with a subset of those extra driver checks (type VERIFIER /? to see the options), but in your case the potential range of issues is so broad that doing without any of the extra scrutiny runs the risk of missing something important.