General ⇒ Not getting DVI file

[pallav]

I am not getting DVI file and getting an error report as follows:

MiKTeX Problem Report
Message: The page could not be rendered.
Data: Error: /syntaxerror in -file-
Operand stack:
39158280 55380996 1000 600 600
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1893 1 3 %oparray_pop 1892 1 3 %oparray_pop 1876 1 3 %oparray_pop 1755 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:77/200(L)-- --dict:170/300(L)--
Current allocation mode is local
Last OS error: No such file or directory
MiKTeX GPL Ghostscript 8.60: Unrecoverable error, exit code 1

Source: C:\work3\miktex-2.8\Libraries\MiKTeX\Dvi\DviPage.cpp
Line: 1045
MiKTeX: 2.8
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
SystemAdmin: yes
PowerUser: no
Root0: C:\Documents and Settings\Administrator\Application Data\MiKTeX\2.8
Root1: C:\Documents and Settings\Administrator\Local Settings\Application Data\MiKTeX\2.8
Root2: C:\Documents and Settings\All Users\Application Data\MiKTeX\2.8
Root3: C:\Program Files\MiKTeX 2.8
UserInstall: C:\Documents and Settings\Administrator\Application Data\MiKTeX\2.8
UserConfig: C:\Documents and Settings\Administrator\Application Data\MiKTeX\2.8
UserData: C:\Documents and Settings\Administrator\Local Settings\Application Data\MiKTeX\2.8
CommonInstall: C:\Program Files\MiKTeX 2.8
CommonConfig: C:\Documents and Settings\All Users\Application Data\MiKTeX\2.8
CommonData: C:\Documents and Settings\All Users\Application Data\MiKTeX\2.8

[adrian]

The approach to solving these problems is almost always to produce the smallest
(.tex) file that illustrates the problem. Start from a minimal file, and add
lines until adding a single line causes the problem. If you then post your file, someone will doubtless be able to help.
The log file often is not enough - being able to reproduce the problem on someone
else's system is usually enough.