Brand new laptop, Win7 Ult x64, BSOD's!!!

Casey R · 11 Jan 2010

Hi -

Did you use the Norton Removal Tool? I found NIS drivers in the dump. Please run/ re-run the NRT.

Download the NRT; save to desktop. Then go to desktop, RIGHT-click on the NRT icon and select "Run as Administrator". When complete - re-boot.

NRT - ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Thanks. Unfortunately I'm not able to get this program to run. It just hangs, the process seems to be running according to Task Manager but nothing happens.

Is there anything else you could suggest? Where might I find any remnants of NIS?

done.

As for the newest round of BSODs - 6 mini kernel dumps -

(3) 0x1e (0xc0000005,,,) = kernel mode exception; 0xc...5 = memory access violation; prob cause = "memory corruption"; app running = "Seesmic Deskto" - do you know what this is?

Yes - it's a Twitter management application - Seesmic Desktop. It runs on Adobe's AIR platform - might it be unstable? There's a version that runs natively in Windows but it's not as good (it regularly misses tweets).

- 0x1e #2 - this one was a "VERIFIER_ENABLED_VISTA_MINIDUMP", eventhough Windows 7, but named the Microsoft network driver tcpip.sys

- 0x1e #3 - verifier came up empty; p/c = "memory corruption"; app running = chrome.exe

(1) 0xa = driver attempted improper access of paged pool, p/c = "memory corruption"

Anything I can do about these?

I did see this VNC mirror driver in the dump =

Code:

 vncmirror.sys Fri Mar 14 13:43:05 2008 (47DAB929)

I don't know which VNC edition you have - make sure it is not the Free version as it's not compatible with Vista and therefore not with Windows 7 either, per the VNC site --> RealVNC - VNC feature comparison and download selector

I have the Enterprise edition which claims to be compatible. It works fine, so I guess it is, lol.

(2) 0xc9 (0x21a,,,) = Driver Verifier flagged the Microsoft SCSI class system dll classpmp.sys
The "0x21a" = The previously-set IRP_MJ_POWER status has been converted to STATUS_NOT_SUPPORTED.

Code:

FAILURE_BUCKET_ID:  X64_0xc9_21a_VRF_CLASSPNP!ClasspPowerDownCompletion+26d

What devices do you have connected to the system? Have you changed the power settings?
START | power | power options | reset defaults

I occasionally plug my phone in via USB. But nothing was plugged in when any of these BSOD's happened....and no, I haven't changed the power settings.

Do you have Adobe CS4 or other Adobe product installed? This Adobe driver has caused other BSODs in recent times -

Code:

adfs.SYS     Thu Jun 26 16:52:37 2008 (48640195)

It is possible for this to be software replated, specifically NIS if corrupted itself because no NRT used or NRT did not take it out the 1st time around; VNC appears to be a candidate as well and Adobe.

Try the above suggestions, see if BSODs persist.

Regards. . .

jcgriff2

.

I do have CS4 installed. It's a must for the work I do, so I can't get rid of it. Hopefully they fix any compatability issues.

Casey R · 12 Jan 2010

Guys, here's something interesting. I dismissed it until now, but since it just happened again it is now worth pointing out.

Almost every BSOD I have had over the past two weeks has happened when I have left my computer on, running, but with no activity. For example, I might have been using the laptop for a few hours with no BSOD's, then got up to go to the kitchen to make food. I'll leave the system alone for 10 or 15 minutes, and when I return, there will have been a BSOD.

Logically this to me sounds like perhaps power management? Ie, after no activity for a certain amount of time, the system will attempt to go into low power mode and will then BSOD? I've also noticed that a few times, the same thing has happened when I put the computer into sleep mode. It will seem like it has gone to sleep, but later on when I attempt to bring it out - I find it has restarted due to a BSOD.

What do you recommend I look at it to try and see if this is the problem? I haven't changed any of the power management settings since installing the OS.

jcgriff2 · 13 Jan 2010

Hi -

The system is never really idle, i.e., "no activity". In fact just the opposite. During the 15 or so min that you are away from the system, Windows 7 senses idle user time and then Task Scheduler goes to work - running housekeeping chores. There are jobs scheduled that specifically wait for idle user time, some specific to idle user Internet activity.

Please try the Norton Removal tool again - run it in SAFEMODE w/ NO Internet connectivity at an elevated admin level (RIGHT-click, run as admin).

Change the power setting option - choose a different plan and see if that helps as well.

Regards. . .

jcgriff2

.

Casey R · 14 Jan 2010

Managed to run the Norton Removal Tool in safe mode.....it doesn't appear to have helped...still getting lots of BSOD's.

Here's the latest batch of Minidumps.

usasma · 14 Jan 2010

Multiple different errors. Please run Driver Verifier using these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 11 23:23:15.063 2010 (GMT-5)
System Uptime: 0 days 3:54:53.014
BugCheck 1E, {ffffffffc0000005, fffff80000b9a040, 0, 0}
Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+374f2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 12 23:33:00.049 2010 (GMT-5)
System Uptime: 0 days 12:16:04.000
BugCheck 1E, {ffffffffc000001d, fffff88000fdc810, 2, fffffa80046dc300}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 00:12:17.248 2010 (GMT-5)
System Uptime: 0 days 0:38:19.074
BugCheck 3B, {c000001d, fffff80002b80818, fffff88007a7ed10, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  vlc.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 21:21:16.564 2010 (GMT-5)
System Uptime: 0 days 4:36:39.515
BugCheck 4E, {99, 117058, 2, 116fd8}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 22:16:09.339 2010 (GMT-5)
System Uptime: 0 days 0:54:21.290
BugCheck BE, {fffff88001163598, 8000000003665121, fffff88007791080, a}
Probably caused by : cng.sys ( cng!AesExpandKey+2b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GoogleCrashHan
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 23:10:31.090 2010 (GMT-5)
System Uptime: 0 days 0:53:50.041
BugCheck 1, {744a2dd9, 0, ffff0000, fffff88007d51c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 17:22:04.049 2010 (GMT-5)
System Uptime: 0 days 3:37:00.000
BugCheck 1000007E, {ffffffffc000001d, fffff88000c7d800, fffff88002fd9718, fffff88002fd8f70}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 17:32:03.649 2010 (GMT-5)
System Uptime: 0 days 0:09:29.599
BugCheck 50, {fffff7ffdaa7e318, 0, fffff80002bc4406, 2}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  wmpnetwk.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 17:40:58.656 2010 (GMT-5)
System Uptime: 0 days 0:07:57.607
BugCheck 24, {1904fb, fffff8800627bd88, fffff8800627b5e0, fffff880012d1806}
Probably caused by : memory_corruption
PROCESS_NAME:  svchost.exe
DEFAULT_BUCKET_ID:  CODE_CORRUPTION

Casey R · 19 Jan 2010

Latest bunch of Minidumps....happened with Driver Verifier running...

usasma · 19 Jan 2010

Looks to be an issue with your storage sub-system (hard drive, file system, controller, etc).

Start with a hard drive diagnostic: HD Diagnostic

Then this:

CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Then update Windows

Then remove the current motherboard/chipset/storage drivers - and replace them with freshly downloaded drivers. Here's a link to the Clevo download website: CLEVO - Download
I suspect that this will be the critical thing - so please let us know the specifics of your progress here.

Then, please remove these drivers while we're troubleshooting:
adfs.SYS Thu Jun 26 16:52:37 2008 - Adobe file system (just uninstall all Adobe products)
vncmirror.sys Fri Mar 14 13:43:05 2008 - VNC remote control software

Then see if you still get BSOD's.

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 16 20:07:56.775 2010 (GMT-5)
System Uptime: 0 days 0:17:16.791
BugCheck A, {6aacb78, 2, 0, fffff80002acc838}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  googletalk.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 01:18:35.551 2010 (GMT-5)
System Uptime: 0 days 0:00:33.564
BugCheck C9, {21a, fffff880018c928d, fffff9800a1d0cf0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspPowerDownCompletion+26d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 11:39:59.802 2010 (GMT-5)
System Uptime: 0 days 0:51:31.815
BugCheck 3D, {fffff88008741ed0, 0, 0, fffff80002acc80e}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 12:53:53.472 2010 (GMT-5)
System Uptime: 0 days 1:12:54.485
BugCheck C9, {21a, fffff880018da28d, fffff98016ec2cf0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspPowerDownCompletion+26d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 23:16:55.413 2010 (GMT-5)
System Uptime: 0 days 6:10:28.301
BugCheck 24, {1904fb, fffff88002705028, fffff88002704880, fffff880012a2806}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 01:53:11.871 2010 (GMT-5)
System Uptime: 1 days 2:35:45.884
BugCheck 1A, {403, fffff68000016c68, ea50000022bd5867, fffff68000016c6c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f72 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe

Casey R · 20 Jan 2010

HD Diagnostic found no errors:

Checkdisk results:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 21/01/2010 02:30:27
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: KingSimon-PC
Description:

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

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
111872 file records processed.

File verification completed.
168 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
150572 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
111872 file SDs/SIDs processed.

Cleaning up 151 unused index entries from index $SII of file 0x9.
Cleaning up 151 unused index entries from index $SDH of file 0x9.
Cleaning up 151 unused security descriptors.
Security descriptor verification completed.
19351 data files processed.

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

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

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

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

244093951 KB total disk space.
53923848 KB in 90292 files.
58264 KB in 19352 indexes.
0 KB in bad sectors.
220983 KB in use by the system.
65536 KB occupied by the log file.
189890856 KB available on disk.

4096 bytes in each allocation unit.
61023487 total allocation units on disk.
47472714 allocation units available on disk.

Internal Info:
00 b5 01 00 57 ac 01 00 d6 3f 03 00 00 00 00 00 ....W....?......
2e 02 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/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="2010-01-21T02:30:27.000000000Z" />
<EventRecordID>5482</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>KingSimon-PC</Computer>
<Security />
</System>
<EventData>
<Data>

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

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
111872 file records processed.

File verification completed.
168 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
150572 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
111872 file SDs/SIDs processed.

Cleaning up 151 unused index entries from index $SII of file 0x9.
Cleaning up 151 unused index entries from index $SDH of file 0x9.
Cleaning up 151 unused security descriptors.
Security descriptor verification completed.
19351 data files processed.

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

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

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

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

244093951 KB total disk space.
53923848 KB in 90292 files.
58264 KB in 19352 indexes.
0 KB in bad sectors.
220983 KB in use by the system.
65536 KB occupied by the log file.
189890856 KB available on disk.

4096 bytes in each allocation unit.
61023487 total allocation units on disk.
47472714 allocation units available on disk.

Internal Info:
00 b5 01 00 57 ac 01 00 d6 3f 03 00 00 00 00 00 ....W....?......
2e 02 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

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

Going to replace drivers now.

usasma · 21 Jan 2010

Looks good so far. We can rule out the hard drive and the file system.

Casey R · 22 Jan 2010

I was only able to find Chipset drivers on the CLEVO website......no motherboard or storage ones.

What do I look for in device manager in order to remove the existing chipset drivers? Or can I just install the new ones over the top?