Connecting to the Internet Causes BSOD/CRASH

okay well atleast we are making progress software or hardware they can be fixed, software will be updating/removing bad drivers etc and hardware replacing (normally).

I will double check to make sure it is not the wireless connection.

Just as past reference we tried seatools last time but it didn't work. it instructed me to instal .NET v4 and i did. However it still pop'd up saying i need to install .NET v4. I will retry though. oh i have done memtest in the past, however only 4 passes and no errors. I will run that though for 8 passes tomorrow for i am busy for i am busy for most of the day tomorrow.

Yet again thanks for your time and patients!

The attached DMP file is of the CRITICAL_OBJECT_TERMINATION (f4) bug check.

*This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.*It's a verifier enabled dump however it's failing to detect a device driver in violation, therefore this is likely a hardware issue at this point.

1. Are all of your network drivers up to date via the manufacturers website?
2. Are you connecting from a wireless adapter or directly from an ethernet cable?

If the answer is yes to 1 and you've already tried connecting directly via ethernet to rule out the adapter....

Let's go ahead and start with a Memtest for NO LESS than ~8 passes (several hours). If it goes at least 8 passes without any errors whatsoever, move onto chkdsk and Seatools:

Memtest86+:

Download Memtest86+ here:

http://www.memtest.org/

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

Chkdsk:

Chkdsk:There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:

    Open the "Computer" window

    Right-click on the drive in question

    Select the "Tools" tab

    In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

http://www.seagate.com/support/downloads/seatools/

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick

i dont know but for some reason when i checked the computer properties it said i needed 400mb (this is in the same section/area where you can disable automatic restart so i did what it said so i just click the automatic setting of allocating virtual memory i think it was not so sure but since then i forced it to crash and i got this minidump file upon bluescreen when connecting to the internet, here is the file: https://skydrive.live.com/redir?resid=334CE6A169DD2E62!920&authkey=!ADUTHuveu_2z86U&ithint=file%2c.zip

If there are no dump files being generated during a crash, especially with verifier enabled, we likely have an underlying hardware problem.

I am not understanding correctly either, so can you please elaborate on whether or not you've crashed since enabling verifier and attempted to connect to the internet? If so, was a MEMORY.DMP generated in C:\Windows or a .DMP generated in C:\Windows\Minidump?

Regards,

Patrick

okay i went into computer properties and played around with a few settings and it just blue screen'd and dump'd sucessfully looking for the dump file now. It produced a dump file: https://skydrive.live.com/redir?resid=334CE6A169DD2E62!920&authkey=!ADUTHuveu_2z86U&ithint=file%2c.zip