Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on a new pc

30 Jan 2011   #1
bmori

windows 7 home premium 64bit
 
 
BSOD on a new pc

recently got a new laptop for my wife only to be haunted by the BSOD - tried various things like restoring to factory default and installing software item by item.

recently restored to factory default for a second time and running with hardly any software it crashed with an error today - although not quite a BSOD.

Ran the BSOD program and have attchached a zip file.

If I do
  1. Press Winkey+R (Start > Run…)
  2. Type perfmon /report and press Enter.
I get an error - program not found.

I am running Windows 7 64bit - I have attached a text file of the system info.

Anything hints or tips much appreciated

thanks
Bill


My System SpecsSystem Spec
.
30 Jan 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bmori View Post
recently got a new laptop for my wife only to be haunted by the BSOD - tried various things like restoring to factory default and installing software item by item.

recently restored to factory default for a second time and running with hardly any software it crashed with an error today - although not quite a BSOD.

Ran the BSOD program and have attchached a zip file.

If I do
  1. Press Winkey+R (Start > Run…)
  2. Type perfmon /report and press Enter.
I get an error - program not found.

I am running Windows 7 64bit - I have attached a text file of the system info.

Anything hints or tips much appreciated

thanks
Bill

Hi Bill and welcome


there were no DMP files in the upload please try this method.

If you wish to have others 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.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.
My System SpecsSystem Spec
30 Jan 2011   #3
fimble

windows 7 ultimate
 
 

If you don't find a minidump folder or .dmp files inside check you have minidumps enabled.

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.

The .dmp files are located at C:\Windows\Minidump. Until a .dmp file is generated, the Minidump folder may not exist.

And as zigzag says: Copy the .dmp files to a new folder on your desktop. Zip up that folder and attach to a post.
My System SpecsSystem Spec
.

31 Jan 2011   #4
bmori

windows 7 home premium 64bit
 
 

Many thanks guys for all your help and info...........as it happens the pc was configured to auto restart and not to do a minidump. So since all this is after the event I'll have to go back to sleep until it crashes again.

If it hasn't crashed again in the next couple of days I'll install the latest version of Skype - that always seems to do it even if it's not running.
My System SpecsSystem Spec
31 Jan 2011   #5
jcgriff2

Windows 7 - Vista
 
 

Hi -

You have an old installation of ESET installed - v4.2.67.10.

Update ESET installation to v4.2.71.2 - ESET Downloads

Regards. . .

jcgriff2

`
My System SpecsSystem Spec
31 Jan 2011   #6
bmori

windows 7 home premium 64bit
 
 

will do JC - I have downloaded the latest rev - the installed version is less than one month old do you think that this might have been a contributer?

cheers
Bill
My System SpecsSystem Spec
31 Jan 2011   #7
jcgriff2

Windows 7 - Vista
 
 

Hi -

The aged ESET installation definitely could have contributed to BSODs/ app crashes. The version you had installed was from April 2010 -
Code:
shellext        4.2.67.10       04/11/2010 17:19
ekrn            4.2.67.10       04/11/2010 17:15
egui            4.2.67.10       04/11/2010 17:15
eguiscan        4.2.67.10       04/11/2010 17:17
eguiamon        4.2.67.10       04/11/2010 17:13
eguiemon        4.2.67.10       04/11/2010 17:15
eguidmon        4.2.67.10       04/11/2010 17:14
eguiepfw        4.2.67.10       04/11/2010 17:16
eguiUpdate      4.2.67.10       04/11/2010 17:20
eguiMailPlugins 4.2.67.10       04/11/2010 17:19
Time will tell if the updated ESET installation helps with your BSODs or not.

Given brand new system, let Driver Verifier do some work for you. If BSODs are software related, Driver Verifier will flag the 3rd party driver responsible and force BSOD. Let it run for 36 hours minimum or BSOD, whichever comes first -

Driver Verifier - sysnative.com - MVP

If D/V BSODs your system, please re-run --> https://www.sevenforums.com/crashes-d...tructions.html

Regards. . .

jcgriff2

`
My System SpecsSystem Spec
31 Jan 2011   #8
bmori

windows 7 home premium 64bit
 
 

Hi JC, upgraded to the latest version of nod and set all the parameters for the driver verifier.
How do I know if the verifier is running and when its finished? There are not many non microsoft drivers on the new pc.
I also did a Mcafee clean up - there were a few bits left after the uninstall.

many thanks for all your help - much appreciated
Bill
My System SpecsSystem Spec
02 Feb 2011   #9
Jonathan_King

Windows 7 Professional x64
 
 

To see the status of driver verifier, open a command prompt and enter verifer /query. If it gives a list of drivers being verified, you know it's running.

When driver verifier finds an error, it will cause a BSOD; if that happens, upload a new jcgriff2 report, and turn off verifier. If you go 24 hours with verifier running, and no BSOD, go ahead and turn it off.
My System SpecsSystem Spec
03 Feb 2011   #10
bmori

windows 7 home premium 64bit
 
 

thanks Jonathan I did that when I started it running but the screen flashed by so quick I couldn't read it - as an aside do they still drink pabst blue ribbon in rednecksville

cheers
Bill
My System SpecsSystem Spec
Reply

 BSOD on a new pc




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 23:14.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App