BSOD on startup; PAGE_FAULT_IN_NONPAGED_AREA

[w1z4rd156]

Hi!
Had this problem for about a week now, however it has been getting worse recently, last week my laptop blue screened once or twice, and this morning it happened within 2 minutes of booting up, every time I restarted it. I can start my PC and log into windows, and sometimes get a few programs running, but not enough time to run any diagnostics or even view log files. I can't start the machine in safe mode either, it crashes and restarts while loading drivers.

System Specs:
Dell Studio 14z
Intel duo (? -- I'll double check when I get home)
5GB PC3 8500s RAM, (I know weird number, not sure how they got that)
Windows 7 home premium x64
Can't think of anything else off the top of my head that could be relevant.

I've done a little research on it, seems like its either:
A) bad hardware, RAM/HDD/L1/L2 cache or processor itself. or,
B) bad driver. (I'm leaning towards this problem)

I'm up at school at the moment, so I don't have direct access to it at the moment, but I have extra PC's that I can use at home to post/run some HDD tests on if needed. I can probably get the logs from the laptop HDD as well via that.

Here's what I have tried doing so far:
-Ran Windows memory check tool, no RAM errors (not Memtest86, I know, but I don't have a bootable USB key with memtest on it, or a CD drive for my laptop. I should have one by tonight though, so I'll be running that overnight, will post results tomorrow.)

-Removed the single 4GB RAM module I could find on my PC and restarted with just the 1 GB that's somewhere else on the motherboard, same results.

-Removed the HDD to back up some data and am now running chkdsk on it from my desktop.

-Tried system restore, but I get a different bluescreen, didn't think to take a picture of it, I'll post it when I get home tonight. IIRC it was a IRQL_NOT_LESS_OR_EQUAL error.

Can't get the crash dump files from here, but I'll try and post them when I get home tonight, but here's the bluescreen info:
------------------------------------------------------------------
...blahblahblah shutting down your computer...

cpuz135_x64.sys

PAGE_FAULT_IN_NONPAGED_AREA

blah blah blah

***STOP: 0x00000050 (0xffffffff00000028, 0x0000000000000000, 0xfffff8800A414603, 0x0000000000000005)

*** cpuz135_x64.sys - Address FFFFF8800A414306 base at FFFFF8800A412000 datestamp 4e779f0d

Thanks for your help!

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to 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.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

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.

 

[w1z4rd156]

Here's the Windows\minidump folder.

Update: Ran CHKDSK and came up with 'some errors' that got fixed. Going to try & see if that fixed anything & then run Memtest86 for a while.

 

[zigzag3143]

Here's the Windows\minidump folder.

Update: Ran CHKDSK and came up with 'some errors' that got fixed. Going to try & see if that fixed anything & then run Memtest86 for a while.

Every one of these was Related to cpuz135_x32.sys CPUID service from CPUID. I would remove it..


Also needing attention

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

* Did you run a FULL SYSTEM scan with Malwarebytes?

 

[w1z4rd156]

Plugged the HDD in and I'm now posting from my laptop... so far no crashes, I'm going to take your advice and remove DemonTools & Avast.

 

[w1z4rd156]

Update:
Ok, so my laptop seemed to be running fine, I uninstalled Demontools and Avast, and restarted after a few hours of sitting around. Windows had a few updates to install and I let it do those. I came back, logged in and got the same blue screen, I've attached the .dmp file. I searched my HDD and Registry for CPUz135_x64.sys, but couldn't find anything relating to it.

On another note, everything seems sluggish and slow to respond. I started up Minecraft a bit ago and was getting 1-2fps, I normally get 40+. And my processor is idling at 100%.

I restarted and windows prompted me to do a system restore, which I accepted & has got me back to here. Hasn't BSOD'd yet.

Here are the updates windows installed:
Security Updates for Windows 7 x64 based systems:
KB2621440
KB2641653
KB2665364
KB2667402

Update for Windows 7 x64 based systems
KB2639308

Windows Malicious Software Removal Tool x64
KB890830

 

[w1z4rd156]

So, new problems... I ran the dell diagnostics, everything seemed fine, I left the room while the extended memory tests were running and came back to a powered down computer... First sign of trouble.

I was planning on upgrading to win 7 ultimate soon anyway, so I formatted the drive and started a fresh install, which installed without any problem, but now I'm experiencing random shutdowns, very quickly upon startup.

Going to see if I can run memtest for a while and see if that turns anything up...

 

[zigzag3143]

So, new problems... I ran the dell diagnostics, everything seemed fine, I left the room while the extended memory tests were running and came back to a powered down computer... First sign of trouble.

I was planning on upgrading to win 7 ultimate soon anyway, so I formatted the drive and started a fresh install, which installed without any problem, but now I'm experiencing random shutdowns, very quickly upon startup.

Going to see if I can run memtest for a while and see if that turns anything up...

That shut down is beginning to feel like heat.

 

[w1z4rd156]

That was my thought too.
I cleaned out the heat sinks & pointed my desk fan at it.
Running memtest86+ 4.2 now, it ran for a full pass with only the one GB stick in, and then powered down. Shut down at test #4 with all 5GB installed. I can't find where the other 1GB stick is either, unfortunately, so I can't remove that.

 

[w1z4rd156]

Re-seated the RAM and windows is now running...but everything is incredibly slow, and CPU usage is still at 100%. Haven't updated drivers yet, but this seems really strange, I've never had a pc be this slow after a fresh install of windows. Is it possible for a root kit to stay present through a format?

 

[zigzag3143]

Re-seated the RAM and windows is now running...but everything is incredibly slow, and CPU usage is still at 100%. Haven't updated drivers yet, but this seems really strange, I've never had a pc be this slow after a fresh install of windows. Is it possible for a root kit to stay present through a format?

There is even malware that can reside in MBR, and malware that can jump partitions. I am not a malware expert so perhaps you might ask in the security section here