Random BSOD in Windows 7 64 bit

[usasma]

Let's wait for the next BSOD to see what happens.
You've made a lot of changes to the system.

 

[kc7404]

Here are the latest results ......

I hope you might find some information that will help resolve this.

Thank you for your patience.

 

[zigzag3143]

Well, I am feeling a little defeated right now as I just suffered yet another unexpected crash and I had done the following:

000.fcl ----- PowerDVD ----- Uninstalled completely
npusbio_x64.sys ----- NaturalPoint Optitrack ----- This is the most current driver
OA002Afx.sys ----- Creative Camera driver ----- Uninstalled completely
OA002Ufd.sys ----- Creative Camera driver ----- Uninstalled completely
OA002Vid.sys ----- Creative Camera driver ----- Uninstalled completely
PxHlpa64.sys Roxio CD/DVD burning program ----- Uninstalled completely
RtNdPt60.sys ----- Netgear GA511 Driver file ----- Could not find any drivers

Attached is the latest file crash details.

I hope you might have some more clues for me.

Thank you for all of your help and not giving up.

Sincerely,

KC

KC

hi and welcome

we will get to the bottom of this

this last was caused by memory.

I would
download memtestx86 and run for at least 4passes.
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

llet us know the resultls

Ken J+

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012210-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
[B]Windows 7 Kernel Version 7600 MP (4 procs) Free x6[/B]4
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Fri Jan 22 20:15:10.915 2010 (GMT-5)
System Uptime: 0 days 5:09:20.882
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80069966d0, fffffa80069966c0, fffffa80069966d0}

[B]Probably caused by : Pool_Corruption[/B] ( nt!ExFreePool+536 )

Followup: Pool_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:[/B]
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80069966d0, the pool entry being checked.
Arg3: fffffa80069966c0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80069966d0, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
[U][I][B]
PROCESS_NAME:  VistaFirewallS[/B][/I][/U]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003006d6f to fffff80002ed4f00

STACK_TEXT:  
fffff880`074193d8 fffff800`03006d6f : 00000000`00000019 00000000`00000003 fffffa80`069966d0 fffffa80`069966c0 : nt!KeBugCheckEx
fffff880`074193e0 fffff800`031e21d0 : 00000000`00000004 00000000`00008814 fffff880`63416553 fffff8a0`00000000 : nt!ExFreePool+0x536
fffff880`074194d0 fffff800`0319a1e6 : fffff880`07419840 00000000`00000000 fffffa80`069a0e90 fffff800`031c30c5 : nt!RtlpNewSecurityObject+0xcc0
fffff880`07419760 fffff800`031c2ba1 : 00000000`00000000 fffffa80`07799aa0 00000000`00000000 00000000`00000000 : nt!ObpAssignSecurity+0x82
fffff880`074197d0 fffff800`031bfb52 : fffff880`07419ae8 fffffa80`0d5e0690 fffff8a0`0357ac50 00000000`0102d9d8 : nt!ObInsertObjectEx+0x1e1
fffff880`07419a20 fffff800`031a1fa7 : fffff8a0`10d19310 fffffa80`0d5cf900 fffff8a0`10d192f0 fffffa80`0d5cf910 : nt!SeCopyClientToken+0x8a
fffff880`07419ab0 fffff800`031bf76f : 00000000`00000000 fffff880`07419b28 ffffffff`ffffffff fffffa80`0d5cf910 : nt!SepCreateClientSecurity+0xb7
fffff880`07419ae0 fffff800`03170821 : 00000000`0102db30 fffff960`00000001 fffff880`07419bc8 fffff880`07419c38 : nt!AlpcpCreateSecurityContext+0xe7
fffff880`07419b80 fffff800`02ed4153 : fffffa80`0d6c4060 00000000`00000001 00000000`00000020 00000000`00000001 : nt!NtAlpcCreateSecurityContext+0x130
fffff880`07419c20 00000000`77cb064a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0102d998 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cb064a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePool+536
fffff800`03006d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePool+536

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

Followup: Pool_corruption
---------

 

[kc7404]

Hi ZigZag,

Thank you for posting.

When you mentioned that the crash was caused by memory, was it the one yesterday or the crash before it from about 6 days ago?

I know a few things about computers, but only enough to make myself a nuisance, not productive.

I searched for the memtestx86 program but learned it works mainly for a pc with 4GB of RAM and I have 8 GB.

I then opted for the "memtest86+-4.00.iso" file but I do not know how to make it work?

Additionally, when you mention "run a system file check
type cmd in search>right click and run as admin>sfc /scannow", would I simply be:
1) Type cmd (to bring up a DOS Window)
2) How do I get it as an Administrator?
3) Then type sfc/scannow

Do I then take a screen shot of the results or can they be copied and saved in Notepad.

Thank you for any detailed explanation ... I am not IT savvy but I will follow instructions.

Sincerely,

KC

 

[kc7404]

Hello ZigZag,

I did figure out the scannow command and there were the results:

"Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc/scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>"


I still do not know how to implement and run the memetest86+.

Can someone assist?

Thank you.

Sincerely,

KC

 

[ickymay]

Hello ZigZag,

I did figure out the scannow command and there were the results:

"Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc/scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>"


I still do not know how to implement and run the memetest86+.

Can someone assist?

Thank you.

Sincerely,

KC

download this version of memtest86+ then burn to CD and run that CD from boot for at least 3 passes

 

[kc7404]

Hi Ickymay,

Thank you for the help.

I did copy and burn the file on a cd.

When I reboot my system (Dell) there are 2 keys that I can hit when it is in the process of loading:
F2 --- Setup
F12 --- Boot Menu

I tried to look (as much as I could) into both areas, but could not seem to find where to have my pc automatically run the "memtest86+-2.11.iso" file.

When I brought up the CMD Windows as an Administrator and changed directories to the CD/DVD Drive and tried to execute the file in DOS I got an error message stating that Windows could not open file.

It was suggested to either find some program on my machine or web to see if it could be run but I had little luck.

What am I doing wrong?

Thank you for your help.

Sincerely,

KC

 

[usasma]

You must use an ISO burner to burn the .iso file to the disk. When it does this, it lays out the files in the specific order that's required to make the CD/DVD bootable. Just copying the .iso to the disk won't work.

I'd suggest this free burning tool: ISO Recorder v3
Once it's installed, reboot, then right click on the .iso file and select the option to Copy Image to CD" (should be the top option). Here's a description: How to use ISO Recorder

Also, please run Driver Verifier according to the following directions. This is because of this line in the dump file above:

BAD_POOL_HEADER (19)The pool is already corrupt at the time of the current request.This may or may not be due to the caller.The internal pool links must be walked to figure out a possible cause ofthe problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.

Here's the instructions:

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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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

 

[kc7404]

Last night I ran "Memtest86+ Version 2.11" for 3 complete passes (it took over 4 hours to execute) and my computer passed with no errors.

I subsequently set up the Driver Verifier and after rebooting my machine and letting it sit overnight, there were no crashes to report.

Slightly confused, this morning I set it up again (following the same step-by-step process as I had last night) and a crash did occur.

Attached please find the results and I'll await further news.

I cannot express in words the gratitude I have for all of you who have been patiently helping me reach a resolution to this issue.

Sincerely,

KC

 

[kc7404]

2 Additional files should they prove useful.

 

[usasma]

Please turn Driver Verifier off (according to the instructions above).

The dump files point to npusbio_x64.sys - a component of your NaturalPoint Optitrack
Please download the latest drivers for it from the NaturalPoint website
Then uninstall the current one's from your system,
then install the freshly downloaded one's on your system.
The current Optitrack drivers are older (from 2007) and may have issues with Win7

Also, please update your RtNdPt60.sys driver - it's also from 2007
It belongs to your Realtek NDIS Protocol Networking Driver

Here's a summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 06:43:42.953 2010 (GMT-5)
System Uptime: 0 days 0:09:58.950
BugCheck C9, {24c, fffff880042086f0, fffff9800d9a4c60, 103}
*** WARNING: Unable to verify timestamp for npusbio_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for npusbio_x64.sys
Probably caused by : npusbio_x64.sys ( npusbio_x64+86f0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 06:56:04.163 2010 (GMT-5)
System Uptime: 0 days 0:11:59.786
BugCheck C9, {24c, fffff880018256f0, fffff9801ec6cc60, 103}
*** WARNING: Unable to verify timestamp for npusbio_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for npusbio_x64.sys
Probably caused by : npusbio_x64.sys ( npusbio_x64+86f0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 11:58:25.113 2010 (GMT-5)
System Uptime: 0 days 5:02:00.111
BugCheck C9, {24c, fffff88010bed6f0, fffff98011c6ac60, 103}
*** WARNING: Unable to verify timestamp for npusbio_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for npusbio_x64.sys
Probably caused by : npusbio_x64.sys ( npusbio_x64+86f0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[kc7404]

The Driver Verifier has been turned off.

I did reach out to the Natural Point Organization and apparently the drivers that I had were the latest and the greatest for the Track IR 4 series.

I have uninstalled those and in their place have installed the drivers for the Track IR 5 series with the hopes that the "npusbio_x64.sys" file might be different.

Additionally I did my best to locate updates for the "RtNdPt60.sys" driver from the Realtek NDIS Protocol Networking Driver and I believe I may have found them.

I will post again when another BSOD crash occurs.

Sincerely,

KC

 

[kc7404]

I thought I had indirectly won the battle as I did not have a crash for a few days but alas it was not meant to be at this point in time.

Here are the new results.

Thank you for your assistance and I'll await further news.

Sincerely,

KC

 

[kc7404]

Another file and another crash record if needed .....

Sigh ..... I almost wish I had just left my system with Vista

 

[ickymay]

Another file and another crash record if needed .....

Sigh ..... I almost wish I had just left my system with Vista

WD shows

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031a856d, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008e9d740, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!CmpKcbCacheLookup+1dd
fffff800`031a856d 418b45f4 mov eax,dword ptr [r13-0Ch]

CONTEXT: fffff88008e9d740 -- (.cxr 0xfffff88008e9d740)
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000036c
rdx=000000000da57e80 rsi=fffff8a000814608 rdi=fffff88008e9e318
rip=fffff800031a856d rsp=fffff88008e9e120 rbp=fffff8a000814010
r8=0000000000000007 r9=0000000000000000 r10=000000000000000d
r11=fffff88008e9e2d0 r12=fffff8a00477ecb0 r13=fff3f3f3fff3f3f0
r14=0000000000000003 r15=fffff8a003e296f8
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!CmpKcbCacheLookup+0x1dd:
fffff800`031a856d 418b45f4 mov eax,dword ptr [r13-0Ch] ds:002b:fff3f3f3`fff3f3e4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Integrator.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800031a7b28 to fffff800031a856d

STACK_TEXT:
fffff880`08e9e120 fffff800`031a7b28 : fffff880`08e9e2d0 fffff880`00000005 fffff880`08e9e6a8 fffff880`08e9e6c0 : nt!CmpKcbCacheLookup+0x1dd
fffff880`08e9e210 fffff800`031a5d81 : fffff8a0`00020220 fffff880`08e9e6c0 fffff880`08e9e6f8 fffff880`08e9e6e0 : nt!CmpBuildHashStackAndLookupCache+0x328
fffff880`08e9e5f0 fffff800`031c5764 : fffff800`031a5ae0 00000000`00000000 fffffa80`071c6470 00000000`00000701 : nt!CmpParseKey+0x2a1
fffff880`08e9e8c0 fffff800`031ca876 : fffffa80`071c6470 fffff880`08e9ea40 00000000`00000040 fffffa80`06a2d900 : nt!ObpLookupObjectName+0x585
fffff880`08e9e9c0 fffff800`031a9bec : 00000000`00000000 00000000`00000000 fffff880`08e9ec01 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`08e9ea90 fffff800`031abd3b : 00000000`0443e778 00000000`000f003f 00000000`0443e798 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`08e9ebe0 fffff800`02ece153 : fffffa80`07116060 fffff880`08e9eca0 00000000`7efa1000 fffffa80`08ffcf20 : nt!NtOpenKeyEx+0xf
fffff880`08e9ec20 00000000`76df0e0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0443e738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76df0e0a


FOLLOWUP_IP:
nt!CmpKcbCacheLookup+1dd
fffff800`031a856d 418b45f4 mov eax,dword ptr [r13-0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpKcbCacheLookup+1dd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff88008e9d740 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd

BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd

Followup: MachineOwner
---------

as a Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION from the MSDN library it states "The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code."
the suggested cause is:
"This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code."
but I'm not convinced this is what's happening here.

however blue screen viewer claims raspptp.sys the microsoft Peer-to-Peer Tunneling Protocol driver was the cause ?
This would be in keeping with a network problem either drivers or a collision with an AV or firewall ?

these two drivers

npusbio_x64.sys fffff880`0192e000 fffff300`0193f000 0xfffffa8000011000 0x461cca35 11/04/2007 11:44:53
RtNdPt60.sys fffff880`046ff000 fffff300`0470b000 0xfffffa800000c000 0x475dfad0 11/12/2007 02:49:52

are still out of date and need updating ?

as usama has said npusbio_x64.sys is a component of your NaturalPoint Optitrack and RtNdPt60.sys driver belongs to to your Realtek NDIS Protocol Networking Driver, presumably your struggling to find an updated version for these ?

At this point I feel your issue is to do with networking , can you please tell us what antivirus and firewall you are using ?

 

[kc7404]

Ickymay,

Thank you for your response.

Concerning the drivers for the TrackIR and the Realtek NDIS Protocol Networking, I can honestly say I was genuinely under the impression I had found and installed the newest drivers available.

Beyond a shadow of a doubt I can confirm this for the TrackIR as I have been at their site and have tried the latest drivers for both the TrackIR 4 (which is the unit I have) and the TrackIR 5 ..... I have even spoken with one of their technicians who told me both were compatible with Windows 7 yet here we are with these results.

As for the Realtek NDIS Protocol Networking Driver, I thought I had found the right file / files but this leaves me more confused than ever and I am unsure what to search for.

==========================================================

For my anti-virus, I use Avast which I update and run full checks weekly:
avast! - Download Free Antivirus Software or Internet Security

For my firewall, I use Vista Firewall Control made by Sphinx Software:
Windows 7 Firewall Control : Sphinx Software
I can change this to their Windows 7 version but liked the interface for Vista better so I kept it ... I was originally on Vista and then upgraded to 7.

==========================================================

I'll await further responses / recommendations.

Should I simply wipe my C Drive, buy a full copy of Windows 7 (not the upgrade from Vista) and simply start a fresh or will I simply have these issues again?

I have not heard other TrackIR Users complain about crashes with Windows 7 so could it be something that doesn't bode well with the Vista-to-7 transition but might not happen in a Windows 7 fresh install?

Thank you for your time.

Sincerely,

KC

 

[kc7404]

A copy of the most recent crash ..... Does it reveal anything new?

 

[ickymay]

A copy of the most recent crash ..... Does it reveal anything new?

nope crash was again

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000315656d, fffff88003721740, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )

Followup: MachineOwner
---------

I think it's possible theres a conflict between TrackIR and another device , can you remove it purely for testing purposes ?

I would also unninstall Avast and your Sphinx firewall temporarily to eliminate them as the possible cause, use MSE and windows firewall temporarily

I don't know if your going to gain anything by a fresh install just yet as you might just end up with the same issues

the upgrade disk has a full version of windows 7 on it , so did you install from boot and wipe vista or did you install from within vista ?

 

[kc7404]

Hi Ickymay,

Thank you for responding.

I think it's possible theres a conflict between TrackIR and another device , can you remove it purely for testing purposes ?

Do you mean simply unplug the device or unplug it an uninstall the software?

so did you install from boot and wipe vista or did you install from within vista ?

It was only just a short while ago but my memory is horrible. I believe I inserted the disk and installed from Vista but I am not 100% sure, sorry.

I'll await your response.

 

[rossathome]

I too have Windows 7 64 bit .I fixed this random reboot by uninstalling Roxio from Dell . it was ver 9 DE . I noticed the crash happened with this install so removing it thus fixed the problem. I noticed you too have Roxio. Roxio products are quite buggy now. watch out with bloatware like this. let me know if this helps.
Ross