Regular BSOD - won't restart unless power disconnected for 15min or more!!

This BSOD has been happening more regularly, sometimes after 30mins, other times after a couple of hours.

If I try and restart it crashes shortly after Win 7 logo appears.

Unless I disconnect the power for at least 15mins, it won't restart Windows - just re crashes.

Have attached the dump and sysdata files - note that the two files are not always written.

Hopefully someone can analyze this for me.

Rig is i7-920 on an ASUS P6TD Deluxe(not overclocked), Win 7 SP1, Nvidia Quadro FX 1800, 12gb Patriot RAM, disks are WDC Raptor 280GB for OS, Patriot Warp V2 64GB SSD, and 2 x 1TB Seagate Barracuda's in Raid 0




Windows Forum Admin
Staff member
Premium Supporter
[FONT=Courier New][SIZE=2][COLOR=#000000]Crash dump file:        C:\Users\Mike\Downloads\SysCrashData\020612-55037-01.dmp
Date/time:              2/5/2012 5:23:49 AM GMT
Uptime:                 01:25:26
Bug check code:         0x3D
Bug check parm 1:       0xFFFFF88004DDBF40
Bug check parm 2:       0x0
Bug check parm 3:       0x0
Bug check parm 4:       0xFFFFF880015C6E47
Probably caused by:     [URL=""]ntoskrnl.exe[/URL]
Driver description:     [URL=" Kernel & System"]NT Kernel & System[/URL]
Driver product:         [URL="® Windows® Operating System"]Microsoft® Windows® Operating System[/URL]
Driver company:         [URL=" Corporation"]Microsoft Corporation[/URL]
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              8
Page size:              4096

Bug check description:
This bug check appears very infrequently. 


The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 

There are nearly half a dozen Norton driver modules in the crash dump. Consider following the steps outlined below to determine if the crashes continue to happen without Norton.

Last edited by a moderator:
Thanks Mike for the quick reply,
Using BlueScreenView I notice that (along with ntoskrnl.exe) Mv61xx.sys, are the only two marked as 'appears in the crash stack'

Re Norton, I have a Norton suite installed, plus Norton Ghost backup utility.


Windows Forum Admin
Staff member
Premium Supporter
I was looking at all loaded modules from the time of the stop. It is quite possible that the persistent slowdown you describe in the boot process is caused by a driver conflict. As antivirus would be typically suspect, and as these are the most predominant modules loaded (outside of Microsoft ones), this would be a starting point. Have you checked event viewer logs around the time of the slowdown (which you describe as a sort of outage). I would suggest doing so and also would ask if Saltgrass or Elmer can check this one.

Hi Mike,
Firstly I might have found the culprit - Norton Ghost - more after this,
Re event viewer - nothing obvious - there is only an
Event 41 Kernel-Power
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly".

Re rebooting , in a normal (successful) Windows start-up I hear a couple of sets of disk chatter, after one of these crashes the logo comes up, then a brief disk noise then silence, within 5 secs or so another VERY brief BSOD (only about half a second ! no time to read it) then it shuts down and tries to restart- viscous cycle.

What intrigues me is why disconnecting the power for some minutes enables a reboot?? But if I don't - even after an hour or so Windows still won't start. Is there something stuck in memory?

Now re Norton Ghost, because I was getting BSOD after 30 mins or so after boot, Ghost had missed backing up my main Raid 0 drive(s), so I've been trying to do manual runs the last few days, I've noticed that each time I've tried this (4-5 times ) I get a BSOD after about 5 mins. So earlier this evening I stopped the Ghost service - at the moment the PC has been up for over 6 hours with no BSOD. I'll let it run all night and see if this lasts :).

Another point is that I think this Ghost issue might only happen when I try and run it against my Raid drives, I was able to run it on my smaller system drive (300GB Rapter) and my SSD drive. I note again that mv61xx.sys was in the crash stack - I believe mv61xx.sys is related to a Marvel IDE/SATA driver.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.