Windows 7: Random Bluescreens & Event ID 7001 & 7023 Maybe Freezing my Computer!

I have just freshly installed windows as i just formatted my drive and started from new now i have downloaded all the latest drivers for my computer least i hope i have but i seem to be getting BSOD now and then as i used to get BSOD before so i thought maybe a format will fix that well seems not as i have just experienced 2 BSOD and sometimes some freezes that i have to force restart and also when i was playing a game i alt tab out of it for a bit as i was checking guides after a few times doing that it just sat at a black screen and done nothing.

I have posted the dump file and perfmon file in the zip file below.



Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64. - the original installed OS on the system? Yes. - an OEM or full retail version? Brought by a computer store that custom built my computer. - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? The computer was purchased on April 26th 2012, So hardware is pretty new. - What is the age of OS installation = Was just previously reinstalled after a format.

Hello Verenios and welcome to Sevenforums.

BSOD Report

Update of drivers ($driverq_v)
Driver Reference Table - arc.sys
Driver Reference Table - adpu160m.sys
Driver Reference Table - nfrd960.sys

Arc.sys and adpu320.sys are both a part of the Adaptec miniport drivers. Look for new and updated drivers at the link below. As you can see, they're both from 2007, which might conclude that they're incompatible with some of the Windows 7 modules.

IBM Support Portal: Support home

Adaptec - Technical Support

SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.


Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

MemTest86+

Dumps might point to hardware looking at your SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
error message. A good place to start is the Memtest86+, which would test your RAM sticks. Do 7-8 passes and post back your results.

Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.

Thank you for your reply, I have looked into this and for the drivers i have absolutely no clue what driver or what to download i have looked on the sites and that's were i am lost on what to download..

Try to use the Intel Driver Update Utility and see what it's pointing at. Sometimes it can be quite useful detecting what specific drivers you need.

Intel® Driver Update Utility

You might need to hit Ctrl + F5 once or twice in order to make it work.

Best Regards,
Frederik.

I went to the intel site and tried twice and twice i was struck down by a BSOD but showed no reason why so i used WhoCrashed App and it says this

On Tue 26/06/2012 7:01:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-13478-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800A9EE912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED

Could it be since its Intel that its doing the BSOD since my comp is AMD?

I don't think so no.
cpudrv64.sys is the System Requirements extension, the one Intel Driver Utility was using. Oh well, let's skip the driver updates for now, just because the driver is old, doesn't mean it doesn't work - we might ignore it for now.

Can you upload the new .dmp?

Best Regards,
Frederik.

Ok here is the new dump file.

Thanks a lot Verenios.
You can proceed to this part.

Best Regards
Frederik.

Okay i did the SFC /scannow

And these are the results as it poped up saying i did have corrupt files and that windows has repaired them i dont know if i should post it but here they are.

If you know what was corrupted could you point it out so i know for sure what i did wrong so next time i can be sure not to make that same mistake. lol

Hey Verenios,

It's definitely great news and we should name it an achievement that sfc /scannow actually found something. Looking at a log file, is like finding a specific person in Hong Kong. I do not know at this time what is fixed, but I will look further in it and report if I found something.

It's great news.

Best Regards,
Frederik.