New computer, BSOD every day, unknown reason. multiple errors.

[TASSADAR]

64 bit original full retail windows 7 ultimate system installed on brand new hardware < 3 months. completely new computer and I can't get it to stop BSOD. What might be my problem? I was completely fine on my old computer until a power outage fried all my components, I went out and bought a WHOLE new computer. I don't know what could be wrong. Anybody got any ideas?

Included is a zipped folder of my BSOD reports and my perfmon.

-Tassadar

 

[JMH]

Tassadar

Included is a zipped folder of my BSOD reports and my perfmon.

* No folder included...

* Assuming that your computer is new & under warranty {approx 3 months old }

IMHO -
We volunteers should not be putting at risk the rights,YOU, the consumer has under that warranty.

Therefore I would strongly suggest that you should seek advice asap.

 

[zigzag3143]

I second JMH

 

[TASSADAR]

You see everybody, the errors have become so frequent, I have resorted to installing Ubuntu 11.04 on one of my other HDDs just to post this comment. I have no idea what the problem is and have no patience to speak with somebody over the phone. If there is ANY way to get this under control, I will try to repost the zip folder so you guys can take a look.

 

[TASSADAR]

Windows_NT6_BSOD_jcgriff2.zip

This is the upload link. I am sorry to not have posted it in the first comment but this is what I have compiled. I am open to all suggestions. I have installed the hotfix and am running it right now.

 

[zigzag3143]

IF YOU ARE NOT GOING TO RETURN THIS COMPUTER FOR WARRANTY SERVICE (though I would)


These were caused by a memory exceptions. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

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



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html




Also I would run the update readiness tool then update to SP-1


Ensure you install the correct 64 or 32bit option for your system)

Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

ISC Diary | Windows 7 / 2008 R2 Service Pack 1 Problems

links courtesy jmh

 

[TASSADAR]

Ok so I ran the Driver Verifier, and the Memory Check. Check was clean. I ran the verifier and received this BSOD about 45 minutes

"A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

UNEXPECTED_KERNEL_MODE_TRAP

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8,
0xfffff980165f4fb3)

*** ntoskrnl.exe - Address 0xfffff800030bf5c0 base at 0xfffff8000304f000 DateStamp
0x4e02aa44
"

 

[zigzag3143]

Ok so I ran the Driver Verifier, and the Memory Check. Check was clean. I ran the verifier and received this BSOD about 45 minutes

"A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

UNEXPECTED_KERNEL_MODE_TRAP

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8,
0xfffff980165f4fb3)

*** ntoskrnl.exe - Address 0xfffff800030bf5c0 base at 0xfffff8000304f000 DateStamp
0x4e02aa44
"

Again we need the actual dmp file to examine