random BSOD's and cant do .dmp ntoskrnl.exe ( nt+7cc40 ) problem

[rugged04270]

BSOD at random times, seems to occur more often though, when referencing hard drive memory.
My first problem I need help with is when i try to access a .dmp file i get told something about symbols referencing the following:
ntoskrnl.exe ( nt+7cc40 )
any idea how to fix it?

 

[rugged04270]

PS. sorry i am not following the exact rules regarding the whole .dmp file thing but i dont know how to do that...

 

[zigzag3143]

BSOD at random times, seems to occur more often though, when referencing hard drive memory.
My first problem I need help with is when i try to access a .dmp file i get told something about symbols referencing the following:
ntoskrnl.exe ( nt+7cc40 )
any idea how to fix it?

I would be happy to show you how to get WinDbg working right after we fix you.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[rugged04270]

Attached is the requested zip file.
Also: not overclocking, with my system, and for what i do with it i dont see the point.

 

[zigzag3143]

Attached is the requested zip file.
Also: not overclocking, with my system, and for what i do with it i dont see the point.

Memory management Related to pctNdis-PacketFilter64.sys NDIS - Packet Filter from PC Tools. I would remove it

Uninstall tool

 

[rugged04270]

Attached is the requested zip file.
Also: not overclocking, with my system, and for what i do with it i dont see the point.

Memory management Related to pctNdis-PacketFilter64.sys NDIS - Packet Filter from PC Tools. I would remove it

Uninstall tool

i used the program you linked, and uninstalled the program as well, how do i tell if that got rid of the packet-filter?

 

[rugged04270]

So I did what you said, and removed the file, at least I think I did, but my computer just crashed again, what now?

 

[zigzag3143]

So I did what you said, and removed the file, at least I think I did, but my computer just crashed again, what now?

The usual, upload the dmp file.

 

[rugged04270]

Attached is the error log, could this be caused by a bad video card?

 

[zigzag3143]

Attached is the error log, could this be caused by a bad video card?

There has been no indications (even indirect) of that.


Just noticed your Zone Alarm. That should be removed and replace with MSE.

http://download.zonealarm.com/bin/free/support/cpes_clean.exe


Microsoft Security Essentials - Free Antivirus for Windows

 

[rugged04270]

Are you sure that will help? I used to run norton and i still had this problem, I don't think MSE will change that.

 

[cluberti]

Both of these dump files point to memory corruption as the culprit. That doesn't mean necessarily you have bad RAM, but it does mean someone's corrupting data being placed into a CPU's register (either to/from disk or to/from RAM). When did this start, and does it happen when you're booted in safe mode at all?

 

[rugged04270]

Both of these dump files point to memory corruption as the culprit. That doesn't mean necessarily you have bad RAM, but it does mean someone's corrupting data being placed into a CPU's register (either to/from disk or to/from RAM). When did this start, and does it happen when you're booted in safe mode at all?

It has been happening since i built it, and i have never started it in safemode, as i dont really know what safe mode is/does.

 

[cluberti]

Safe mode loads Windows, but without drivers and without loading most services/startup items. If you press F8 right before the Windows "splash screen" during boot, you can select "Safe Mode" from the boot options.

 

[rugged04270]

Safe mode loads Windows, but without drivers and without loading most services/startup items. If you press F8 right before the Windows "splash screen" during boot, you can select "Safe Mode" from the boot options.

so if i boot in safe mode, i just use the computer as normal for a while and see if it happens?

 

[cluberti]

As much as possible - you won't have network access, and a lot of services aren't running. It's more a means to test to see if you have driver or 3rd party software/services problems.

 

[rugged04270]

As much as possible - you won't have network access, and a lot of services aren't running. It's more a means to test to see if you have driver or 3rd party software/services problems.

ok, will do in the AM, i have to burn mem-test to a cd to run it right?

 

[cluberti]

No, not at all. This is something you can do just with your keyboard - specifically the F8 key .

 

[rugged04270]

No, not at all. This is something you can do just with your keyboard - specifically the F8 key .

to run the Mem-test program? i thought f8 was just to get me to safe mode

 

[cluberti]

If you want to burn test your RAM beforehand, yes, you'd need to burn the test program to a CD/DVD and boot from that.