It is my feeling that the most likely cause is memory. Yes, you can possibly solve the problem by fixing any
memory problems. However, ignore the other problems and another BSOD is a very strong possibility.
If overclocking restore normal settings
Result:
Result: I'm not overclocking
SFC /scannow
Result:
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
I've attached this file.
Download memtest86 and test RAM
RAM - Test with Memtest86+ - Windows 7 Forums
Result: This one has been tricky. I've ran the memory test by USB, but after 20 minutes my laptop shuts down. No memory problems were caught by that time.
I've tried to figure out if there are any settings that might be causing this, but I don't know where they
would be...the OS hasn't launched by this stage, so where would I look?
Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.
Results:
This has been really tough. I'm not sure how to assess what these files are and whether they are needed. I've
looked up a number of these files but I'm honestly not sure how to proceed. Do I replace them? With what, and
how do I know the replacements are any better?
I'm a bit cautious about replacing files like this when I don't really understand what they do. I'm happy to
do the work but I'd appreciate some advice.
mdmxsdk.sys Mon Jun 19 17:26:59 2006
This appears to be a modem component. Apparently is is needed to prevent new installation of existing
hardware on bootup.
secdrv.SYS Wed Sep 13 09:18:32 2006
Appears to come from game installation, possibly for anti-burning protection.
peauth.sys Mon Oct 23 04:55:32 2006
This looks to be a device drive that's installed as part of the Windows OS.
crcdisk.sys Thu Nov 02 04:52:27 2006
Apparently written by Microsoft.
eabfiltr.sys Thu Nov 30 11:24:57 2006
This appears to be a keyboard driver in Hp laptops.
SynTP.sys Fri Jan 12 16:06:00 2007
Found in laptops with touchpads, which mine has.
rimsptsk.sys Tue Jan 23 02:40:19 2007
Driver file from the company REDC. Some websites suggest this may possibly be a malicious file.
rixdptsk.sys Tue Jan 23 03:03:27 2007
Apparently a trustworthy file from Microsoft.
PxHelp20.sys Fri Feb 02 16:23:57 2007
Related to DVD burning. My latop can burn CDs.
nvsmu.sys Fri Feb 16 10:50:31 2007
Something to do with graphics
rimmptsk.sys Sat Feb 24 00:42:21 2007
Another REDC file. Digitally signed by Microsoft Windows Hardware Compatibility Publisher
btwavdt.sys Mon Feb 26 00:06:24 2007
Users report this is related to Skype or bluetooth. I've had no problem with Skype at all and don't use
bluetooth.
btwrchid.sys Mon Feb 26 00:08:38 2007
a blueooth driver
nvmfdx32.sys Tue Mar 06 14:29:33 2007
Several website list this as safe. I'm not sure what it's related to.
btwaudio.sys Thu Mar 29 14:51:42 2007
bluetooth software
spldr.sys Thu Jun 21 20:29:17 2007
MS Windows security loader. I can't really tell what this does.
nvlddmkm.sys Mon Jul 09 07:19:30 2007
Something to do with graphics. There are suspicious reports about this but I don't understand them.
xaudio.sys Thu Oct 18 18:36:53 2007
Conexant audio system driver file
HSX_CNXT.sys Thu Nov 01 20:46:56 2007
A modem driver
HSXHWAZL.sys Thu Nov 01 20:47:51 2007
Apparently an MS file.
HSX_DPV.sys Thu Nov 01 20:50:39 2007
Also a trustworthy Microsoft file.
Uninstall your current Anti Virus and replace with Microsoft Security Essentials.
www.microsoft.com/Security_Essentials/
Result:
I can't do this unfortunately, as my laptop blue screens within seconds of normal mode, so I only really
have safe mode to play with. I've not been able to install this program.
I should add here, I think the anti-virus software is a serious candidate for causing these problem. I had Norton pre-installed when I bought this laptop. It expired at pretty much the exact same time this started happening. Could we focus on this? It might save a lot of other work.