New laptop, getting BSODs

[Lacrimosa]

Ran the system file scan, it says it "did not find any integrity violations".

 

[usasma]

In reference to all those drivers listed in post #14.
This is a consequence of how HP sets up their systems - lot's of extra, unneeded drivers being loaded.

You'll have to determine what storage controllers you have on your system (probably listed in the System Specifications) - and then update those drivers.

Also, you can stop the unused one's from loading. But be sure that they're unused - as unloading the used one's will probably stop Windows from loading (and will require making a System Restore point first, and then having the ability to log into Startup Repair so you can run System Restore (rstrui.exe) if needed).

 

[Lacrimosa]

I just decided to reformat, getting rid of the HP stuff. I just got a BSOD and a system halt again, though. Would storage controller drivers carry over formats like that? Here's the dump, is it the same thing?

 

[usasma]

In general, if a BSOD carries over between formats, then the problem is likely to be a hardware issue. There are several other things that it could be - but the most common is a hardware problem.

FYI - the other stuff is either an installation that does not wipe the hard drive clean - and this could retain sometthing from the previous installation (such as malware) that could continue the BSOD's
Also, an improper installation of Windows (for testing) could have installed something that is incompatible/won't function properly with Windows.

The dump files don't show anything in particular, so I'd start with these hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

If the above tests don't reveal anything, then try these:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

More info on the BSOD here: http://www.carrona.org/bsodindx.html#0x0000007F
In particular:

Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 20:04:25.639 2010 (GMT-5)
System Uptime: 0 days 2:32:09.418
BugCheck 7F, {8, 80050033, 6f8, fffff80002ac012b}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol

 

[Lacrimosa]

Thank you again.
I've run the Memory and HD Diagnostics, both came up with 0 errors.

 

[usasma]

Then it's most likely a hardware problem.
If this is a laptop, there's not going to be much that you can do (outside of the RAM and Hard drive).

Try these 2 free stress tests:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: http://www.mersenne.org/freesoft/

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

 

[Lacrimosa]

Thank you.. will try these as soon as possible.
And I forgot to add to my earlier post.. but I have lost files, apparently because of these BSODs. I was working on a drawing in Paint Tool SAI yesterday, and after the BSOD the file was nowhere to be found. Another time before that, the file I was working on seemingly corrupted and I had no way to retrieve or fix it.