BSOD while plugging USB stick

Please follow all suggestions posted in both threads. It is impossible for us to assist you if we do not know what you have and have not done.

In your next reply I would like to see;

• Have you installed Service Pack 1? If so, did you encounter any problems?
• What AV are you currently using and which one originally came with your machine?
• Please attach the CBS.log file created by running SFC /SCANNOW.
• Please attach the Memorydump.zip via DropBox as the attachment is to big to attach here at SF.
• Have you tried installing the latest drivers? If so, have you removed the old leftovers by running Driver Sweeper?

Good luck and keep us posted,
Nommy

Once again read this and follow the directions, all of them, There are blue underlined links, follow or read them too.
The tool will find them. You are at your PC, we can't remoter control it.
Blue Screen of Death (BSOD) Posting Instructions

After you comply them some help can be given.

zino0001 said:

• Have you installed Service Pack 1? If so, did you encounter any problems?

No, There is no SP1 installed.

Then please install it as I described in post #2.
Service Pack 1 updates critical errors and flaws in Windows 7 and we can not guarantee your safety from, for instance, malware if you do not have it installed.

zino0001 said:

• What AV are you currently using and which one originally came with your machine?

how can I findout ?

Open your task bar and click on the upwards pointing arrow. In there you will see icons of programs that are currently running in the background. Hover over all of them to see their names, one should be your AV.
If you found no one then I suspect that you have no AV installed (there was none mentioned in your MSINFO file either), and if that is the case, please follow the following;
Please download Microsoft Security Essentials from here;

1. Download the file and save it to your desktop.
2. Double click the file and follow the on-screen instructions.
3. Restart your machine after installing MSE and please run a full scan and report back anything found.

----------

zino0001 said:

• Please attach the CBS.log file created by running SFC /SCANNOW.

well when I run its just flash on screen and disapeared.

What do you mean? Does Command Prompt close just after you open it, or are you unable to follow the instructions given?

If SFC is unable to run, please run it at boot by following this;
Please use the SFC /SCANNOW command at boot as shown in option one of this tutorial.

   Note

You will need either your original Windows Installation disc or a Repair Disc for this to work.

1. First change the Boot order so that DVD's boot before Windows does.
2. Insert either your installation or repair disc in your machine.
3. Navigate to the System Recovery Options, and once there, click on Command Prompt.
4. In command prompt, please type the following;
   sfc /scannow /offbootdir=f:\ /offwindir=f:\windows
   Replace F: with the letter where Windows is installed on!
5. SFC will now attempt to search for integrity violations and fix those found.
6. Once done, please type "Exit" and hit ENTER to exit command prompt.
7. To restart, remove the DVD and select Restart from the menu.
   
   If SFC found and repaired any violations, please do the following;
8. When restarted, open an elevated command prompt.
9. Type (or copy) the following, this will create a .txt file on your desktop;
   findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
10. In your next reply, please attach this file using the method displayed in this tutorial.

----------

zino0001 said:

• Please attach the Memorydump.zip via DropBox as the attachment is to big to attach here at SF.

CAN'T FIND AS PICTURE SAID

I am aware of this, that's the reason why I clearly described you how to upload your memorydump in post #8.
The SF Diagnostic Tool can't upload that as, as I have already described, it isn't located in the default dumpfile location, and it isn't a usual dump file. It also exceeds the Forums upload restrictions.

Also, do make sure that your Windows is set to create dump files upon BSoD as I have described in post #2.

zino0001 said:

• Have you tried installing the latest drivers?

Yes drivers updated.

Good, have you encountered any problems so far?


Good luck and keep us posted,
Nommy

You can use both option one and option two of this tutorial to configure your system to create dump files.
Please choose for the Small Memory Dump option.

---------

After enabling Windows to configure them, please do the following to create a BSoD on purpose;
Please follow this;

Arc said:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Good luck and keep us posted,
Nommy

zino0001, Just a question if I may.
Are you now running without the mentioned above drivers installed?

And guys just for future reference :) ;

Notice in the third line NMI


That is the reason no dumps were created - :: Non-maskable interrupt ::
There was "no time" to call on the KeBugcheckEx routine to generate a dump file
usually it's due to severe error (usually originates in hardware) this case a memory parity.
I believe the OS didn't even attempt
the create a dump file as it will fail the memory comparison when trying verify the integrity
of the content of the file before writing to disk, this is to avoid data corruption.

For good measure I would test the RAM.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.