PC restarts for no reason (minidumps)

By Jam_Master_K ยท 15 replies
Jan 1, 2007
  1. My HP Media Centre 7635 has developed a habit of restarting itself, all of its own accord. It happens at random times but mainly occurs when the machine has been running for a long period of time.

    I have attached two minidumps that the PC created when it happens and hopefully somebody on here will be able to shed some light on what the problem is as i am a relative n00b to this, and have no idea how to interperet minidumps.

    Any help would be appreciated.

    Thanks in advance.

    Attached Files:

  2. Rik

    Rik Banned Posts: 3,814

    Both of your minidumps point to nt!_KPRCB and i cant seem to find any info on that.

    You may be experiencing overheating, give your case and heatsinks/fans a good dust out and see if that helps.
  3. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Thanks for the reply rik! :)

    But what do you think could be overheating. I initially thought it might be an overheating problem and so i installed temperature monitoring software. And upon looking at the logs from the times when the computer restarts, neither the hard-disks or cpu are reaching very high temperatures when it occurs.
  4. Rik

    Rik Banned Posts: 3,814

    What software did you get?
  5. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Hardware Sensors Monitor 4.2 from http://www.hmonitor.net/.

    It gives a read out of the hard disk/ CPU / Graphics card every 2 seconds or so.
  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Software error of ZoneAlarm


    Both dumps are crashed by ZoneAlarm at the same instruction address. De-install or downlevel ZoneAlarm may resolve the blue screen problem.

    Mini120506-01.dmp BugCheck 1000007E, {c0000005, a8407027, b0c12954, b0c12650}
    Probably caused by : vsdatant.sys ( vsdatant+43027 )

    Mini120806-01.dmp BugCheck 1000007E, {c0000005, a7618027, b8ee2954, b8ee2650}
    Probably caused by : vsdatant.sys ( vsdatant+43027 )

    Timestamp of vsdatant is 4495E11F
  7. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Thats great. I will give it a try thanks.
  8. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    From the stack trace, I find the footprint of Netlimiter and then ZoneAlarm crashed. The culprit maybe either Netlimiter or ZoneAlarm. According to history record, the old version of Netlimiter causes bugcheck code 7E. I searched google about your version of Netlimiter and no hit.

    b0c12a18 8869c6b4 8985bf18 b0c12d00 8869c620 vsdatant+0x43027
    b0c12a1c 8985bf18 b0c12d00 8869c620 8958d008 0x8869c6b4
    b0c12a20 b0c12d00 8869c620 8958d008 00000400 0x8985bf18
    b0c12a24 8869c620 8958d008 00000400 88e21000 0xb0c12d00
    b0c12d00 804eeeb1 8985bf18 8869c620 8869c6fc 0x8869c620
    b0c12dac 805ce794 00000003 00000000 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    b0c12d24 a846ea2b 89611030 8869c620 8985bf18 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
    b0c12d5c a84703d3 00000000 0000040d b0c12da4 nltdi+0x2a2b <-- Netlimiter
    b0c12d70 a8470448 88a1a050 b0c12da4 00000102 nltdi+0x43d3
    b0c12d90 a84704ab b0c12da4 00000000 89737c10 nltdi+0x4448
    b0c12dac 805ce794 00000003 00000000 00000000 nltdi+0x44ab
    b0c12ddc 805450ce a8470458 00000003 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
  9. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    "PC restarts for no reason"

    This is a FASLSE statement!

    There is always a reason for unexpected PC restarts :)
  10. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Hi guys, Sorry to bother you all again and dredge up this old thread but...

    Well the problem hasn't occured in a long time until it happened again this afternoon. I thought i had fixed the problem. :(

    I was wondering, if its not too much bother if somebody could have a look at this most recent minidump attached to this post? And if it is the same problem then i will have to rectify the programs involved again.

    Cheers in advance if anybody can help.
  11. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    Yeah, it's exactly the same problem. Try updating ZoneAlarm, my version is 6.5.737.000 and the vsdatant.sys file is dated Aug 24 2006.

    BugCheck 1000007E, {c0000005, aa401027, b030b954, b030b650}
    Probably caused by : vsdatant.sys ( vsdatant+43027 )
    Image name: vsdatant.sys Timestamp: Mon Jun 19 07:26:23 2006 (495E11F)
  12. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Thank you so much for your help. I really appreciate it. :)

    I have updated my version of ZoneAlarm to version 7.0.302.000, and with that the vsdatant.sys file hase been updated, as i just checked its timestamp and it is: 08 January 2007 22:29:52.

    Hopefully this might rectify the problem.

    Thanks again.
  13. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    Grrrr.......As i mentioned i update the version of Zonealarm to combat the restart problem and it seemed to have worked, but then this morning my computer restarted right after logging into windows on two consecutive occasions, which seems to indicate that it was when one of the startup programs were initiating that the problem occured.

    The Bugcheck code is different this time. :|

    I have attached the two minidumps and if somebody could have a look at them again i would be delighted. I really want to overcome this problem.

    If it involves ZoneAlarm on this occasion i think i am just going to uninstall it and go in search of some other internet security software. :(

    Again, thanks in advance to anybody who can help.
  14. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

  15. Jam_Master_K

    Jam_Master_K TS Rookie Topic Starter

    cpc2004, once again, you have been of great assistance. Thank you very much.

    Thats it, i have had enough of ZoneAlarm and its hassles. I am going to probably give Kaspersky a try.

    Thanks again.
  16. mollusc_limited

    mollusc_limited TS Rookie

    Hi there,

    There's a BIOS setting which could cause the problem.

    Details are outlined in the article here:


Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...