BSOD with Ethernet Cable/Wireless Adapter plugged in

[robozman]

I have been having BSOD problems ever since I bought this computer (almost a year ago)
Originally it would BSOD on File > Open but I worked around that.
Not It BSODs when ever I either boot it up with some type of internet adapter plugged in, or plug some sort of internet adapter after I turned it on. If I plug it in after it has be turned on, it will run for maybe 10-20 min, and then BSOD.
I was unable to retrieve a System Health Report
I received the error:
Error:

An error occured while attempting to generate the report.
The system cannot find the path specified.
This may relate to me being in safe mode but I'm not sure.

Windows 7 . . .
- x64bit
- Windows 7 Home Premium OEM
- Coming up on 1 year
- 1 year also
- Gateway DX 4840
- Intel Core i3 CPU 550
- 8192mb Ram

 

[zigzag3143]

I have been having BSOD problems ever since I bought this computer (almost a year ago)
Originally it would BSOD on File > Open but I worked around that.
Not It BSODs when ever I either boot it up with some type of internet adapter plugged in, or plug some sort of internet adapter after I turned it on. If I plug it in after it has be turned on, it will run for maybe 10-20 min, and then BSOD.
I was unable to retrieve a System Health Report
I received the error:
Error:

An error occured while attempting to generate the report.
The system cannot find the path specified.
This may relate to me being in safe mode but I'm not sure.

Windows 7 . . .
- x64bit
- Windows 7 Home Premium OEM
- Coming up on 1 year
- 1 year also
- Gateway DX 4840
- Intel Core i3 CPU 550
- 8192mb Ram

Nothing in the compressed file please try this method

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.

 

[robozman]

"\Windows\Minidump\" Attached

Thanks For Your Reply,
I zipped up the "\Windows\Minidump\" folder and attached it.

 

[JMH]

> AVG can be a contributing cause of BSOD'S.
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST.

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

> These crashes were caused by a memory exception. (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[robozman]

AVG/Memtest/Verifier Results

Uninstalled AVG (No help)
Installed Security Essentials
Ran memtest to 81% complete of the test (Got Kinda Bored Cause I was Getting To The Point Of 1 test per hour, and you did say 5 or 6 passes, what ever that means). No errors.
Set up Driver Verifier.
Computer Freezes Before it can BSOD (Completely Freezes and requires a force restart NO BSOD)
Is a dmp file still created in this kinda "crash"? Or do dmp's specifically relate to BSOD's?
Thanks For The Help

 

[zigzag3143]

Uninstalled AVG (No help)
Installed Security Essentials
Ran memtest to 81% complete of the test (Got Kinda Bored Cause I was Getting To The Point Of 1 test per hour, and you did say 5 or 6 passes, what ever that means). No errors.
Set up Driver Verifier.
Computer Freezes Before it can BSOD (Completely Freezes and requires a force restart NO BSOD)
Is a dmp file still created in this kinda "crash"? Or do dmp's specifically relate to BSOD's?
Thanks For The Help

The DMP file with verifier runnning may contain the name of the offending driver. Upload it to us

 

[robozman]

Thanks a lot for your help, but I instead decided to do a fresh installation of Ultimate so....
But Thanks A Lot Anyway. I'll be sure to come here if I have any more trouble.

 

[zigzag3143]

Thanks a lot for your help, but I instead decided to do a fresh installation of Ultimate so....
But Thanks A Lot Anyway. I'll be sure to come here if I have any more trouble.

Good idea and good luck

 

[JMH]

Thanks a lot for your help, but I instead decided to do a fresh installation of Ultimate so....
But Thanks A Lot Anyway. I'll be sure to come here if I have any more trouble.

Wise person indeed.
Often a Clean Install is the quickest & neatest way to go...
Good luck!