[Crownflame]

All right, done again, here are the results:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 2/8/2012 12:14:20 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: SarahSchowen-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.
216768 file records processed.

719 large file records processed.

0 bad file records processed.

0 EA records processed.

50 reparse records processed.

276568 index entries processed.

0 unindexed files processed.

216768 security descriptors processed.

Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
29901 data files processed.

CHKDSK is verifying Usn Journal...
33662928 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
216752 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
49263586 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

297170037 KB total disk space.
99698544 KB in 136961 files.
87752 KB in 29902 indexes.
0 KB in bad sectors.
329397 KB in use by the system.
65536 KB occupied by the log file.
197054344 KB available on disk.

4096 bytes in each allocation unit.
74292509 total allocation units on disk.
49263586 allocation units available on disk.

Internal Info:
c0 4e 03 00 db 8b 02 00 10 ad 04 00 00 00 00 00 .N..............
b9 08 00 00 32 00 00 00 00 00 00 00 00 00 00 00 ....2...........
30 c7 1f 77 00 00 00 00 50 23 c2 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-02-08T18:14:20.000Z" />
<EventRecordID>4061</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>SarahSchowen-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.
216768 file records processed.

719 large file records processed.

0 bad file records processed.

0 EA records processed.

50 reparse records processed.

276568 index entries processed.

0 unindexed files processed.

216768 security descriptors processed.

Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
29901 data files processed.

CHKDSK is verifying Usn Journal...
33662928 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
216752 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
49263586 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

297170037 KB total disk space.
99698544 KB in 136961 files.
87752 KB in 29902 indexes.
0 KB in bad sectors.
329397 KB in use by the system.
65536 KB occupied by the log file.
197054344 KB available on disk.

4096 bytes in each allocation unit.
74292509 total allocation units on disk.
49263586 allocation units available on disk.

Internal Info:
c0 4e 03 00 db 8b 02 00 10 ad 04 00 00 00 00 00 .N..............
b9 08 00 00 32 00 00 00 00 00 00 00 00 00 00 00 ....2...........
30 c7 1f 77 00 00 00 00 50 23 c2 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

[Advertisements]

OK now lets verify drivers.

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Best Regards

[rshaffer61]

OK now lets verify drivers.

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Best Regards

[Crownflame]

http://www.pcpitstop...?conid=24786471

There you go.

Edited by Crownflame, 08 February 2012 - 03:01 PM.

[rshaffer61]

OK network drivers appear to be up to date according to PC PitStop. Did you update the network driver for the network using DriverMax way back earlier?

[Crownflame]

Yup, I updated ALL of the drivers in those five screenshots I posted, and now scanning with Drivermax says my computer is fully up to date, so I don't think I missed anything there.

[rshaffer61]

Any more BSOD's since everything has been updated?

[Crownflame]

Well, I updated all the drivers between Feb.2 and 3, and then I had the two BSODs I posted on page two on the 6th, but since then I haven't had any issues.

So yes, technically I've had BSODs since I updated everything, but for the past two days I haven't had any issues.

[rshaffer61]

OK please do the following and it may tell us more. I'm glad the BSOD's have stopped for now but lets see if we can see a clearer picture now.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[Crownflame]

Here they all are. A few of them are kinda old though.


On Mon 2/6/2012 6:07:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020612-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA800BE60000, 0x2, 0x0, 0xFFFFFA60010541F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 2/6/2012 6:07:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x521F2)
Bugcheck code: 0xD1 (0xFFFFFA800BE60000, 0x2, 0x0, 0xFFFFFA60010541F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 2/6/2012 7:10:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA800B7E8000, 0x2, 0x0, 0xFFFFFA60010571F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 2/5/2012 6:13:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA800B508000, 0x2, 0x0, 0xFFFFFA60010521F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/2/2012 8:37:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020212-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA80098F8000, 0x2, 0x0, 0xFFFFFA6000E5D1F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/2/2012 1:49:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA800983C000, 0x2, 0x0, 0xFFFFFA6000E5A1F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 1/11/2012 2:50:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0xFFFFFA800969C000, 0x2, 0x0, 0xFFFFFA6000E601F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[rshaffer61]

Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

[jcgriff2]

Hi -

All bugchecks = 0xd1 = improper access of pageable memory (or bad memory)

Windows NT Kernel and Microsoft networking related driver tcpip.sys named as probable cause; both are defaults.

I would suggest running Driver Verifier to see if any 3rd party drivers get flagged -

http://sysnative.com...er_Verifier.htm

Regards. . .

jcgriff2

[Crownflame]

All right, I'm having a hard time finding adequate time to run both of those tests, but I'll do it at the soonest opportunity.

I'm a bit curious about the startup test. First off, I'm not sure which of these are the touchpad or keyboard entries, which you said not to disable, and while it's stupid, I'd rather ask than get it incorrectly and then be stuck.





Secondly, how do I know if I've found the problem (my BSODs have been really random, sometimes happening hours after the computer's been turned on)? And what do I do if the system doesn't boot correctly?

And does that Driver Verifier test run in the background, or what? It says it needs to run like 24 hours, so I'll need to be able to plan whether or not I can use my computer during that time.

[rshaffer61]

Post 6 memtest ran with no errors showing
SFC aka System File Checker ran post 8 with files found
DriverMax ran post 16 and all out of date files updated
Chkdsk ran in post 27 and reran in post 31 with results posted
Now I want to check PSU and HD.

Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions

[Crownflame]

Here's the speedfan.



And for this harddrive thing, I'm looking at this data lifeguard program, then?

Edited by Crownflame, 10 February 2012 - 02:17 PM.

[rshaffer61]

Temps look good but no voltages showing.

Please download and run Hardware Monitor
Installation (setup version only)
HWMonitor is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, fans speed.
The program handles the most common sensor chips, like ITE® IT87 series, most Winbond® ICs, and others. In addition, it can read modern CPUs on-die core thermal sensors, as well has hard drives temperature via S.M.A.R.T, and video card GPU temperature.